Territory Planning setup and processing for Agentforce Life Sciences
Key Takeaway
Activate an Enterprise Territory Management territory model before you create alignments, because each Territory Planning alignment imports the active hierarchy as its planning areas.
Territory Planning in Agentforce Life Sciences uses a planning dataset, Sales Planning segments, and alignment rules to decide which accounts and users belong to which Enterprise Territory Management territory. A scheduled process then turns those decisions into territory association records.
What the org needs
Territory Planning requires Enterprise or Unlimited Edition with Life Sciences Cloud and the Life Sciences Customer Engagement managed package. The org also needs these add-on licenses:
- Life Sciences Cloud for Customer Engagement
- AnalyticsQueryServiceForSalesPlanning
- SalesPlanning
- SonicEmbeddedStoreBase
Assign the AnalyticsQueryServiceForSalesPlanning, SalesPlanning, and SonicEmbeddedStoreBase licenses to each user who accesses Territory Planning.
Before setup, the org also needs these settings and components:
- "Sales Territories" enabled
- "Person Accounts" turned on
- "State and Country/Territory Picklists" turned on
- "Data Pipelines" enabled
- The Customer Engagement managed package installed
- "Admin Console" enabled
Rules that use specialty data depend on the Healthcare Provider Specialty trigger handler being active, so verify this trigger handler during org preparation.