What are three key considerations when working with a customer on their Service Territory management...

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.