Why your WhatsApp display name gets rejected, and how to fix it
Meta rejects a display name when it cannot tie the name to your legal business and your public website. Here are the four reasons I see most, and the exact fix for each.


Meta rejects a display name when it cannot tie the name to your legal business and your public website. Here are the four reasons I see most, and the exact fix for each. In this deep dive, we explore actionable strategies, real-world engineering blueprints, and future-proof patterns to elevate your digital operations.
- What the review is actually checking
- Rejection 1: your brand name is not your legal name
- Rejection 2: the name is not on the site, or it is spelled differently
- Rejection 3: the name is a claim or a keyword
- Rejection 4: it looks like a person
- One detail that costs people a month
- How to appeal without guessing
- You can still send while it is under review
- The checklist I run before submitting
- Where BNex fits
- Related Reading
You pick a name, type it into the box, wait two days, and the status says declined. No detail, no phone number to call, and the number is already half configured.
I build BNex, a WhatsApp Business Platform product, and this is the most common place people get stuck in their first week. The review is not random, and it says nothing about the quality of your name. It is a comparison. Meta takes the string you submitted and asks two questions: does this belong to the business that owns this account, and can I see it in public?
Below is what the review checks, the four rejections I see most, and what to change in each case.
What the review is actually checking
Four things, in rough order of how often they fail:
- Relationship to the legal business. The display name must connect to the entity that was verified. A trading name with no visible link to the registered company is the most common rejection.
- Consistency with external branding. The same string, with the same spelling, capitalisation and spacing, must appear on your website or public material.
- Not generic. A category ("Fashion", "Travel Agency") or a generic place name is refused. So are slogans and long descriptions.
- Not restricted. Words like "Official" or "Verified", any Meta or WhatsApp brand name, emojis, URLs and phone numbers are out.
There is also a requirement people miss: the business needs a working website. A parked domain, an Instagram page standing in for a shop, or a site behind a login is not enough.
Rejection 1: your brand name is not your legal name
This is the big one. You trade as "Spice Route Kitchens". The verified entity is "SRK Hospitality Private Limited". You submit "Spice Route Kitchens" and it comes back declined.
The name is fine. What is missing is the bridge between the two strings, in public. Meta reads your website, not your intent.
The fix is one sentence in the footer and one paragraph on the About page:
Spice Route Kitchens is a brand operated by SRK Hospitality Private Limited.
Put the legal name in your terms page and on an invoice PDF as well. If the relationship is a subsidiary, a franchise or a distributor arrangement, say so in plain words. Then resubmit.
Rejection 2: the name is not on the site, or it is spelled differently
I have seen a rejection caused by a hyphen. The website said "Blue-Ocean Media", the submission said "Blue Ocean Media". Another came from an ampersand where the site used "and".
Meta checks for the name as it appears externally. Small differences read as a different business.
Open your live homepage and look at four places: the header, the footer, the About page and the contact page. The string should be identical in all four, and identical to the submission, character for character. Then check for the same string off your own site, if you have it: a LinkedIn company page, a Google Business Profile, a directory listing.
If the site is being rebuilt right now, wait. Submitting against a half finished site burns a review cycle.
Rejection 3: the name is a claim or a keyword
"Best Chennai Web Design Agency". "24/7 Plumbing Services Near You". "Buy Sarees Online". All three get declined.
The rule is that the name represents a business, not a pitch. If your trading name genuinely contains a place, that is usually fine. If the place is there to catch searches, it is not.
Use the trading name and stop. The description field is where the explaining goes, and it is not reviewed the same way.
Rejection 4: it looks like a person
A full personal name is refused unless it is clearly the brand, and the brand is visible externally. This catches a lot of solo consultants and agents who put their own name on the number.
If the business really is you, put the trading name on the number and your own name in the description. If you want the personal name on it, make it a brand: it needs to appear as a brand on the website, not as a friendly greeting in a hero paragraph.
One detail that costs people a month
Before the number is registered you can change the display name as often as you like. After registration, changes go through review and there is a waiting period between requests, commonly 30 days.
So a rushed first submission is not a small mistake. It can cost a month of running on a name you do not want. Decide the string before you touch the form, and write it down.
How to appeal without guessing
When a name is declined you can appeal. A support case that says "please approve" gets nowhere. Include:
- The phone number and the WhatsApp Business Account ID.
- The exact display name you want, written precisely.
- Why it differs from the primary business name, if it does.
- Public evidence of the link: the page on your site that shows both names, an invoice, a registration document, a LinkedIn page.
If the name belongs to a subsidiary or an associated brand, say which one and attach the material that shows the relationship. Reviewers approve documents, not explanations.
You can still send while it is under review
The review does not block messaging. You can connect the number and send while the name sits in pending. What customers see may be your phone number instead of the business name until the name is approved, which looks rough but is not fatal.
That matters when you plan a launch. Do not hold a campaign for a name review, and do not run a big outbound push on a number whose name is still pending.
The checklist I run before submitting
- The exact string is on the homepage header, footer, About and contact page.
- The legal entity name appears on the same site, with a sentence connecting the two.
- The name on the business portfolio matches, or the difference is explained.
- No "Official", "Verified", "Meta" or "WhatsApp", no emojis, URLs or phone numbers.
- At least three characters, and no slogans.
- The website loads publicly, without a login.
- You are willing to keep this name for at least a month.
That takes twenty minutes. It is cheaper than a declined review and a thirty day wait.
If you are starting from zero, the full path from business portfolio to a live API number is in how to get WhatsApp Business API access. If you are still deciding whether you need the platform at all, WhatsApp Business API vs the Business app is the shorter read.
Where BNex fits
BNex is the WhatsApp Business Platform product I build. It does not shortcut the display name review. That review belongs to Meta, and the only thing that moves it is a name that matches your public business.
What BNex does is make the next part sane: one business number instead of an employee's handset, and a shared inbox so the conversation stays with the company when that employee is on leave. If you have already been through a template rejection, the reasons templates get rejected is the same discipline applied to message copy.
If your display name has been declined and you cannot see why, send me the name you submitted and the URL of your site on WhatsApp at +91 73587 22745. I will tell you which of the four above it is, and it usually takes one look.
Related Reading
Get more insights like this
Join our list for practical automation, web engineering, and growth strategy — written by builders, for builders.

Manikandan S
Founder & Technical Lead at ZiyncFounder and technical lead at Ziync. I build high-performance websites and web applications for startups and mid-market teams: React, Next.js, Firebase. Based in Chennai, working with clients worldwide.