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