> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/strategies/whatsapp/how-to-approve-the-whatsapp-display-name-in-the-official-api.md).

# How to Approve the WhatsApp Display Name in the Official API

Practical guide for SprintHub customers who use direct integration with the Official WhatsApp API (Cloud API). Understand what the display name is, why it is different from the "certificate", and how to get it

## What is the Display Name?

The **display name** (display name) is the name that appears to your customers when they receive a message from you on WhatsApp. It is the first thing the person sees — even before opening the conversation.

If the name is not approved, WhatsApp shows only the **phone number** in place of the company name. This reduces customer trust and can hurt your response rates.

## The Confusion with the "Certificate"

Many customers come to us asking about a **"certificate" required to approve the name**. Let's clear this up once and for all:

{% hint style="warning" %}
**Attention — This does not apply to you**

That so-called "display name certificate" was used in the old **On-Premises API** (self-hosted), which Meta discontinued. In this old model, the company hosted WhatsApp on its own servers and needed to download and register a certificate manually every time the name changed.

In SprintHub, the integration is done via **Official Cloud API** — the infrastructure belongs to Meta itself. This means that:
{% endhint %}

| On-Premises API (old)             | Cloud API (SprintHub)                       |
| --------------------------------- | ------------------------------------------- |
| Company hosted the servers        | Meta hosts everything in the cloud          |
| Needed to download certificate    | **No certificate** — automatic registration |
| Certificate was valid for 14 days | Approved name stays active directly         |
| BSP managed the process           | You manage it directly in Meta Business     |

{% hint style="info" %}
**Summary**

In the Cloud API (which is what SprintHub uses), approval of the display name **does not depend on any certificate**. It depends only on two things: **your company name in Meta Business Manager** and the **Meta's naming rules**.
{% endhint %}

## What Does Approval Depend On?

Meta analyzes two factors when approving (or rejecting) your display name:

### 1. The company name in your Business Manager (BM)

The display name needs to have **a direct relationship** with the company name registered in your Meta Business Manager account. Meta cross-checks this name with your website, documents, and online presence. If the display name does not match the company's identity, it will be rejected.

### 2. Meta's formatting rules

Even if the name is correct, it must follow a set of formatting rules. See below.

## Meta Display Name Rules

1. **Represent the business for real**\
   The name must represent your business, product, service, or department. It needs to be consistent with the branding on your website and official materials.
2. **Minimum of 3 characters**\
   Names with only 1 or 2 characters will be rejected. Example: `CT` is rejected, but `CT Store` is accepted.
3. **No ALL CAPS**\
   The name must use correct grammatical capitalization, just like the company name. `MARCO'S STORE` will be rejected — the correct one is `Loja do Marco` (unless your brand is registered that way in all caps).
4. **No URL format**\
   Names like `mycompany.com.br` or `www.store.com` are not allowed.
5. **No generic or geographic terms alone**\
   Names like `Fashion`, `Brazil`, `Consulting` or `Real Estate` will be rejected. It needs identity: `Fashion Express`, `Oliveira Real Estate`.
6. **No personal names alone**\
   `João Silva` will be rejected. But `João Silva Law` or `JS Consulting` may be accepted if it is on the website.
7. **Additional words: only region, department, or test**\
   You can add words that indicate region, department, or test account. Example: `Vida Pharmacy Brazil` or `Vida Pharmacy Support` are accepted. But `Vida Pharmacy Official` is not.

## Practical Examples

| Status | First name                      | Reason                                         |
| ------ | ------------------------------- | ---------------------------------------------- |
| ✅      | `SprintHub`                     | Brand name, consistent with the website and BM |
| ✅      | `Oliveira Real Estate`          | Full business name                             |
| ✅      | `Bem Estar Clinic Support`      | Name + department (allowed)                    |
| ✅      | `TechStore Brazil`              | Name + region (allowed)                        |
| ❌      | `SUPERGEEKS EDUCATION`          | All caps (unless registered that way)          |
| ❌      | `supergeekseducacao.com.br`     | URL format                                     |
| ❌      | `Education`                     | Generic term, without identity                 |
| ❌      | `SuperGeeks Official Education` | "Official" is not allowed                      |

## Step by Step: How to Change and Approve

{% stepper %}
{% step %}

#### Access Meta Business Manager

Log in `business.facebook.com` with your company's administrator account.
{% endstep %}

{% step %}

#### Go to WhatsApp Manager

In the side menu, click on **Account settings** → **WhatsApp Manager**. If you prefer, go directly to: `business.facebook.com/wa/manage`
{% endstep %}

{% step %}

#### Select your number

In the **Phone numbers**section, find the number connected to SprintHub.
{% endstep %}

{% step %}

#### Edit the display name

Hover over the current name in the "Name" column and click the **pencil icon** (edit). Enter the new name following the rules above.
{% endstep %}

{% step %}

#### Submit for review

Click on **Next** to submit. Meta reviews it automatically. In most cases, approval takes from **a few minutes to a few hours**.
{% endstep %}

{% step %}

#### Done — no certificate, no hassle

In the Cloud API, after approval the name becomes active automatically. You don't need to download anything, you don't need to re-register the number. Just wait for the approval to appear in the dashboard.
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Tip for quick approval**

Before submitting, make sure the name you want to use appears **exactly like that on your website**. Meta cross-checks the display name with your online presence. If the website says "SuperGeeks AI School" and you try "SuperGeeks Education", it may be rejected.
{% endhint %}

***

## Business Verification ≠ Display Name

Another common confusion: **business verification** (business verification) is a separate process from display name approval. However, they are connected:

**Before verifying the business:** your display name is approved automatically in most cases, without detailed review.

**After verifying the business:** Meta starts to review the display name more strictly, cross-checking it with the documents you submitted during verification. Any future name change goes through review.

Business verification is required to unlock higher message-sending limits (above 1,000 conversations/month) and to request the official business account (green badge).

## Frequently Asked Questions

<details>

<summary>Do I need to download any certificate?</summary>

No. In the Cloud API (the integration used by SprintHub), there is no certificate for the display name. That was part of the On-Premises API, which was discontinued by Meta.

</details>

<details>

<summary>My name was rejected. What do I do?</summary>

Check whether the name follows all the rules listed above. The most common reason for rejection is that the name does not match what appears on the company's website, or it uses a prohibited format (URL, all caps, generic term). Correct it and resubmit.

</details>

<details>

<summary>Can I change the name as many times as I want?</summary>

You can change the display name up to 10 times in a 30-day period. Each change goes through a new review.

</details>

<details>

<summary>How long does approval take?</summary>

In most cases, from a few minutes to a few hours. In rare cases it may take longer, especially if the company has already been verified and Meta cross-checks information more strictly.

</details>

<details>

<summary>If I don't approve the name, can I still send messages?</summary>

Yes, but your customers will see only the phone number, not the company name. This hurts trust and response rates.

</details>

<details>

<summary>Does SprintHub need to do anything in this process?</summary>

No. Name approval is done directly between you and Meta, through the Meta Business Manager dashboard. SprintHub is already integrated via Cloud API — as soon as the name is approved by Meta, it appears automatically in the sent messages.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.sprinthub.com/en/strategies/whatsapp/how-to-approve-the-whatsapp-display-name-in-the-official-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
