How to check whether a number is on WhatsApp
There are two different checks and they answer different questions. Format validation tells you whether a number is well-formed for its country — it is instant and free, and catches most bad data. Checking whether the number is actually registered on WhatsApp requires opening a chat with it through a connected session, so it is slow and counts as activity on your account. Clean formatting first, then verify selectively.
Two checks, two questions
| Format validation | WhatsApp registration check | |
|---|---|---|
| Answers | Is this a plausible number for its country? | Does this number have a WhatsApp account? |
| Speed | Instant, thousands at a time | Seconds per number |
| Needs a connected device | No | Yes |
| Counts as account activity | No | Yes |
| Catches | Missing country codes, wrong digit counts, junk data | Numbers that exist but never installed WhatsApp |
Format validation eliminates most of the failures in a typical imported list. The registration check is for the residue.
Step 1 — Fix the formatting
BuzzRelay validates numbers on import using a full international numbering database, so it knows how many digits each country's numbers should have and which prefixes exist. Anything that cannot be parsed is flagged before it reaches a campaign.
The default phone region setting (Settings, default IN) decides how to read numbers with no country code. A list of local numbers written as 9876543210 is interpreted using that region, so set it to wherever most of your contacts are before importing.
Store numbers in full international format — +919876543210 — and the default region stops mattering. This is worth doing at the spreadsheet stage if your list spans countries, because one region setting cannot be right for all of them.
The commonest problems in an imported list, in order:
- Missing country code on a mixed-country list.
- A leading zero kept from local dialling (
09876543210). - Excel having stripped the leading
+, or turned a long number into scientific notation. - Landlines, which will never be on WhatsApp.
- Spaces, dashes and brackets — harmless, these are normalised automatically.
Format the phone column as Text in Excel before saving. A number column silently drops the leading + and can convert long numbers to scientific notation, which is the single most common cause of a broken import. See Import contacts from Excel.
Step 2 — Check WhatsApp registration
A well-formed number still may not be on WhatsApp. To check, BuzzRelay opens a chat with that number through a connected device's session: if the chat opens, the number is registered; if WhatsApp rejects it, it is not.
Right-click a contact in Contacts and choose Validate on WhatsApp. The result appears as a status against the contact:
| Status | Meaning |
|---|---|
| Valid | A chat opened — the number is registered. |
| Invalid | WhatsApp rejected the number — no account. |
| Unknown | Inconclusive: a slow page, a dropped session, or a timeout. Re-check later; do not treat it as invalid. |
You can also mark a contact valid or invalid by hand from the same menu, which is useful when you already know the answer and do not want to spend a check on it.
Do not bulk-validate a large list. Each check is a real interaction with WhatsApp from your account. Running thousands of them back to back is exactly the automated pattern that gets numbers restricted — and it is a particularly bad pattern, because opening many chats that do not exist looks like number harvesting. Validate selectively, not as a routine pre-campaign step.
A better approach than mass validation
For most lists, checking every number in advance is not worth the risk or the time. Let the campaign tell you instead:
- Clean the formatting on import — this removes the bulk of the failures.
- Run the campaign normally.
- Export the campaign log from Analytics.
- Numbers that failed with a "not on WhatsApp" style result are your invalid ones.
- Mark or remove them so future campaigns skip them.
This costs you nothing extra: the send attempt was going to happen anyway, and you get the same information from it.
Be wary of online "WhatsApp number checker" services. Uploading your customer list to a third party is a data-protection problem in its own right, and many such services work by running exactly the mass-checking pattern described above — from numbers they control, until those get banned. See Is bulk WhatsApp messaging legal?
Why invalid numbers matter
Beyond wasted sends, a high proportion of failures in a campaign is itself a risk signal. An account repeatedly attempting to message numbers that do not exist looks like it is working through a harvested list — which is usually what is happening. Keeping your list clean protects the number as well as your reporting.
Frequently asked questions
How can I check if a number is on WhatsApp?
In BuzzRelay, right-click a contact and choose Validate on WhatsApp. It opens a chat with that number through a connected device: if the chat opens the number is registered, if WhatsApp rejects it there is no account, and an inconclusive result is reported as unknown rather than invalid.
Can I validate thousands of numbers at once?
You should not. Each check is a real interaction with WhatsApp from your account, and running thousands back to back looks like number harvesting, which is one of the patterns most likely to get a number restricted. Clean the formatting on import and let the campaign log identify the invalid numbers instead.
Why do my imported numbers fail even though they look correct?
Usually Excel formatting. A phone column formatted as a number drops the leading plus sign and can convert long numbers to scientific notation. Format the column as Text before saving, and prefer full international format such as +919876543210.
What does the default phone region setting do?
It tells BuzzRelay which country to assume for numbers written without a country code, and defaults to IN. If your list spans several countries, store every number in full international format instead, because one region setting cannot be correct for all of them.
Last updated: