Phone number validation: what it is, how it works, and why your data depends on it
Every phone number in your database is either an asset or a liability. A validated mobile number that connects to a decision-maker generates pipeline. A disconnected number, a landline mislabeled as mobile, or a number that rings to the wrong person wastes a dial, damages sender reputation (for SMS), and erodes rep confidence in the data.
Phone number validation is the process of confirming that a phone number is syntactically correct, actively in service, and reachable at the intended type (mobile, landline, VOIP). For B2B sales teams — especially those doing cold outbound — validation is what separates a dial list from a contact list.
This guide covers what phone number validation means, how it works technically, the four business use cases where it matters, how to validate numbers at scale, and what to look for in a validation service.
Phone number validation vs. phone number verification
These terms are used interchangeably. They shouldn't be.
Validation confirms the number is technically correct and currently active. It answers: is this number real, is it in service, and what type of line is it (mobile, landline, VOIP)?
Verification confirms the number belongs to the intended person. It answers: does this number reach John Smith, the owner of Smith's Plumbing?
Validation is automated and scalable — you can validate millions of numbers through API calls. Verification requires human interaction — someone calls the number and confirms identity.
Most "phone validation" services deliver validation, not verification. They tell you the number is active and mobile; they don't tell you who picks up. That last mile — confirming identity — requires either a live dial or a provider that builds verification into their data collection process.
How phone number validation works under the hood
Step 1: Syntax and format check
The first validation layer checks whether the number conforms to the correct format for its country:
- Correct country code (e.g., +1 for US/Canada)
- Correct number length (10 digits for US numbers)
- Valid area code- No impossible digit combinations
Google's open-source library libphonenumber handles this layer and is used by most validation services as the foundation. It validates format against the International Telecommunication Union's (ITU) numbering plan database.
Step 2: Carrier lookup
A carrier lookup identifies which telecommunications provider owns the number and what type of line it is:
- Mobile: Cell phone on a mobile carrier (AT&T, Verizon, T-Mobile)
- Landline: Fixed line, typically at a physical location- VOIP: Voice over IP (Google Voice, RingCentral, Vonage)
- Toll-free: 800/888/877 numbers
Carrier data comes from the Number Portability Administration Center (NPAC) in the US, which maintains the master database of number assignments and port histories.
Why this matters for sales teams: Mobile numbers connect to the person. Landlines connect to the office (or nobody, after hours). VOIP numbers may or may not be actively monitored. Knowing the line type before dialing lets reps prioritize mobile numbers — where connect rates are 3-4x higher than landlines.
Step 3: HLR (Home Location Register) query
An HLR query pings the mobile carrier's database to check whether the number is:
- Active: Currently registered to a device and able to receive calls/SMS
- Inactive/deactivated: No longer in service
- Roaming: Active but on a different network (relevant for international)
HLR queries are the most technically reliable validation method for mobile numbers. They return real-time status directly from the carrier network. The limitation: HLR queries work on mobile numbers only (not landlines or VOIP) and cost $0.005-0.01 per query at scale.
Step 4: CNAM (Caller Name) lookup
A CNAM lookup returns the name associated with the phone number in carrier databases. For business lines, this often returns the business name. For personal mobiles, it may return the account holder's name.
CNAM is useful for validation — confirming the number is associated with the expected business or person — but coverage varies. Not all carriers provide CNAM data, and the name may be outdated.
4 business use cases
Use case 1: Outbound sales (cold calling)
The highest-impact use case. Sales teams running cold outbound need validated mobile numbers for decision-makers. The math:
- Unvalidated list: 20-30% of numbers are disconnected, wrong type, or unreachable. Reps burn 2-3 hours/day dialing dead numbers.
- Validated list: 90%+ of numbers are confirmed active mobiles. Reps spend dial time on reachable contacts.
But validation only solves the quality problem — not the coverage problem. If your enrichment provider returns mobile numbers for only 15-20% of your target accounts, validation on those numbers confirms they're good, but 80% of your accounts still have no number to validate.
As one retail marketing lead at a major ecommerce platform described their enrichment output: "57 contacts provided, 20% of the accounts have a decision maker mobile number. The other 80% have no way to reach the owner by phone."
Validation confirms the 20% is accurate. Coverage solves the other 80%.
Use case 2: SMS deliverability
SMS campaigns require mobile numbers (not landlines, not VOIP). Sending SMS to a landline wastes the message and the spend. Carrier lookup identifies mobile vs. non-mobile, preventing wasted sends.
Additional SMS considerations:
- TCPA compliance: Cold SMS to mobile numbers has specific legal requirements. Consult your compliance team regarding consent and opt-in obligations.
- 10DLC registration: Business SMS through 10-digit long codes requires carrier registration. Validation confirms the recipient number is SMS-capable before registration costs are incurred.
- VOIP filtering: Some SMS platforms don't deliver to VOIP numbers. Carrier lookup identifies VOIP numbers for separate handling.
Use case 3: Fraud prevention
For businesses that use phone numbers as identity verification (banks, fintech, e-commerce), validation detects:
- Disposable/temporary numbers (prepaid burner phones)
- VOIP numbers used to mask identity- Numbers recently ported (potential SIM swap fraud)
- Numbers registered in unexpected geographies
Use case 4: CRM data quality
Phone numbers decay. People change carriers, disconnect numbers, or let business lines lapse. Periodic validation across your CRM identifies stale numbers before reps encounter them:
- Flag disconnected numbers for removal or re-enrichment- Identify landlines mislabeled as mobile- Detect VOIP numbers in the mobile field- Measure overall database phone health (% active, % disconnected, % wrong type)
How to validate phone numbers
Free online validation
Services like NumVerify, AbstractAPI, and PhoneValidator offer free or low-cost single-number lookups. Useful for spot-checking individual numbers; not practical for bulk validation.
Bulk validation services
For lists of 1,000+ numbers:
- Twilio Lookup API: Carrier identification, line type detection, caller name. $0.005/query for carrier, $0.01 for CNAM.
- Telnyx: Number validation with carrier and line type data. Competitive per-query pricing.
- NumVerify: Bulk validation API with format, carrier, and line type.
- Ekata (Mastercard): Identity verification including phone validation. Enterprise-grade.
API integration for real-time validation
For validating numbers as they enter your system (form submissions, lead imports):
- Form field captures phone number
- API call validates format, carrier, and line type in real time
- Invalid or non-mobile numbers are flagged or rejected before entering the CRM
- Valid mobile numbers proceed to lead routing
Most validation APIs respond in under 500ms — fast enough for real-time form validation without user-perceived delay.
Google's libphonenumber
Google's open-source library handles format validation (not carrier or activity status):
- Validates format against ITU numbering plans
- Identifies country and region
- Formats numbers to E.164 international standard
- Available in Java, JavaScript, C++, Python, and PHP
Use libphonenumber as the first validation layer (format check), then carrier/HLR services for deeper validation.
What to look for in a validation service
Accuracy
The service should correctly identify line type (mobile vs. landline vs. VOIP) and active status at least 95% of the time. Test against a sample of known numbers before committing.
Coverage
US, Canada, and international coverage vary by provider. If you're validating US numbers only, most providers are adequate. International validation requires a provider with carrier relationships in target countries.
Speed
Real-time validation requires sub-second response times. Bulk validation should process 10,000+ numbers per hour. Latency during HLR queries varies — some carriers respond instantly, others take seconds.
Data freshness
Number portability (people switching carriers) means carrier data changes daily. The validation service should use real-time or near-real-time carrier lookups, not cached databases from last month.
Compliance
Ensure the service complies with TCPA regulations regarding automated queries. Some validation methods (particularly those that ring the number briefly) have regulatory implications. API-based carrier lookups are generally compliant; "ping" methods may not be.
Cost
Typical pricing:
- Format validation: free (libphonenumber)
- Carrier/line type lookup: $0.003-0.01/query
- HLR query (mobile active status): $0.005-0.015/query
- CNAM lookup: $0.01-0.03/query
- Full validation (format + carrier + HLR + CNAM): $0.02-0.05/query
At scale (100,000+ validations), negotiate volume pricing. Most providers offer tiered plans.
Best practices
Validate before you dial
Run your entire dial list through validation before any outbound campaign. A 30-minute validation run saves hours of wasted dials on disconnected numbers.
Validate on import
Every list that enters your CRM — purchased lists, event attendees, enrichment imports — should pass through validation before loading. Prevent bad numbers from entering the system rather than cleaning them out later.
Re-validate quarterly
Phone numbers change. Re-validate your active CRM contacts every 90 days. Flag numbers that have changed status (active → disconnected) for re-enrichment.
Prioritize mobile over landline
For outbound sales, mobile numbers generate 3-4x higher connect rates than business landlines. Use carrier lookup to identify and prioritize mobile numbers in your dialing sequence.
Track validation metrics
- % mobile: What proportion of your phone data is verified mobile vs. landline vs. VOIP?
- % active: What proportion is confirmed in service?
- Disconnect rate over time: Is your data decaying? If 10% of numbers disconnect per quarter, your refresh cadence needs to match.
The coverage problem validation can't solve
Validation tells you whether a phone number is good. It can't create a phone number that doesn't exist in your database.
For local business verticals, the primary challenge isn't validation — it's coverage. Traditional enrichment providers deliver decision-maker mobile numbers for only 15-20% of local business accounts. There's nothing to validate on the other 80%.
As one sales operations note from a hospitality technology platform documented: with their existing provider, phone numbers were "50% mobile." After switching to a provider built for local business data: "100% mobile, 85% accuracy."
The validation question becomes relevant after you've solved the coverage problem — when you have mobile numbers and need to confirm they're active and accurate before loading them into your dialer.
For teams selling to local businesses, the sequence is:
- Coverage first: Get decision-maker mobile numbers from a provider that sources from licensing databases, business registrations, and other non-LinkedIn data
- Validation second: Confirm the numbers are active, mobile, and accurately formatted
- Outbound third: Dial with confidence that the number reaches the right person
FAQ
What is phone number validation?
Phone number validation confirms that a phone number is correctly formatted, currently in service, and identifies the line type (mobile, landline, VOIP). It's the automated process of checking a number before you use it.
What's the difference between validation and verification?
Validation confirms the number is technically correct and active (automated, scalable). Verification confirms it belongs to the intended person (requires human confirmation, not scalable). Most services provide validation, not verification.
How much does phone number validation cost?
Format validation is free (Google's libphonenumber). Carrier and line type lookups cost $0.003-0.01 per query. Full validation (format + carrier + HLR + CNAM) costs $0.02-0.05 per query. Volume discounts are available for 100,000+ validations.
How often should I re-validate phone numbers?
Every 90 days for active outbound lists. Phone numbers disconnect, port to new carriers, and change status continuously. Annual validation is insufficient — significant decay happens within a single quarter.
Can I validate phone numbers for free?
Format validation is free using Google's libphonenumber library. Carrier lookup and active status checking require paid services, though some providers offer free tiers for low-volume testing (50-100 numbers/month).
Phone number validation ensures the numbers in your database are real, active, and correctly typed. But validation solves data quality — not data coverage. If your enrichment provider returns mobile numbers for only 15-20% of your target accounts, the priority is coverage first, validation second. Get the numbers, then confirm they work.
