Cross-field consistency check: phone country code vs. address country

Outcome. Contacts whose phone number's country calling code clearly disagrees with their stated address country are flagged for a look, catching mismatched or copy-pasted contact records before a call goes to the wrong country's sales rep or time zone.

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

flowchart TD
    A[Phone number and Country/Region known] --> B[Custom code: extract calling code, compare to country table]
    B --> C{Result}
    C -->|match| D[Status: Consistent]
    C -->|ambiguous| E[Status: Ambiguous - shared calling code]
    C -->|mismatch| F[Status: Mismatch - needs review]
    F --> G[Create task]

When to use it, when not to

• UseUse it once phone numbers and country values are already reasonably normalized, see data-quality-003 for phone format and data-quality-004 for country normalization. A consistency check built on messy inputs on both sides mostly produces noise.
• UseUse it as a light sanity check, not a hard rule. A contact can legitimately carry a phone number from a country other than where they currently live, an expat, or a second office line.
• SkipDo not use it on portals where Country or Phone number is rarely populated; a check that can only run on a small fraction of records is not worth the build effort yet.
• SkipDo not use it expecting precise country detection from a phone number alone. Several countries share the same calling code, for example the North American Numbering Plan covers the United States, Canada, and a number of Caribbean nations all under +1, so this fiche treats those as ambiguous rather than a firm mismatch.