What are three key considerations when working with a customer on their Service Territory management design?
Service Territory design heavily impacts the performance of the Gantt and Optimization engine.
Option C is correct: Historically, Salesforce recommended keeping Service Territories to around 50 Resources to ensure the Gantt loads quickly and optimization runs efficiently. (While limits have increased, this remains a safe 'rule of thumb' for design).
Option D is correct: Territories are almost always Geographic. This drives the travel time calculations, which are central to the Field Service value proposition.
Option B is correct: This refers to the Appointment Booking search space. If a territory is too massive, the engine has to score thousands of candidates, which is slow. Designing territories/policies so that the engine evaluates a focused set (e.g., ~20 qualified candidates) ensures sub-second response times for booking slots.
Option A (Skill assignments) is about Resources, not Territory structure.
Werner
5 days agoBok
10 days agoTula
15 days agoVeronika
20 days agoLawanda
25 days agoHeidy
1 month agoLavonna
1 month agoDannette
2 months agoPrecious
2 months agoDoyle
2 months agoAlonso
2 months agoLatricia
3 months agoSalome
3 months agoIzetta
3 months agoBette
3 months agoMuriel
3 months agoVallie
4 months agoQuentin
4 months agoTy
4 months agoOzell
4 months agoTricia
4 months ago