Phone validation
Validate numbers before you spend on SMS and WhatsApp
CampaignHQ validates numbers on secure infrastructure to standardize formats, filter invalid entries, and distinguish mobile vs landline — so routing and deliverability decisions start clean.
Delivery
Secure cloud
Pricing
Ask sales
OTP?
Separate
Validation tells you whether a number looks deliverable and what kind of line it is — it does not prove the user controls that number. Use OTP or WhatsApp flows when you need proof of possession.
Where it fits in CampaignHQ
Same pattern as email verification: clean data at capture and before large sends — wired into CampaignHQ SMS and WhatsApp workflows.
In the platform
Lists, signup, and journeys
- Validate on import and periodic CRM sync
- Catch fake or malformed signup numbers early
- Segment mobile vs landline before SMS vs voice routes
- Normalize to E.164 for WhatsApp and SMS APIs
Developers
API-first validation
Call validation from your services behind authentication — CampaignHQ exposes APIs suited for signup flows, imports, and messaging pipelines without exposing credentials in the browser.
- Pass PhoneNumber + optional IsoCountryCode
- Returns PhoneType, Carrier, Country, CleansedPhoneNumberE164
- Ideal for microservices and custom signup backends
How validation works
Step 01
Collect or upload numbers
From forms, imports, or your CRM — optionally pass ISO country for ambiguous inputs.
Step 02
Validate server-side
Our backend checks validity, type (mobile/landline/VoIP), and enriches carrier and geography where available.
Step 03
Use cleansed E.164
Route SMS and WhatsApp sends using standardized numbers and safer audience splits.
Example response (illustrative)
{
"PhoneType": "MOBILE",
"Carrier": "Airtel",
"Country": "India",
"CleansedPhoneNumberE164": "+919876543210"
}Exact fields can vary by region and integration; map responses in your backend against our API contract when you wire validation.
What you get from each validation
Pricing
Interested in phone validation volume, packaging with SMS and WhatsApp, or enterprise terms? Talk to sales — we'll align pricing with how you send and how often you validate.
Validation stays behind your authenticated backend
We never ask end users to embed secrets in the browser — integrate through CampaignHQ so credentials stay server-side.
Reduce wasted SMS spend
Drop obviously invalid numbers before carrier billing on SMS and WhatsApp.
Faster list hygiene
Automate validation in pipelines instead of manual spreadsheet checks.
Multi-channel ready
Validation sits alongside email, SMS, and WhatsApp — one workflow for outreach and hygiene.
Frequently asked questions
Is this the same as OTP verification?
No. Validation checks number metadata, formatting, and network signals. It does not prove the user owns the phone. For ownership, use SMS OTP or WhatsApp verification flows.
How is this billed?
Contact sales for packaging and volume pricing that fits your workspace — including validation alongside SMS and WhatsApp.
Can we validate numbers in bulk?
Yes. Use validation in list import pipelines, CRM sync jobs, or before high-volume SMS and WhatsApp campaigns to reduce wasted sends.