Troubleshooting accounts that fail to align to territories
Key Takeaway
When an account fails to align, check three things: the account is a valid healthcare provider, it has the data its job needs, and the job that matches its rule type has run. A geographic job that succeeds but processes zero accounts usually means the wrong job ran for the rule type.
In Agentforce Life Sciences for Customer Engagement, batch jobs align accounts to sales reps' territories. The jobs turn manual territory assignments or geographic rules into records and sharing that give reps access. When an account fails to align, check the conditions the relevant job requires: an active account, a primary healthcare provider, the correct assignment or address data, and the job that matches the rule type.
How accounts align to territories
Automated batch jobs align accounts to territories. Alignment comes either from explicit mappings or from geographic codes. Explicit mappings are manual assignments made in Salesforce's standard territory management tools or loaded from external systems. Geographic codes include zip or postal codes and bricks.
The jobs turn manual assignments or geographic rules into Provider Account Territory Info records and sharing. If the right job has not run, or the account doesn't meet the job's conditions, the account doesn't align. Each of the three jobs handles a different alignment source.
| Job | Alignment source |
|---|---|
| Align Account to Territory | Manual account-to-territory assignments |
| Align Zip to Territory | Postal code rules (GeoCodeType = ZipToTerritory), used mainly in the United States |
| Align Brick to Territory | Brick and Geo Group rules (GeoCodeType = BrickToTerritory, GeoGroup1, or GeoGroup2), used mainly in Europe |
If Affiliation Rules exist in the org, the Affiliation Alignment job runs automatically after the Account, Zip, and Brick to Territory jobs run. The Affiliation Alignment job aligns accounts to the specified territories through provider affiliations that meet the rule criteria: Account Type, Affiliation role, and Specialty.
A job that completes successfully but processes zero accounts usually means the wrong job ran for the rule type. Check the rule's GeoCodeType and run the job that matches it. ZipToTerritory rules need Align Zip to Territory. BrickToTerritory, GeoGroup1, and GeoGroup2 rules need Align Brick to Territory, not Align Zip to Territory.
Marco manages territories for a US sales team. His postal code rules all use GeoCodeType = ZipToTerritory, but he runs Align Brick to Territory by mistake. The run completes successfully but processes zero accounts. Because zip rules need Align Zip to Territory, he runs that job instead. Now the valid accounts whose postal codes match his rules align to their territories.