Skip to content
The Workflow Library
Get the full library

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

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

Professional

Seat pricing: Professional edition. To build it, a GTM Seat or an Ops Seat (an Ops Seat cannot create marketing emails or sequences). Per-hub plans: Data Hub Professional.

6 steps
Per-hub plans: also Marketing Hub Professional

On per-hub plans, one of its steps belongs to another subscription: add to static list needs Marketing Hub Professional. Both are required to build it as written. On seat pricing the edition covers both.

Updated for HubSpot seat pricing
OutcomeContacts 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 mapdata-quality-046
Territory, phone, or country known/changed leads to Custom code: territory-to-country lookup vs phone and address. Custom code: territory-to-country lookup vs phone and address leads to Mismatch?. Mismatch? leads to yes: Flag Mismatch, add to list, create task; no: Consistent. yes no Territory, phone, or country known/changed Custom code: territory-to-country lookup vs phone and address Mismatch? Flag Mismatch, add to list, create task Consistent
Territory, phone, or country known/changed leads to Custom code: territory-to-country lookup vs phone and address. Custom code: territory-to-country lookup vs phone and address leads to Mismatch?. Mismatch? leads to yes: Flag Mismatch, add to list, create task; no: Consistent. yes no Territory, phone, or country known/changed Custom code: territory-to-country lookup vs phone and address Mismatch? Flag Mismatch, add to list, create task Consistent

One of 565 written HubSpot workflow specs, by a collective of independent HubSpot consultants.

When to use it, when not to

Use it

  • Use 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.
  • Use 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.
Read more on when to use itShow less

Skip it

  • Do 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.
  • Do 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.
Read more on when to skip itShow less

The rest of this spec

Prerequisites · 5 items

Every property with its label, internal name, type and options, plus the assets the workflow needs.

Enrollment · 4 parts

The trigger, the criteria as ticked in the UI, the re-enrollment rule and the suppression list.

Steps · 6 numbered actions

Each action in order with its parameters, branches and delays.

Known pitfalls · 4

Traps seen in production, each with what breaks and what to do instead.

Test plan and UAT script · 4 cases, 3 variants

How to prove it works in a test portal, one case per branch, and a sign-off sheet.

Files · PDF, Markdown, JSON, CSV, code

The properties JSON creates the fields in one call. The workflow JSON documents the build. The custom coded action ships as a ready-to-paste .js file.

Install · 1 click, switched off

The installer creates the properties and the workflow, switched off, then opens a task for what it cannot create. Nothing is deleted, enabled or enrolled.

Unlock all 565 specs, 149 EUR

One-time, excl. VAT. 30-day refund. Installs in 3 portals. Founding price until 30 November.

Read the free Data quality spec

Not the workflow you needed?

More in Data quality

50 specs in this section

See all 50 This category, 39 EUR
FreeRequired field enforcement on contact creation (email or phone missing)Contact9 steps Cross-field consistency check: phone country code vs. address countryContact6 steps Phone number formatting to a standard international formatContact4 steps Duplicate contact detection and merge review queueContact7 steps

Read 12 complete specs before you pay.

One per category, same format as the paid ones. Email only, no card.

We email the link, then a short note when specs change. Nothing else.

149 EUR199

Full library, 565 specs
Get the full library