Phone number formatting to a standard international format

Outcome. Every contact's phone number lands in one consistent international format, so dialers, texting tools, and country-based segmentation all read the same value.

flowchart TD
    A[Phone or mobile known, not yet formatted] --> B[Format a phone number: Phone number]
    B --> C{Mobile phone also known?}
    C -->|yes| D[Format a phone number: Mobile phone number]
    C -->|no| E[Skip mobile format]
    D --> F[Set Phone format status = Formatted]
    E --> F
    F --> G{Parse failed?}
    G -->|yes| H[Set Needs review + add to review list]
    G -->|no| I[Done]

When to use it / when not to

• Use it when phone numbers arrive from many sources (forms, imports, manual entry) in inconsistent formats: local format, dashes, parentheses, missing country code.
• Use it when a connected calling or SMS tool needs consistent formatting to dial or send reliably.
• Do not use it if the portal is single-country with a fixed local format already enforced at the form level. A simple strip-formatting Set property value action may be enough, see Variants.
• Do not use it as a substitute for phone number validity checking (catching fake or impossible numbers). That needs a separate custom code check, see data-quality-029 for the related consistency check.