Territory-country mismatch flag (phone or address vs. assigned territory)

Outcome. Contacts whose phone country code or address country falls outside the countries actually covered by their assigned sales territory get flagged before a rep spends time on a lead routed to the wrong region.

Workflow map Enrollment, branches and actions at a glance data-quality-046

flowchart TD
    A[Territory, phone, or country known/changed] --> B[Custom code: territory-to-country lookup vs phone and address]
    B --> C{Mismatch?}
    C -->|yes| D[Flag Mismatch, add to list, create task]
    C -->|no| E[Consistent]

When to use it, when not to

• UseUse it once you have a defined Territory property, assigned by a lead-routing workflow for example, mapped to a fixed list of countries per territory, and territory-to-country coverage is stable enough to hardcode into a lookup table.
• UseUse it as a check on the routing outcome, complementary to data-quality-029, which checks phone-versus-address consistency directly without reference to an assigned territory. This fiche instead checks the assignment itself against the country evidence.
• SkipDo not use it if territory assignment in your portal is based on something other than country, an industry vertical, company size, named accounts. This fiche only makes sense for geography-based territory models.
• SkipDo not use it to automatically reassign the contact to a different territory owner. A country mismatch might be a legitimate exception, a global account intentionally routed to a specific rep regardless of geography. Flag it for a human decision rather than silently reassigning.