On this page
A WhatsApp Business account check tells you whether a phone number has a WhatsApp account and, if it does, whether that account was set up as a business account. It doesn't tell you who owns the number, whether the business is real, or anything about its profile. Used with that in mind, the flag is a useful signal for B2B lead qualification and support routing. This post explains what the flag means, where it falls short and how to use it responsibly.
How is a WhatsApp Business account different from a personal one?
Both are WhatsApp accounts tied to one phone number. The difference is how they were set up and what the owner can do with them.
WhatsApp launched the WhatsApp Business app on 18 January 2018 as a free Android app for small businesses. The launch post listed business profiles (description, e-mail or store address, website), messaging tools such as quick replies and away messages, and an account type: people would know they were talking to a business because it would be listed as a Business Account (WhatsApp, 2018).
Today WhatsApp for Business has two main products:
- The WhatsApp Business app, used by small businesses on a phone, with a business profile and messaging tools (WhatsApp Business App).
- The WhatsApp Business Platform, which WhatsApp describes as enterprise-level WhatsApp APIs that businesses can integrate with back-end systems such as a CRM (WhatsApp Business Platform).
The check reports on the account registered to the number, so when it says an account exists, the business flag tells you which kind it is.
What does the business flag mean?
It means the account behind the number is configured as a business account. Nothing more.
MobileValidate's WhatsApp Business check (whatsapp.business) returns two answers in one result:
registered | attributes.business | Meaning |
|---|---|---|
true | true | A WhatsApp Business account exists |
true | false | A regular (personal) WhatsApp account exists |
true | absent (null in the v1 whatsapp object) | An account exists; the business flag couldn't be determined this time |
false | ignore (may be false) | Conclusive: no WhatsApp account |
null | — | Unknown: no conclusive answer; reason explains why |
The business check also answers the plain registration question. If you ask for both whatsapp and whatsapp.business, the API runs only whatsapp.business and you pay for one check per number. You're not charged for inconclusive results (unknown, unsupported country, timeout, invalid, duplicate).
What are the limits of the business flag?
The flag describes a configuration choice made by whoever set up the account. Read it with these limits in mind:
- It's not verification. Anyone can install the Business app. A scammer can create a business account as easily as a bakery can. Official confirmation of a business identity is a separate matter. The 2018 launch post already distinguished plain business accounts from "Confirmed Accounts", where the account phone number had been confirmed to match the business phone number (WhatsApp, 2018). Our check doesn't report any such confirmation.
- Many businesses use personal accounts. Sole traders, freelancers and small firms often run their business from a personal WhatsApp account.
business: falsedoesn't mean "not a business". - Some business accounts belong to individuals. People sometimes choose the Business app for its features, for example away messages, without running a company.
- It's a point-in-time answer. Accounts are created, switched and deleted, and numbers get reassigned. Every answer carries
checked_at. - No profile data. The check never returns the business name, description, catalog, photo or any other profile field. It can't tell you which business it is.
So treat the flag as one piece of evidence that's consistent (or inconsistent) with what you already know, never as proof.
Why can the flag be null in real time?
Because the business flag is harder to determine quickly than registration itself. In real-time lookups, a conclusive registered: true can come back without the flag. That result is still a conclusive registration answer and is billed as one.
Design for it:
- If the flag only adds context, for example in a support-routing rule, treat a missing flag as "not known" and fall back to your default route.
- If the flag is essential, for example when qualifying a list of B2B leads, run the numbers as a bulk job, where the flag is filled more reliably.
- Never convert a missing flag into
false.nullmeans unknown.
What does a request look like?
With a test key, +447700900006 is the documented business account and the other test numbers behave as usual. This is a real test-mode request:
curl https://api.mobilevalidate.com/v1/lookup \
-H "Authorization: Bearer $MOBILEVALIDATE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"numbers": ["+447700900006", "+447700900001", "+447700900002", "+447700900003"],
"checks": ["whatsapp.business"], "wait": 5}'The four whatsapp.business results, trimmed:
{"status": "completed", "registered": true, "attributes": {"business": true}, "confidence": "high", "billed": false, "reason": null}
{"status": "completed", "registered": true, "attributes": {"business": false}, "confidence": "high", "billed": false, "reason": null}
{"status": "completed", "registered": false, "attributes": {"business": false}, "confidence": "high", "billed": false, "reason": null}
{"status": "unknown", "registered": null, "attributes": null, "confidence": null, "billed": false, "reason": "UPSTREAM_TIMEOUT"}And the summary for the request:
"by_service": {"whatsapp.business": {"completed": 3, "registered": 2, "not_registered": 1, "unknown": 1, "pending": 0}}Test keys return fixed answers and never bill. Every result also carries checked_at. See test mode for all test numbers, and our WhatsApp API guide for polling, pending answers and code in Node and Python.
How can B2B teams use it for lead qualification?
As one consistency check on inbound leads, next to the checks you already do. A lead that fills in your demo form gives you a company name, a work e-mail and a phone number. The business flag helps you see whether the number fits the story:
| Lead claims | Check result | Reading | Suggested action |
|---|---|---|---|
| A company, gives a company mobile | business: true | Consistent | Normal routing |
| A company, gives a company mobile | business: false | Common for small firms and staff phones | Normal routing; check the e-mail domain |
| A company | registered: false | Neutral in markets where WhatsApp is rare | Normal routing; see channel by country |
| A company | registered: false, plus a disposable e-mail and a voip line | Several weak signals agree | Verify before a salesperson spends time |
| An individual consumer | business: true | Possibly a business owner or a mis-filed lead | Ask in the first reply, don't assume |
Combine the flag with the carrier lookup and e-mail checks, as described in lead verification. The value is in spotting leads that don't hang together, not in ranking leads by account type.
How can support teams use it for routing?
When a number contacts you, knowing whether it's run as a business account can help you route the conversation:
- Partner and supplier queues. An inbound contact from a business account that matches a known partner number can go to the account team rather than consumer support.
- Impersonation reports. Customers forward messages from numbers claiming to be your company. Recording whether the reported number is a business account helps your fraud team triage. Scammers often use business accounts to look official, so a
trueflag is not reassurance. Combine it with spam reputation where available. - Channel choice for replies. If a customer who opted in to WhatsApp updates writes from a business account, they may be contacting you for their company. That can change which team and which templates should answer.
Keep these rules explainable. An agent should see "business account: yes, checked 2 hours ago", not an unexplained score.
What are the responsible-use rules?
The business flag is about a number that usually belongs to, or is used by, a person. Use it only where you have a clear reason.
- Check numbers you already hold for a legitimate purpose: leads who contacted you, sellers applying to your platform, numbers reported to your fraud team. Under the GDPR, you need a lawful basis (Article 6) and should keep only what you need (Article 5(1)(c)): the flag and its date, not the raw response.
- Don't use it to find people to message. WhatsApp's Business Messaging Policy says businesses may only contact people on WhatsApp if they gave you their mobile phone number and you received opt-in permission to message them. A business flag is not consent, and a list of "numbers with business accounts" is not a marketing list.
- Respect objections. People can object through our opt-out form. Suppressed numbers are skipped and never charged.
Our acceptable use policy forbids unsolicited messaging, profiling and scanning number ranges, and requests with 20 or more consecutive numbers are refused as suspected_enumeration. WhatsApp is named here descriptively. MobileValidate is not affiliated with WhatsApp or Meta.
What are the key takeaways?
- The WhatsApp Business check answers two questions: does the number have a WhatsApp account, and is it a business account.
- The flag describes how the account is set up. It isn't verification, it doesn't identify the business, and it returns no profile data.
business: falsedoesn't mean "not a business", andbusiness: truedoesn't mean "trustworthy".- In real time the flag can be missing next to a conclusive
registeredanswer. Treat it as unknown, and use bulk jobs when the flag is essential. - Use it as a consistency signal for B2B leads and as context for support and fraud routing, next to carrier and e-mail checks.
- It's not consent. Message only people who opted in, and check only numbers you have a reason to process. Details and pricing are on the WhatsApp Business check page.
Sources
- Introducing the WhatsApp Business App (archived copy) — WhatsApp, 2018
- WhatsApp Business Messaging Policy — WhatsApp, 2026
- WhatsApp Business App — WhatsApp, 2026
- WhatsApp Business Platform — WhatsApp, 2026
- General Data Protection Regulation (EU) 2016/679 — European Union, 2016
Frequently asked questions
Does a WhatsApp Business account prove that a number belongs to a real company?
No. Anyone can install the WhatsApp Business app and create a business account. The flag says how the account is set up, not who owns the number or whether the business is genuine.
Why is the business flag null even though registered is true?
The account check was conclusive, but the business flag could not be determined for that answer. This happens more often in real-time lookups. The result still counts as a conclusive registration answer.
Does the check return the business name or profile?
No. The result contains registered and the business flag only. Business names, descriptions, photos, catalogs and other profile details are never returned.
Can I use the flag to build a list of businesses to message on WhatsApp?
No. WhatsApp's business messaging policy requires that people gave you their number and opted in before you contact them, and our acceptable use policy forbids finding recipients for unsolicited messages.
Should I run the business check in real time or in bulk?
Both work. The business flag is filled more reliably in bulk jobs, so if the flag matters more than speed, for example when qualifying a lead list, run it as a job.
Related services and guides
More from the blog
All articlesDevelopers
How to check if a phone number is on WhatsApp with an API
How a WhatsApp registration check works, what registered, not registered and unknown mean, and how to call it responsibly from cURL, Node and Python.
8 min read
Deliverability
How to choose a messaging channel by country
WhatsApp, Telegram, Viber, LINE, Zalo, RCS or SMS? How to pick a channel per country for messages customers expect, and measure it on your own base.
6 min read
Guides
Messaging-app registration checks: a guide for every app
What a registration check tells you for WhatsApp, Telegram, Viber, Signal, iMessage, RCS, LINE, Zalo and more: modes, unknowns, billing and consent.
8 min read


