How US Phone Validation Works — Real-Time Carrier Lookup

US phone validation is a real-time carrier database query — not a format check. Here is exactly what happens when you validate a number, and how to integrate it into a TCPA-compliant workflow.

The Technical Process

Step 1 — Number Normalisation

The input number is normalised to E.164 format (+1XXXXXXXXXX for US and Canada), stripping any formatting characters (dashes, parentheses, spaces, country code prefixes). This ensures the number can be matched against carrier records regardless of how it was entered.

Step 2 — Carrier Database Query

The normalised number is queried against live carrier registration databases — not a static lookup table. This is what makes real-time phone validation different from format checking. The query determines:

• Whether the number is assigned to a subscriber (valid)
• Whether the subscriber account is currently active
• Which carrier currently holds the number
• Whether the number has been ported from another carrier
• The line type (mobile, landline, VoIP, toll-free, prepaid)

Step 3 — DNC & TCPA Litigant Check

The number is cross-referenced against the FTC Federal Do Not Call Registry and a database of known TCPA litigants. These checks run in parallel with the carrier query, adding no meaningful latency to the overall response time.

Step 4 — Geographic Data Derivation

City, state, ZIP code, area code, and time zone are derived from the number’s NPA-NXX (area code + exchange prefix) using NANP geographic data. Note: for ported numbers, geographic data reflects the original area, not the subscriber’s current location.

Step 5 — JSON Response

All data is returned in a single JSON response in under 1 second:

{
  "valid": true,
  "active": true,
  "line_type": "Mobile",
  "carrier": "T-Mobile",
  "original_carrier": "AT&T",
  "ported": true,
  "dnc": false,
  "tcpa_litigant": false,
  "city": "Chicago",
  "state": "IL",
  "zip": "60601",
  "timezone": "America/Chicago"
}

Building a TCPA-Compliant Calling Workflow

The Decision Tree

Use the validation response to gate every outbound contact decision:

1. active = false → Remove from list. Do not dial. No possibility of connection.
2. dnc = true → Suppress from outbound. Tag record in CRM. Do not call without prior written consent on file.
3. tcpa_litigant = true → Escalate to compliance review before any contact. High litigation risk.
4. line_type = VoIP → Flag for review. May be valid, but evaluate against your lead quality criteria.
5. line_type = Mobile AND dnc = false AND active = true → Eligible for autodialed calls and SMS, subject to consent on file.
6. line_type = Landline AND active = true → Eligible for manual outbound calls. Not eligible for SMS.

Integration Points

• Web form — call the API at form submission, before the lead is saved
• CRM webhook — trigger validation when a new contact is created; write results to custom fields
• Pre-campaign check — batch-validate your segment before export to your dialer
• Dialer list upload — run CSV through the batch validator; filter before loading into your platform

Accuracy & Data Sources

Phone Validator US connects to real-time carrier data from US and Canadian telecommunications providers via SS7 network lookups and CNAM databases. Accuracy depends on carrier reporting — numbers ported very recently (within hours) may reflect the previous carrier until databases propagate. For bulk pre-campaign validation, running validation 24 hours before your campaign accounts for any propagation delay.