Create or update a territory custom object record when an account is assigned to a territory

Outcome. Every distinct territory value used on companies gets exactly one Territories record with a running account count, instead of sales ops keeping a separate spreadsheet of who owns which patch.

Workflow map Enrollment, branches and actions at a glance sales-ops-022

flowchart TD
    A[Company Territory property changes] --> B[Custom code: find or create territory record, adjust counts]
    B --> C{Sync failed?}
    C -->|Yes| D[Notify sales ops of failure]
    C -->|No| E[End, counts and associations updated]

When to use it, when not to

• UseUse it when territory reporting needs to live on a record you can associate other objects to (deals, contacts, tasks) rather than staying stuck as a text or enumeration value on the company alone.
• UseUse it once your Territory values are stable and standardized (a fixed list, not free text) so one company value maps to exactly one territory record.
• SkipDo not use it if your territory model changes shape often (frequent re-splits, renames); every rename means a new territory record accumulates unless you actively archive the old one, since this workflow only creates or increments, it never merges or renames existing records.
• SkipDo not build this if you only need territory reporting inside a dashboard filter on the company property itself; a dedicated custom object is worth it mainly when you need to associate other records (like a territory owner's tasks or plan documents) to the territory itself.