The WhatsApp green tick: what it means and how to get it

The green tick beside a business name on WhatsApp indicates that Meta has confirmed the account belongs to the business it claims to represent. That is the whole of the claim. It is an identity assertion, not a quality endorsement, not a service rating, and not a statement that the business is reputable or well run.

This narrow meaning is worth holding onto, because most disappointment with the badge comes from expecting it to do more. It signals authenticity to a customer deciding whether the account messaging them is genuinely the airline, the bank or the retailer it appears to be. For a customer who has been targeted by impersonation attempts, that is genuinely valuable. For a business hoping the badge will improve how its messages perform, it is the wrong instrument.

Meta has revised both the criteria for the badge and where it appears more than once, and has at times connected official business status to its broader verification offerings. That history is the main reason advice about the green tick ages badly. The stable part is what the badge asserts; the process and prerequisites are worth reading from Meta's current documentation rather than from any account written earlier, including this one.

The badge does not raise messaging limits. Capacity is governed by the messaging limit ladder and the quality rating, both driven by sending history and recipient feedback. A verified business with poor recipient feedback is a verified business with a restricted number.

It does not improve deliverability. Template messages are delivered on the same basis regardless of badge status, and a badge does not exempt a message from the 24-hour window rule, from template approval, or from the consent requirement attached to marketing. It confers no relief from any policy.

It does not protect against template rejection or account restriction. Verification and template review are separate processes with separate criteria, and a verified business submitting a non-compliant template gets it rejected exactly as anyone else would. Nor does the badge substitute for business verification in Meta Business Manager, which is a distinct step that the badge process depends on rather than replaces.

What it does do is reduce a specific friction: the moment a customer wonders whether the account contacting them is real. Whether that friction is costing your business anything is the question worth asking before investing effort in the badge, and for many small businesses the honest answer is that it is not the binding constraint.

The badge sits at the end of a chain, and most refusals happen because something earlier in the chain is incomplete. A business needs a WhatsApp Business Account on the WhatsApp Business Platform, connected to a Meta Business Manager, with business verification completed. Business verification is its own process: Meta checks that the legal entity exists and that the person requesting is entitled to act for it, using official documentation and, typically, corroborating evidence such as a matching website and contact details.

Getting that documentary layer right is unglamorous and decisive. The business name on the registration documents, the name on the Business Manager, the name on the website and the display name on the WhatsApp account should tell a consistent story. Small discrepancies — a trading name in one place and a registered entity name in another, a website whose contact details do not match the submitted address — are the ordinary reason a verification stalls.

The display name matters separately, because WhatsApp has its own display name policy. A name that is a generic category rather than a business identity, or that includes promotional wording, creates a problem independent of whether the entity is verifiable. The name should be the name customers know the business by, matching the identity established everywhere else.

Refusals cluster into a few recognisable causes. Incomplete or inconsistent business verification is the most common: documents that do not match the submitted details, or an entity that cannot be corroborated from independent sources. A weak or absent public presence is another — verification leans on the business being findable and consistent outside Meta's own systems, so an entity with no website, no consistent listings and no independent references is harder to confirm regardless of whether it is legitimate.

Display name problems account for a further share, as does applying while an account has unresolved policy issues. An account under restriction, or with a poor quality rating, is not in a good position to be granted an identity endorsement.

A more mundane cause is applying too early. A newly created account with no sending history, an incomplete profile and a business verification still in progress is a request with little to assess. Completing business verification, filling in the profile properly, establishing a consistent presence and building some ordinary sending history first makes a materially stronger case than submitting immediately and appealing afterwards.

When a request is refused, the stated reason is the thing to work from. Resubmitting unchanged in the hope of a different outcome wastes time; fixing the named inconsistency does not.

For most small businesses the things that actually determine whether WhatsApp works as a channel sit entirely outside the verification process. A complete and accurate profile — business name, category, description, address, hours, website — does more for a customer's confidence than a badge does, and it is available immediately to anyone.

Consistency across surfaces does similar work. A customer who sees the same business name, the same logo and the same contact details on the website, on the invoice and on the WhatsApp profile has been given a coherent identity to trust. That coherence is also, not coincidentally, the evidence verification looks for, so building it serves both purposes.

Behaving well on the channel is the largest factor and the least discussed in the context of the badge. Answering inbound messages inside the window, messaging only people who consented, categorising templates honestly and keeping frequency reasonable is what preserves the account's ability to reach anyone. A verified badge on a restricted number is worth very little. An unbadged number with a green quality rating and a properly consented list is a working channel.

The badge is worth most where impersonation is a live risk or where the business asks customers to act on messages in ways that carry consequence — sending money, sharing a code, following a link to something that matters. In those situations a customer's ability to confirm the account is genuine has real value, and the effort is justified.

It is worth least where customers initiate the conversation, already know the business, and where the messages are ordinary confirmations and replies. A neighbourhood service business whose customers message it first, having found it by recommendation, is not losing anything to the absence of a badge.

The sequencing advice is the same either way. Complete business verification because it is a prerequisite for a range of capabilities and not only for the badge. Get the profile and the display name right. Build a consistent public presence. Establish a clean sending record. Then, if the badge still matters for your situation, request it from a position where the evidence supports the claim — and read Meta's current requirements at that point, since they have changed before and will change again.