Checking
One question: is this number on WhatsApp? Fast, but it trusts whatever data you feed it.
A validator answers two questions per contact: is this number structurally valid for its country, and is it actually on WhatsApp? Everything that fails is separated out before it costs you money or an agent’s time.
If you only ask “is this on WhatsApp?”, you inherit every formatting error already sitting in your CRM.
One question: is this number on WhatsApp? Fast, but it trusts whatever data you feed it.
Normalise, add country codes, reject impossible numbers, deduplicate, verify, then date-stamp the result.
Contact data decays continuously. A segment that was clean in January is not clean in June.
Normalising and deduplicating costs nothing and routinely removes 5–20% of a raw list. Doing it first makes the paid check both cheaper and more accurate.
Run in this order and each step makes the next one cheaper.
Strip spaces and stray text, convert local formats to full international, then deduplicate — after normalising, not before.
Now the yes/no lookup means something, because every number reaching it is structurally valid for its country.
Split into verified, unverified and invalid, and record when each contact was checked so you know when it goes stale.
The split is where the value is, because each segment gets treated differently afterwards.
Valid format, registered on WhatsApp, safe to contact. This is your campaign segment.
Valid number, no WhatsApp account. Route to SMS or calls — and keep this file as a permanent suppression list.
Structurally broken. Send back to the source for correction rather than paying to check it again.
Teams routinely delete the unverified file, then re-buy the same numbers three months later and pay to check them again. Keeping it means every future import can be filtered for free before a single paid check runs.
Same verification job, two different trade-offs. Both are ours.
Runs on your Windows machine. Files never leave your computer and one license covers unlimited checks — but verification runs through a logged-in WhatsApp account.
Runs server-side with no WhatsApp login at all, so no account is ever at risk. Priced at $1 per 40,000 numbers.
To verify numbers as they arrive — at signup, checkout or form submission — you need the API route rather than either UI.
Optional reading. Open only what applies to you.
A WhatsApp number is validated by confirming it is correctly formatted and registered on WhatsApp. Load your list into WhatsPro Turbo Filter and it normalises each number, drops impossible ones, checks registration, and flags which contacts are reachable — one number or thousands in bulk.
Most lists carry defects their owners have never looked at. Numbers stored without country codes. Local trunk prefixes left in place. Landlines mixed into a mobile list. Copy-paste duplicates written two different ways. Free-text like “call after 6pm” sitting in the number column.
Sending that straight into a checker wastes checks and produces misleading results — a number can come back “not on WhatsApp” purely because it was never formatted into something WhatsApp could recognise. Proper validation runs in a specific order:
People change numbers, abandon accounts and switch carriers continuously. A segment that verified cleanly in January is not clean in June.
Re-verify before every significant campaign, and treat anything older than 60 to 90 days as needing a fresh pass regardless of how good it looked last time. If you are validating through the API, cache each result with a timestamp and re-check on that schedule rather than on every send.
One number per row, full international format with the country dial code, duplicates removed, and no free text in the number column.
Formatting rules differ by country — most drop a leading zero, but Italy, Spain, India, Mexico and Poland have no trunk prefix to remove. The country reference has the rule and a worked example for each market.
No. Validation guarantees list quality, not delivery.
You still need consent, a compliant sending method, a warmed sender and relevant messaging. Validation removes one large category of waste — contacting people who were never reachable on the channel — but it does not replace campaign strategy, and it does not create a lawful basis to contact anyone. See our terms and privacy policy.
A tool that confirms each contact is both a structurally valid number for its country and actually registered on WhatsApp, then separates the failures out before you contact anyone.
Checking asks one question: is this on WhatsApp? Validating covers the surrounding data-quality work — normalising, adding country codes, rejecting impossible numbers, deduplicating and dating each verification.
Yes. Cloud verification runs server-side with no login, QR scan or linked device, so your number is never used and never at risk.
That depends entirely on your jurisdiction and how the list was collected. Verification is a data-hygiene step and does not create a lawful basis to contact anyone.
Tell us your list size, the countries involved and whether you need this automated. We will point you at the right option rather than the expensive one.
Cloud verification needs no WhatsApp account — $1 per 40,000 numbers.
The focused active/inactive lookup, if that is all you need right now.
Why account-based verification carries risk, and the no-login alternative.
Dial codes and per-country formatting rules for international lists.
Batching strategy and export handling for very large verification jobs.
Verify numbers automatically at the point they enter your system.
Step-by-step tutorial for preparing files and avoiding common mistakes.