The green tick beside a business name on WhatsApp is the single most misunderstood badge in messaging. It is not the checkmark you see during onboarding, it cannot be bought, and the majority of businesses that apply are rejected the first time โ usually for reasons that have nothing to do with how their WhatsApp account is configured. The badge sits at the intersection of two systems people routinely conflate: the technical WhatsApp Business Platform (the API, your phone number, your display name) and Meta's editorial judgement about whether your brand is genuinely notable. You can do everything right on the first and still fail on the second.
This guide breaks the badge down the way an engineer would: what state your account is actually in, what Meta is checking at each gate, the exact application path, the evidence that moves the needle, and what the realistic options are when (not if) you get a "no". We have cross-referenced Meta's own developer and business documentation, the public WhatsApp Business policies, and the behaviour reported by businesses and Business Solution Providers (BSPs) who file these requests routinely.
What the green tick actually means
The green tick denotes an Official Business Account (OBA). It tells users that Meta has confirmed this is the authentic, notable presence of a well-known brand. It is granted entirely at Meta's discretion, and the deciding factor is brand notability โ not your technical setup, not how much you spend, and not how legitimate your company is.
Two things the green tick is emphatically not:
- It is not display-name approval. When you onboard to the WhatsApp Business Platform, Meta reviews and approves your display name. A successful display-name review gives you a verified business name and a standard (grey) presentation in the chat header. That is a separate, lower gate. The green tick is layered on top of it.
- It is not a toggle. There is no setting, no paid upgrade, no checkbox. You request OBA status, and Meta evaluates whether your brand clears the notability bar. The answer is binary and the reasoning is rarely detailed.
Functionally, once granted, the badge surfaces your business name (rather than a raw phone number) in chat lists, headers, and contact cards, and it acts as an anti-impersonation trust signal. In practice that trust signal nudges reply and open rates upward, because it removes the "is this actually them?" hesitation โ the same hesitation that quietly suppresses performance on cold outreach and WhatsApp broadcast software campaigns.
Account states, in order
It helps to think of your account as moving through discrete states. Most businesses stall at state 3 and never reach state 4 โ and that is fine, because everything that generates revenue is already unlocked at state 3.
| Account state | Send templates / broadcast | Automation & API | Verified display name | Green tick (OBA) |
|---|---|---|---|---|
| Consumer Business app | ~ | โ | โ | โ |
| API, unverified | ~ | โ | โ | โ |
| โ API + business verified | โ | โ | โ | โ |
| API + OBA granted | โ | โ | โ | โ |
The takeaway from that matrix is the most important thing in this article: the green tick gates nothing operational. If your goal is to message customers, automate replies, and run campaigns, you are fully equipped the moment you reach a verified API account.
Eligibility: what Meta is really checking
To be considered for OBA status you generally need all four of the following. The first three are mechanical and within your control. The fourth is the one that fails people.
- A WhatsApp Business Platform (API) account, connected to a Meta Business Manager. The standalone consumer WhatsApp Business app does not qualify. If you are not on the API yet, start with our walkthrough on how to set up the WhatsApp Business API.
- A verified Meta Business Manager. Business verification โ confirming your legal entity with registration documents โ is effectively a hard prerequisite. Meta will not grant OBA to an unverified business.
- A compliant display name. Your display name must satisfy WhatsApp's naming policy and match your real brand. You cannot bolt the green tick onto a name that is generic, misleading, or non-compliant.
- Notability. This is the decisive, fuzzy criterion. Meta wants evidence your brand is well-known and frequently referenced by independent, third-party sources โ major news coverage, widely-cited press, an established public footprint. Your own website, your own socials, and paid placements do not count. The bar is conceptually close to Wikipedia's notability standard: coverage about you, produced by people who are independent of you.
That fourth point is why small and mid-size businesses โ even excellent, profitable, well-run ones โ are routinely turned down. The green tick is reserved for brands with a genuine public profile, not merely brands that are legitimate. Legitimacy gets you a verified display name; fame gets you the tick.
How the four factors actually weigh
In our reading of approval and rejection patterns, the four criteria are not equal. The first three are pass/fail gates that simply have to be clean; notability is the analog dial that decides everything once the gates are passed.
How to apply, step by step
The mechanics are not hard. The evidence is. Work the gates in order, then make your notability case as strong as you honestly can.
- Complete business verification in Meta Business Manager (Security Center / Business Info). Submit legal documents โ business registration, address, and where requested a phone or domain โ that exactly match your registered entity. Mismatches between your trade name and registered name are a common, avoidable failure.
- Get your WhatsApp display name approved in WhatsApp Manager. Resolve any naming-policy flags here first. You cannot earn the green tick on a name that has not cleared display-name review.
- Submit the Official Business Account request. Depending on how your number was provisioned, this is filed through WhatsApp Manager / Business Manager, or your BSP files it on your behalf. Many BSPs expose a "request green tick / OBA" action in their console.
- Provide notability evidence. Attach links to independent press, news features, and reference material. Quality and independence beat quantity: three substantial features in recognised outlets outperform thirty directory listings and reposts.
- Wait for review. The outcome is binary โ approved or not โ and Meta frequently does not give a granular reason. If rejected, you typically can reapply later once your footprint has grown.
Working through an established BSP can smooth the mechanics โ verification, name approval, request filing โ and reputable providers will tell you honestly whether you have a realistic notability case. The major BSPs and aggregators (Twilio, 360dialog, and the WhatsApp-native platforms reviewed in our Twilio WhatsApp alternatives roundup) all handle OBA requests as routine plumbing. But no BSP can manufacture notability. Treat any vendor promising a guaranteed green tick as a red flag โ that guarantee is not theirs to make, because the decision is Meta's and Meta does not sell it.
What counts as notability evidence
The single biggest reason strong companies fail is submitting the wrong kind of proof. Meta is looking for third parties writing about you, unprompted. Here is the rough hierarchy, from strongest to weakest.
The most common rejection reasons
If you are turned down, it is almost always one (or several) of the following. The good news is that three of the five are fully fixable; only the first requires the slow work of actually becoming better-known.
| Rejection reason | What's really going on | Fix |
|---|---|---|
| Insufficient notability | Your brand isn't widely covered by independent sources | Build genuine press/PR presence over months, then reapply |
| Business not verified | Meta Business verification incomplete or documents mismatched | Complete verification with documents matching your legal entity exactly |
| Display-name policy issue | Name uses generic terms, mismatched brand, or prohibited content | Fix the name to comply and match your real brand, get it re-approved |
| Using the wrong product | Applying from the consumer Business app, not the API/Platform | Move to the WhatsApp Business Platform via a BSP |
| Thin or self-referential evidence | Submitted your own site/socials as proof of notability | Replace with independent third-party coverage |
Two of these โ verification mismatches and display-name issues โ are pure self-inflicted friction. Resolve them before you even think about the OBA request, because they will sink the application regardless of how notable you are.
What to do if you're rejected (or won't qualify)
Most businesses land here, and it genuinely is not a problem for day-to-day operations. The badge is a trust signal, not a capability gate.
- You can still run the full Business API. Send templates, automate conversations, broadcast, and build flows โ all without the green tick. Nothing in the messaging stack is locked behind OBA.
- You already have a verified display name. Through normal onboarding your business name presents correctly in most contexts, which delivers a large share of the trust benefit on its own.
- Build notability, then reapply. Earned press coverage, being cited in recognised publications, and a growing public footprint are the only durable path. Reapplying after your brand's profile expands is a legitimate, expected route โ not a workaround.
- Lean on other trust signals now. A complete business profile, a recognisable logo and consistent display name, a verified website, and โ most underrated โ prompt, human-quality responses do more for reply rates day to day than the badge ever will. This is where investing in your conversational layer pays off: see our guides to WhatsApp chatbots for customer support and WhatsApp CRM tools.
Where your effort actually pays back
If you score the levers available to a non-famous business, the badge is a poor place to spend energy relative to the things you fully control. Here is how we weigh the realistic options on the axes that matter.
A note on conversation costs (and why the badge is the wrong thing to optimise)
There is a deeper reason to stop fixating on the tick: it does nothing to change your unit economics. WhatsApp Business Platform billing runs on Meta's per-conversation model, where charges depend on the conversation category (marketing, utility, authentication, service) and the recipient's country โ independent of whether you carry the green tick. A badge will not lower your marketing-conversation rate by a cent.
If you want a lever that actually moves the spend line, it is conversation design and category discipline, not verification status. We cover the mechanics in reduce WhatsApp conversation costs, and you can confirm the current categories and rate structure in Meta's official WhatsApp pricing and platform docs. The point stands: optimise the thing on the invoice, not the thing on the header.
For broader tool selection once your foundations are clean โ broadcasting, CRM, support automation โ start from our WhatsApp marketing tools overview and the platform-specific writeups like the WATI review and respond.io review. The official channel rules themselves live in Meta's WhatsApp Business help center and the developer documentation, which are the only sources worth treating as authoritative when policy questions arise.
How we evaluated this
This is a guide, not a tool ranking, so there is no scored shortlist. Where we make claims about behaviour โ what each account state unlocks, what evidence Meta weighs, why applications fail โ we cross-referenced Meta's published WhatsApp Business Platform and developer documentation, the public WhatsApp naming and business policies, and the consistent reporting of BSPs and businesses who file OBA requests as routine work. The two weighting charts (decision weight and effort payback) are explicitly labelled qualitative: they reflect observed patterns, not a Meta-published rubric, because Meta does not publish one. Where exact figures would matter โ conversation pricing, in particular โ we link to Meta's live documentation rather than quoting numbers that drift.
Conclusion
The WhatsApp green tick is a brand-notability award wearing a verification badge's clothing. The technical prerequisites โ API access, a verified Business Manager, a compliant display name โ are necessary but never sufficient; the decision turns on whether independent sources establish your brand as notable. Get those fundamentals airtight, submit genuine third-party evidence, and treat a rejection as a signal to grow your public profile rather than a verdict on your business.
Above all, keep the badge in proportion. It gates nothing operational, it changes none of your conversation costs, and it is the lowest-control lever you have. The businesses that win on WhatsApp are not the ones with the tick โ they are the ones that reply fast, sound human, and design conversations that respect both the customer and the per-conversation invoice. And ignore anyone selling a guaranteed tick: Meta doesn't sell it, so neither can they.