WhatsApp Green Badge: What Meta Requires and When It Pays Off

WhatsApp Green Badge: What Meta Requires and When It Pays Off

There is no guaranteed path to the WhatsApp green badge. It is the indicator of an official business account, and Meta decides case by case, based mainly on brand notability and account health. A company cannot buy it or demand it. What you do control is preparation: a verified business, a well-configured number, a display name that matches your brand, and a support operation that does not generate reports from users.

Key takeaways

• The green badge marks an official business account. Meta grants it on its own criteria, with no guarantee of approval.
• Business verification, display name approval and the green badge are three different things, and only the first is a prerequisite you can fully control.
• The review tends to center on brand notability, consistency of information and account quality, and the rules can change. Always confirm in Meta's current documentation.
• For most small and mid-sized companies, the badge does not change how well support works. A clear flow, handoff to a human and a healthy number reputation matter more.
• Treat the badge as a possible result of a well-run operation, never as the goal of the project.

What the green badge is and what it is not

The green badge is a verification mark shown next to a company's name on WhatsApp. It signals that Meta has recognized the account as the official account of a brand. Someone who receives a message sees the indicator and understands they are talking to the real company, not to someone impersonating it.

The problem is that the market mixes up similar concepts. It helps to separate them:

• Business verification: a process in Meta's business portfolio where the company proves it exists, using documents and matching data. It is an administrative step and is needed to operate the API at scale. We cover it in Meta business verification for the WhatsApp API.
• Approved display name: the name the customer sees. Meta reviews whether it represents the company coherently. Having the name approved does not mean having the badge.
• Business account: the account is identified as a business, but without the official account mark. This is the normal state of many serious operations.
• Green badge: an additional recognition, granted at Meta's discretion.

Meta also offers other forms of verification and subscriptions across its products, and these programs change over time. So before deciding anything, read the official help page for the WhatsApp Business Platform and confirm what applies to your account today.

What Meta evaluates before granting the badge

Meta's documentation describes the official business account as a recognition tied to notable brands. In practical terms, the review tends to consider whether the brand is known and searched for by people, whether there is a consistent presence outside WhatsApp (your own website, social media, press mentions or independent sources), and whether the account information matches that presence.

To separate what is documented from what is a reading of practice, it is worth being transparent:

• Official documentation: Meta treats the badge as a recognition at its own discretion, with no promised timeline, no promised approval and no charge. The exact criteria and the request form can change, and the reliable source is always the current official page.
• Implementation experience: the signals that generally help are a verified business, a display name identical to the name the public knows the brand by, a website on your own domain, official channels that are consistent with each other, and a clean message quality history.
• Hypothesis: brands that are very well known in your region or segment have a better chance than small local brands, even well-run ones. This is not a published rule. It is a reasonable reading of the notability criterion.

Be wary of anyone who sells the badge as a service with a guaranteed result. If the decision belongs to Meta, nobody outside can ensure it. A legitimate intermediary can help with documentation and setup, but not with the decision.

How to prepare: a step-by-step plan

Even without a guarantee, there is preparation worth doing regardless of the badge, because it makes the account more solid. The order matters.

• Confirm your account type. If you use the WhatsApp Business app on a phone today and plan to integrate AI or a CRM, first understand what changes when moving to the API. The article on migrating a WhatsApp Business App number to the API covers what to prepare.
• Organize your Meta business portfolio with the correct company data (legal name, tax ID, address, website) and complete business verification.
• Set the display name to match the name the public uses, with no promotional additions, no improper capitalization and no generic terms.
• Turn on account protections, such as two-step verification, and restrict who has admin access.
• Make sure your website has its own domain, contact information, and the same visual identity and name used on WhatsApp.
• Operate for a period with quality: send outbound messages only to people who gave consent, use the right templates, and monitor reports and blocks. See WhatsApp outbound messages: templates, opt-in and best practices.
• Only then, check whether your account is eligible to request an official account, and apply through the path Meta indicates, without setting internal expectations about timing or outcome.

Notice that almost all of these steps serve any support operation. If the badge never comes, the work was not wasted.

When the badge is worth it and when it is not

A simple decision guide, in the form of questions:

