Use case
Give every contact a consistent number.
Normalize phone numbers before they enter your CRM or messaging workflow. QuietPass’s free formatting and validation checks help catch malformed input and make numbers easier to compare across systems.
Start with the input, not an SMS
Availability: QuietPass is in early access. Formatting, numbering-plan validation, and basic line type are implemented. Network-backed carrier and SIM-swap checks are being integrated; this page describes the intended workflow. Check current coverage before depending on a signal.
Contact records arrive with spaces, local dialing prefixes, and inconsistent country context. A formatting check can turn a valid national input into a canonical E.164 number or tell your application which input needs correction before it attempts a message.
For example, 021 555 0182 with default_country: "NZ" can be normalized to +64215550182. This is a formatting illustration, not a claim that this number is assigned or can receive SMS.
A practical workflow
- Capture country context
Ask for the country when accepting a national-format number. Preserve the original input for correction rather than guessing an ambiguous country.
- Normalize and validate
Request formatting and validation with checks: []. Store the canonical E.164 value alongside the validation outcome.
- Add type when it helps
Request basic line type for numbering-plan context. Handle ambiguous or unsupported types explicitly; do not assume every mobile-looking number is textable.
- Verify before relying on reachability
Use a separate, appropriate delivery or possession check when required. Reassess time-sensitive network signals at the point of use.
What this can improve
Consistent numbers make it easier to match duplicate records, pass a predictable format between systems, and return useful correction messages. Validation can prevent an obvious input error from reaching a downstream messaging provider.
Formatting does not establish consent to contact someone, remove suppression-list obligations, or guarantee deliverability. A number can be structurally valid and disconnected, reassigned, or unable to receive your chosen message.
Build with the right scope
Use the quickstart for request syntax and the validation guide for possible versus valid numbers. Enhanced line type and current carrier are separate optional checks as supply becomes available.
Before live approval, developer queries are limited to their own verified number. Bulk contact-list processing requires approved live access and an appropriate basis for the customer data.