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.
Ilda
2 months agoRuthann
3 months agoDeeann
3 months agoCharlene
3 months agoWerner
3 months agoBok
3 months agoTula
4 months agoVeronika
4 months agoLawanda
4 months agoHeidy
4 months agoLavonna
4 months agoDannette
5 months agoPrecious
5 months agoDoyle
5 months agoAlonso
5 months agoLatricia
6 months agoSalome
6 months agoIzetta
6 months agoBette
6 months agoMuriel
6 months agoVallie
7 months agoQuentin
7 months agoAleta
9 days agoKandis
14 days agoLovetta
19 days agoAhmed
24 days agoShawnda
2 months agoTy
7 months agoOzell
7 months agoTricia
7 months ago