• Is your brand widely known, and is there a real risk of scammers impersonating it on WhatsApp? In that case the badge has protective value, and the request deserves attention.
• Do your customers tend to distrust unexpected contact, such as billing, delivery, banking or health messages? The greater the distrust, the greater the benefit of a visible sign of authenticity.
• Does first contact come from outbound messages to people who do not yet know the company? The badge may help open rates, but the legal basis and consent matter more.
• Do customers come on their own, through the website, an ad or a referral? Then they already have context, and the badge changes little.
• Does your support still have a confusing flow, inconsistent answers or slow handoff to people? Fix that first. A badge on top of poor support only makes the frustration more visible.
• Is the company small or regional, with little press presence? The request will probably not be approved right now, and putting energy into it is a waste.

If most of your answers point to the last group, move ahead without the badge. If they point to a well-known brand and fraud risk, treat the request as a parallel track, not the center of the project.

Why the badge should not be the goal of a support project

The goal of a WhatsApp support project is to resolve the customer's request safely: answer what can be answered, collect what is missing, and pass to a person whatever requires judgment. The badge does none of these things.

There are three risks in chasing the badge as a goal:

• Priority drift. The team spends weeks on documentation and forms while the support flow, handoff rules and decision records are left for later.
• Dependence on an external decision. A project whose success depends on a yes from Meta is hostage to a timeline nobody controls.
• A false sense of security. The badge shows that the account is authentic, not that the support is good, nor that data use complies with Brazil's data protection law (LGPD). For personal data, consult the national data protection authority (ANPD) and define legal basis, retention and access.

Illustrative scenario: a regional clinic network wants the badge before launching an AI agent for scheduling. They spend a long time gathering press material and wait for an answer. Meanwhile, support continues through an ordinary number, with no conversation records and no handoff rule. The more prudent alternative would be to launch a pilot on a single flow, such as appointment confirmation and rescheduling, with a verified number, a coherent name, clear limits and a human owner. If the badge comes later, it is a bonus. If it does not, the pilot is already producing learning. For this kind of flow, see automatic appointment scheduling on WhatsApp with AI.

What really builds trust in the conversation

Customers trust a conversation because of signals that appear in every message, not only because of the icon next to the name. A practical checklist:

• The contact name matches the brand and the profile photo is the official one.
• The first message says who the person is talking to and what the channel does.
• When AI is involved, this is stated simply, and there is an easy way to reach a person.
• The company never asks for a password, an SMS code or data it does not need.
• Links point to the official domain.
• Outbound messages reach only people who asked to receive them, with a clear way to opt out.
• The agent acknowledges what it does not know instead of inventing a deadline, policy or price.
• Every relevant decision is recorded so someone can review it later.

These points reduce reports and blocks, which are precisely the signals that degrade a number's quality. If your concern is losing the line, the article on a banned WhatsApp number and how to avoid it when using an AI agent covers the behaviors that most put an account at risk. For agents that use language models, it is also worth knowing the risks catalogued in the OWASP Top 10 for LLM applications, such as prompt manipulation and excessive agency.

How our method applies to this topic

The method follows four moves. Map: understand the current flow, where conversations come from, how long they take, and where there is risk of fraud or identity confusion. Limit: define which data the agent sees and which actions it can take, leaving the rest to people. Pilot: choose one real flow, with logs and a success metric agreed in advance, and operate with the account configured correctly. Hand over: deliver the operation with documentation and decide whether to expand, adjust or stop.

In this design, the badge is an optional item on the account preparation list, never an acceptance criterion for the pilot. The source of truth for any account, name or verification requirement is Meta's official WhatsApp documentation, and the rules should be checked at the moment you act, not from memory or from old articles.

Frequently asked questions

How much does it cost to get the WhatsApp green badge? Meta does not treat the badge as a product you can buy, and promises of approval in exchange for payment deserve suspicion. The real costs are in preparing the account and running the support operation, not in a fee for the badge. Check Meta's official page in case anything has changed.

Can every WhatsApp API number have the green badge? No. Using the API does not automatically make an account eligible. Meta evaluates the brand and the account, and many serious operations run normally as a business account without the badge.

Are the green badge and business verification the same thing? No. Business verification proves the organization's existence and data in Meta's business portfolio and is a preparation step. The green badge is an additional recognition granted at Meta's discretion, and being verified does not guarantee receiving it.

Should my company wait for the badge before launching an AI agent on WhatsApp? Generally, no. The safest approach is to start with a small flow, with a verified number, a coherent name, clear limits and handoff to a human, and measure the result. If the account becomes eligible for the badge later, the request can be made without delaying what the pilot teaches you. For the technical design, see how to integrate AI into your company's WhatsApp.

Sources

• Meta: documentação do WhatsApp Business Platform
• ANPD: Autoridade Nacional de Proteção de Dados
• OWASP Top 10 for LLM Applications