> ## Documentation Index
> Fetch the complete documentation index at: https://docs.orbit.devotel.io/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp business identity and verification

> Understand display names, Meta business verification, verified names, and Official Business Account status, and prepare your business identity for review.

# WhatsApp Business Identity and Verification

WhatsApp identity has several separate signals. A display name, Meta business verification, the `verified_name` returned for a phone number, and Official Business Account (OBA) status are not interchangeable. Meta reviews and controls its approvals; Devotel Orbit can show account information but cannot grant a verified name, badge, or OBA status.

## Know which identity signal you are preparing

* **Display name:** The name associated with your WhatsApp business phone number and shown in supported WhatsApp surfaces. Meta reviews whether it represents your business.
* **Meta business verification:** A review of the business and its supporting details in Meta's business tools. It does not automatically grant OBA status.
* **`verified_name`:** The name Meta returns for a phone number. It is not proof of an OBA badge.
* **OBA status:** Meta's separate recognition of an official business presence. The badge's appearance and application availability can change by market and account.

Check the current instructions and eligibility in Meta Business Suite before making a submission. A provider cannot guarantee that Meta will approve or retain a name or status.

## Prepare a display-name submission

1. Choose the established business or product name customers already recognize. Avoid replacing it with a generic description such as “Customer Service.”
2. Make the relationship clear if the name is for a product, subsidiary, reseller, or parent brand. Do not imply an affiliation you cannot document.
3. Gather current business, trademark, and authorization documents before you submit a name that depends on them.
4. Review the name and supporting business details together in Meta's current submission flow. If Meta declines the name, use its stated reason to correct the mismatch before requesting another review.

These steps help you prepare a clear submission; they do not predict or guarantee Meta's decision. Meta's naming requirements and review process are authoritative.

## Monitor the connected number

In Devotel Orbit, open the WhatsApp quality view to see the `verified_name` and quality rating returned for the connected number. The name and rating are separate: a displayed name is not a badge, and a strong rating does not mean Meta granted OBA status. Check Meta's own tools for the current business verification and account status.

After template or campaign waves, review the quality rating and investigate a downgrade. Revisit the audience, consent, copy, and send cadence using your tenant's controls. Read the [WhatsApp quality rating guide](https://docs.orbit.devotel.io/blog/whatsapp-quality-rating-wave-2026) for the relationship between recipient feedback and messaging quality.

## Keep names consistent across channels

Keep your recognized brand name consistent across WhatsApp, RCS, your website, and sender IDs. RCS registration is a separate carrier review: prepare the display name and logo for that channel too, and do not assume approval transfers between channels. Use the [RCS launch checklist](https://docs.orbit.devotel.io/blog/rcs-launch-checklist-2026) to plan that registration.

If you migrate a WhatsApp number or provider, keep its established display name stable unless you have a reason to change it. Plan any change around Meta's review process; do not assume an earlier approval will transfer automatically.

## Related guides

* [WhatsApp Business API guide](https://docs.orbit.devotel.io/blog/whatsapp-business-api-guide-2026) — account, template, and messaging basics.
* [WhatsApp identity and the green tick](https://docs.orbit.devotel.io/blog/whatsapp-display-name-verification-green-tick-oba-2026) — how the four identity signals differ.
* [Google Verified SMS and the transition to RCS](https://docs.orbit.devotel.io/blog/google-verified-sms-to-rcs-legacy-explainer) — background on the legacy verified-SMS program.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.