Meta rejects a WhatsApp Business display name when the name doesn't clearly and honestly match the business behind the number — the most common triggers are a name that reads as generic or promotional, one that doesn't match your public website and legal identity, or one that borrows a brand you don't own. Fix it by making the display name match the name your customers already know you by (and that your website, GST registration, and signage all use), then resubmit; each rejection reason below maps to a specific, fixable cause.
Why the display name is reviewed at all
The display name is the one piece of your WhatsApp Business account a customer sees before they trust the chat — it sits at the top of the conversation and in the business profile. Meta reviews it (separately from your message templates and business verification) to stop impersonation and misleading branding, so a name that looks like a promo banner or a borrowed brand gets held or rejected even when everything else about the account is clean. This is a distinct gate from message-template rejection and from the green-tick official-business-account verification — a name can be approved while templates are still pending, and vice versa.
It's also distinct from simply changing an already-approved display name. This article is about getting a first name (or a resubmission) through review; the change-mechanics piece covers how often you can edit an approved name and what the cooldown looks like.
The six rejection buckets — and the fix for each
| Rejection reason | What it usually means | The fix |
|---|---|---|
| Too generic / descriptive-only | Name is just a category or common phrase ("Best Deals", "Home Services", "Online Store") with no distinctive brand element | Submit your actual brand name. A descriptor is fine only when attached to a real brand ("Sharma Electronics", not "Electronics Shop") |
| Promotional / call-to-action wording | Name contains an offer or instruction ("Buy Now", "50% Off Store", "Order Today") | Strip the promo language entirely — the name is your identity, not an ad. Move offers into message content, never the name |
| Doesn't match your public brand | The submitted name can't be tied to your website, social handles, or legal/GST records | Align the name with the brand your site, invoices, and signage already use; make sure that name is visible on your website before you submit |
| Trademark / brand borrowing | Name is a well-known brand, or a variant of one, that you don't own or aren't authorised to represent | Use your own brand. If you're an authorised reseller, make that relationship provable — and expect extra scrutiny |
| Formatting violation | Emoji, ALL-CAPS (unless it's your genuine acronym), a URL, a phone number, or unusual symbols inside the name | Plain, readable brand name in normal case. Keep the URL and number in the profile fields where they belong, not in the name |
| Unverifiable business | Meta finds no online footprint that corroborates the name exists as a real business | Establish a basic web presence (site or a real, populated business listing) using the same name first, then resubmit |
The single rule underneath all six
Every one of those fixes collapses into one principle: the display name should be the name a customer would recognise as your business, and it should be independently checkable. Meta's reviewers are effectively asking "if I search this name, do I find this business, and does the name look like an identity rather than an advert?" If the answer is yes on both counts, most rejections don't happen in the first place. Get the name, website, and legal/GST record saying the same thing before you submit, and you remove five of the six buckets at once.
Get the DPDP WhatsApp checklist
A founder-led WhatsApp reply with the DPDP consent + audit-log checklist for WhatsApp Business messaging. India-hosted. No spam.
What tends to be allowed (verify against current policy)
- Your legal entity suffix — "Pvt Ltd", "LLP", "& Sons" and similar are generally fine because they're part of your real name, not promotional.
- A genuine acronym — an ALL-CAPS name is usually accepted when it's your actual brand acronym, not stylistic shouting.
- A brand-plus-descriptor — "Meera Textiles", "Rao Diagnostics" pass because the descriptor is attached to a distinctive brand element.
- A regional/language name — a non-English brand name is fine as long as it maps to the business's real, verifiable identity.
These are patterns observed in practice, not guarantees — Meta's display-name guidelines are the operative source and they update. Confirm the current rules before assuming any of the above will clear.
Before you resubmit — a short pre-flight
- Match the trio. Website header, legal/GST name, and the display name you're submitting should all point to the same brand. Fix the odd one out first.
- Kill the promo. Remove any offer, verb, or instruction. If a word is trying to sell, it doesn't belong in the name.
- De-format. Drop emoji, URLs, phone numbers, and stylistic capitalisation.
- Prove existence. Make sure a search for the name lands on your real business — a live website using that name is the strongest signal.
- Then submit once, cleanly. Repeated near-identical resubmissions without changing the underlying cause tend to keep failing; change the actual trigger before trying again.
Where this sits in a new-account launch
Display-name approval is one of the early setup gates, alongside business verification and your first template approvals — none of them should be treated as an afterthought once you're already trying to send. A rejected name stalls go-live the same way a botched sending ramp or an unrecovered quality-rating drop does. If you're moving an existing number between providers, note that display-name state and approvals are part of what you should confirm during a BSP migration — don't assume the name carries over unexamined.
What the platform side costs
Display-name review itself is free — it's part of standard WhatsApp Business account setup, not a paid step. The cost that matters is the one that follows once you're live and sending: on RichAutomate that's ₹0 platform fee, ₹0 setup, and ₹0 monthly minimum, with Client Pay at ₹0.10/message plus Meta's per-conversation rate billed directly, or SaaS Pay at ₹1.20/marketing and ₹0.30/utility conversation all-in. See the full WhatsApp Business API cost breakdown and the Client Pay vs SaaS Pay comparison. Verify current Meta conversation rates, which change periodically. 14-day trial, 100 free credits, no card required to start.
As always: no tool can promise "no ban", and no display name — approved or not — changes that. A WABA stays in good standing on proper opt-in, honest branding, and the official API, not on any specific vendor.