WhatsApp display name rules, and why yours was rejected

A rejected display name is not an unexplained decision. Meta’s webhook returns a coded reason, and six such codes are documented: a person’s name, an unrelated business’s name, an unacceptable format, inconsistent branding, and an unknown reason that sends you to support. Read the code before you change anything, because a name that fails for inconsistency is fixed on your website, not in WhatsApp Manager.

What the display name is

It is not optional, and it is fixed at registration: “You must provide a display name when registering a business phone number.” Meta’s Business phone numbers page describes where it lands: “The display name appears in your business phone number’s WhatsApp profile, and can also appear at the top of individual chat threads and the chat list if certain conditions are met.” The condition is display name approval, which is a separate decision from the Official Business Account badge and does not depend on it.

Two things can overrule it. Your customer can: “Note that if a WhatsApp user edits your profile name in the WhatsApp client, the name they set will appear instead.” And the name is not the profile. Address, website and description sit in a different object, which Meta describes as follows: “Your business phone number’s profile displays additional information such as address, website, and description.” Those you can edit freely. The name you cannot.

Why a review happens without you asking for one

The review is triggered by growth, not by a submission. Meta writes that “When you reach a higher messaging limit”, your name is checked, and phrases the check as automatic: “your business phone number’s display name automatically undergoes verification based on the display name guidelines”. The webhook reference lists the two events that start one:

• “A newly created business phone number’s display name is reviewed.”
• “A business phone number’s already approved display name is edited and reviewed.”

So a name can carry real conversations for months and only then be judged, which is why a rejection can land with no submission of yours behind it. The outcome is pushed to you: “When the process completes, a phone_number_name_update webhook and Meta Business Suite notification are triggered.”

The codes Meta returns

The webhook carries a decision and a rejection_reason. Meta documents the second as “The reason why the business phone number display name was rejected, if it was rejected”, and points at its own guidelines in the same breath: “Review our display name guidelines for common rejection reasons.” These are the values, quoted from that reference.

rejection_reason	Meta’s description
NAME_EMPLOYEE_ISSUE	“Rejected because the display name included a person’s name or employee identifier.”
NAME_INDIVIDUAL_ISSUE	“Rejected because the display name included a person’s name or employee identifier.”
NAME_ENDCLIENT_NOTRELATED	“Rejected because the display name included an unrelated business’s name.”
NAME_FORMAT_UNACCEPTABLE	“Rejected because the display name used an unacceptable format.”
NAME_NOT_CONSISTENT	“Rejected because the display name was not consistent with the business’s branding.”
UNKNOWN	“Rejected for an unknown reason. Contact support.”

Two of those carry an identical description. We do not know whether they mean different things inside Meta, and we will not invent a distinction. A seventh value, null, is not a rejection at all: Meta glosses it as an acceptance.

The decision field matters as much, because two of its four values are neither approval nor rejection. DEFERRED means “Indicates a decision has been deferred.” and PENDING means “Indicates a decision is still pending further review.” Neither calls for a new name. APPROVED is the one that changes what customers see: “Indicates the display name has been approved and will now appear at the top of the business phone number’s profile in the WhatsApp client.”

The states the name itself can be in

decision is the outcome of one review. name_status is the standing of the name, and Meta warns against reading the wrong field for it: “The verified_name value doesn’t indicate whether the display name is approved.” That field is only the string under test, since “It represents the display name string that undergoes verification when eligible”, while “The name_status field indicates its approval status.”

The Business phone numbers page enumerates that field, with a caveat attached: “This field is currently in beta and not available to all developers.”

name_status	Meta’s description
AVAILABLE_WITHOUT_REVIEW	“The display name is ready to use without review.”
PENDING_REVIEW	“Your name request is under review.”
DECLINED	“The name has not been approved.”
EXPIRED	“The phone number’s certificate has expired and cannot be used to register the phone number for API use.”
NONE	“The phone number does not have a certificate and cannot be used to register the phone number for API use.”

Worth noticing what is absent. The Display names page says an approval sets name_status to APPROVED, and that value is not in the list on the Business phone numbers page. We read both on the same day and cannot reconcile them, so treat the list as incomplete rather than APPROVED as wrong.

On a rejection, name_status becomes DECLINED, and Meta gives two routes: edit the name against the guidelines, “or file an appeal via Developer Support or Enterprise Developer Support”.

What a change costs you

Changes are rate limited: “You can change a display name 10 times per 30-day period.” The expensive part is what follows approval. You have a deadline: “After the display name change is approved, you have 14 days to re-register the phone number”. Miss it and the review is wasted: “If the 14-day window expires without re-registration, you must submit the display name for review again.”

Order matters, and Meta states it twice on one page: “Re-registering before approval has no effect.” The re-registration is at least not a full restart, since “You do not need to send the business through Embedded Signup again.” And if you hold the badge, the self-service route closes: “If your business phone number has Official Business Account status, contact direct support to change your display name.”

What we could not verify, and will not quote

The rule set itself. Meta’s developer documentation does not contain the naming rules; it points at a Business Help Center article titled “Display name guidelines for the WhatsApp Business Platform”. We fetched it and extracted under a hundred characters of text, because its body is delivered by script rather than in the HTML. We cannot save a copy, so we will not quote it, and nothing here is sourced from it.

What it covers, named without quotation: what the name must relate to, the requirement that it be findable in your external branding, prohibitions on generic terms, on geographic terms used alone, on website and email formats, on advertising language, on references to Meta’s own apps, and on words implying endorsement. It also handles how to name a parent company or a client. If you need the exact wording before you resubmit, read it at Meta rather than at us.

Two more gaps. No page cited here publishes a review turnaround, so any figure quoted to you as the review time is somebody’s experience rather than Meta’s commitment. And nothing here says whether an appeal is held to a different bar than a resubmission.

The answer

Do not resubmit a guess. Take the code off the webhook, or the status off the field, and treat it as the diagnosis it is. NAME_NOT_CONSISTENT is a website problem: make the name findable in your public branding first. NAME_ENDCLIENT_NOTRELATED is an attribution problem, raised when the name points at a business other than the one that owns the number. The two person-name codes say the name reads as an individual rather than a business. And on PENDING or DEFERRED, change nothing: neither is a refusal.

Reading a platform’s stated reason instead of guessing at it is the same discipline as working out why a review reply was rejected.