Error 131037 is an onboarding gate rather than a bug. Meta documents it as "WhatsApp provided number needs display name approval before message can be sent," with an HTTP status of 400 and a recommended action of changing the business phone number's display name (Meta for Developers, WhatsApp error codes reference, retrieved 2026-08-20).
The display name is what recipients see at the top of the chat. Because it is the entire basis on which someone decides whether a message is legitimate, Meta reviews it before allowing a number to send — and declines names that are vague, unverifiable, or unconnected to a real business.
Teams usually meet this code at the worst moment: the integration is built, the templates are approved, and the launch date is set. This guide covers what gets declined, the resubmission limits worth knowing before you burn attempts, and how to choose a name that passes first time. For the wider failure surface, our WhatsApp Business API error codes reference indexes the rest.
What Gets Declined
Display names are assessed against whether a recipient could tell, from the name alone, which real business is messaging them. BSP documentation lists the recurring decline reasons as generic or misleading content, a name that does not correspond to legal business documentation, restricted terms, and weak association with verified business assets such as a Facebook Page (HighLevel, why WhatsApp display name is declined, retrieved 2026-08-20).
Declined | Why | Better |
|---|---|---|
| Generic, names no business |
|
| Geographic location, not a business |
|
| "Official" is a restricted term |
|
| Contains a Meta product name |
|
| Vague, unverifiable | The registered trading name |
| Overlong, not how customers know you |
|
A name unrelated to your business documents | No documentation match | Your legal or trading name |
Three rules underpin all of it.
It must match your business. Not aspirationally — verifiably. The name should correspond to your legal or registered trading name, or a clearly identifiable product, service, or department within it. A name your business documentation cannot support is the most common decline.
It must be specific. Generic words, geographic terms alone, and industry categories fail because they identify a category rather than a company.
It must avoid restricted terms. "Official," "Global," Meta product names (WhatsApp, Facebook, Messenger), and unsupported symbols. "Official" is particularly tempting for brands worried about impersonation and is exactly the wrong instinct.
Resubmission Is Bounded — Budget Your Attempts
This is the part most teams do not know until they have already spent their attempts guessing.
BSP documentation states that businesses may change a display name up to 10 times within a 30-day period, after which a new cycle begins. It also notes the display name certificate remains valid for only 14 days before requiring reapproval (HighLevel, retrieved 2026-08-20).
Worth flagging on accuracy: these figures come from Business Solution Provider documentation, not from Meta's public error-code reference, which states only the recommended action of changing the display name. Treat them as directional and confirm current limits with your provider before planning around them.
The practical consequence stands either way: do not iterate by trial and error. Ten attempts sounds generous until a team burns four on variations of the same rejected concept. Decide the name deliberately, check it against the rules above, and submit once.
Reviewing and Submitting
Review is usually quick. BSP documentation describes approval as typically taking a few minutes to a few hours, though sometimes longer, with no maximum published. Since there is no guaranteed ceiling, the operational rule is simple: submit the display name early in onboarding, not the week of launch. It sits alongside business verification and app review as a lead-time item you cannot compress — the same trap that produces error 3 on launch day when a team discovers it is still on standard access.
Before submitting, strengthen the association Meta is looking for. A connected Facebook Page, a completed business verification, and a business profile whose website and description match the name all make the review straightforward. A bare name submitted against an otherwise empty business presence is what gets flagged as weakly associated.
Our guide to setting up the WhatsApp Business API covers where display name approval sits in the wider onboarding sequence, and creating a WhatsApp Business account covers the profile that supports it.
What This Is Not
Error 131037 gets confused with several other blockers, and the remedies are unrelated:
Code | Meaning | Fix |
|---|---|---|
131037 | Display name not yet approved | Submit or change the display name |
Phone number not registered | Register the number first | |
Certificate or registration error | Re-register the number | |
Payment method problem | Fix billing setup | |
App lacks required capability | Permissions or access level |
If you are working through go-live and hitting several of these in sequence, that is normal — they are separate gates on the same path, and each has to clear independently.
One thing 131037 is definitely not: a quality or policy enforcement action. It is a pre-launch check, unrelated to quality rating or the enforcement ladder that leads to account restriction. Nothing about your sending behaviour caused it.
Frequently Asked Questions
What does WhatsApp error 131037 mean?
The phone number's display name has not been approved yet, so it cannot send messages. Meta documents it as "WhatsApp provided number needs display name approval before message can be sent," with HTTP status 400 and a recommended action of changing the business phone number's display name.
Why was my WhatsApp display name declined?
The recurring reasons documented by BSPs are a name that is generic or misleading, a name that does not correspond to your legal business documentation, restricted terms such as "Official" or "Global" or Meta product names, and weak association with verified business assets like a connected Facebook Page. In short, a recipient should be able to tell from the name alone which real business is messaging them.
How many times can I change my WhatsApp display name?
BSP documentation states up to 10 changes within a 30-day period, after which a new cycle begins, and notes the display name certificate is valid for 14 days before requiring reapproval. These figures come from provider documentation rather than Meta's public error reference, so confirm current limits with your provider. Either way, decide the name deliberately rather than iterating by trial and error.
How long does display name approval take?
BSP documentation describes it as typically a few minutes to a few hours, sometimes longer, with no published maximum. Because there is no guaranteed ceiling, submit the display name early in onboarding rather than during launch week, alongside business verification and app review.
Can I use "Official" in my display name to prevent impersonation?
No. "Official" is among the restricted terms that cause a decline, along with "Global," Meta product names, and unsupported symbols. The protection against impersonation comes from your name matching your verified business assets and, separately, from the verified badge process — not from the word itself.
Choose the Name Once, Early
Error 131037 is not difficult, but it is easy to make expensive by treating it as a runtime error to iterate against rather than an onboarding step to plan.
Pick a name a customer would recognise as yours, that your business documents support, with no restricted terms and no geography standing in for a brand. Connect the Facebook Page and complete business verification before you submit, so the association Meta is checking for actually exists. Then submit it early — weeks before launch, alongside your other lead-time items — rather than discovering the review queue on the morning of your first campaign.
Want onboarding gates cleared before they become launch blockers? Helo.ai is a Meta Partner with 25 years of enterprise communication experience, managing display name submission, business verification, and number registration for enterprise WhatsApp programmes. Talk to an expert.
Next: error 133010 if the number is not registered yet, or error 131042 if billing is the blocker.
