Our business has Service resources at Country Level an that is the lowest level of service territory hierarchy we follow. Shall we implement the same in FSL, what I understand is:
1. Salesforce recommends to setup territories at much lower level.
2. Which helps in better optimization to keep the less resources per territory.
3. Setting up at country level will have greater impact on time zones and job happening at a particular site.
What are the other downsides of setting up service resources at country level?
What time zone should I setup when defining Service territory at Country Level?
Thanks.
Hey Michel,
Beyond your three points, here are some additional downsides of doing country-level territories
- Poor optimizer performance: Large geographic scope inflates travel time estimates and produces unbalanced schedules
- SLA risk: Hard to guarantee response time SLAs when the nearest resource could be hundreds of miles away
- Operating hours conflict: A single territory can't accurately represent multiple time zones
- Weak reporting: No regional granularity to identify underperforming areas
For Time Zone: Set it to your primary operations hub for that country. If the country spans multiple time zones, a single choice will cause scheduling inaccuracies. This is the strongest argument for splitting into sub-territories by region/time zone, which also resolves most of the issues above. Good luck!
