Quick answer: WhatsApp business identity involves four terms that are easy to conflate: the display name customers see, the verified_name Meta returns for a phone number, the green tick (a recipient-facing verified badge), and Official Business Account (OBA) status. Meta business verification is a separate review, not a shortcut to OBA status. None is automatic. Meta decides whether to approve or retain its statuses; Devotel Orbit can surface account information, but cannot grant verification or secure an OBA badge.
Four identity terms, with separate meanings
- Display name: The business name associated with a WhatsApp phone number and shown to customers in supported WhatsApp surfaces. Meta reviews the name against its requirements. A number can be connected and usable without having an OBA badge.
- Meta-returned `verified_name`: A name Meta returns for the WhatsApp phone number. It is account data, not proof that the account has an OBA badge.
- Green tick / verified badge: A recipient-facing identity signal associated with an Official Business Account in supported WhatsApp surfaces. “Green tick” is the familiar name; Meta may change the badge's appearance. It is not a display-name approval or a status a provider can add.
- Official Business Account (OBA): Meta's account status recognizing an official business presence. The badge is the visible identity signal associated with that status, not a separate approval a provider can grant.
Meta business verification checks the business and supporting information in Meta's tools. Completing it, or having an approved display name, does not by itself grant OBA status.
Meta's product labels and review flows can change by market and account. Check the current requirements in Meta Business Suite before preparing a submission. Approval, badge display, and continued eligibility remain Meta's decisions.
What the operator sees in Devotel Orbit
The WhatsApp quality view can display the phone number's verified_name alongside its quality rating. The name tells you what Meta returned; the rating is a separate measure of messaging quality. Neither one means Orbit approved the name or granted a badge. The WhatsApp dashboard surfaces the available account data for operators to monitor.
On the RCS side, the setup form collects a brand display name and supports logo upload as part of brand registration. WhatsApp and RCS therefore fit into one brand-identity posture for your team, but each channel has its own registration and review process. A name or logo accepted for one channel does not guarantee approval on the other. See the RCS brand registration and logo upload update for the shipped RCS workflow.
Display-name reviews: three avoidable problems
Meta's review is about whether the name clearly represents the business customers expect to find. These examples illustrate common preparation issues, not guaranteed review outcomes:
- Brand mismatch: A company known as “Northstar Dental” submits “Northstar Deals” for a customer-support number. The submitted name adds a sales identity that customers may not recognize. Use the established business or product name that the number represents, and make the relationship clear in the business profile and supporting material.
- Generic wording: A local repair company submits “Customer Service” as its display name. That describes a function, not a distinct business. Submit the actual brand name, such as “Harbor Bicycle Repair,” rather than a category or generic service label.
- Trademark or ownership evidence: A reseller submits “Acme Cloud” without showing its relationship to Acme. If your submitted name relies on a trademark, parent brand, or authorized reseller relationship, prepare current evidence that connects your legal business to the name before submitting. Do not imply an affiliation your documents cannot support.
Keep the public-facing name consistent across your business website, Meta business information, WhatsApp profile, and customer communications. If Meta rejects a name, read the reason, correct the mismatch, and use the review path Meta provides instead of repeatedly resubmitting the same wording.
A name review is separate from ongoing sender quality. After large template or campaign waves, monitor the WhatsApp quality-rating and template-pause guide: recipient feedback can change the number's quality rating even when its name remains unchanged.
Green tick and OBA: what they do—and do not—mean
An OBA badge is a recognition signal from Meta, not a capability that a provider can switch on for you. Meta sets the eligibility criteria and makes the decision. Criteria and application availability may differ by account and region; a small business should not treat a badge as a prerequisite for using the WhatsApp Business Platform, and a large enterprise should not assume its size, paid spend, or verified legal entity guarantees OBA status.
A sound OBA strategy starts with the evidence Meta currently asks for, not a target date for the badge. Keep the legal business details, website, display name, and public profile consistent. If Meta's current review asks you to establish public recognition, gather independent coverage that clearly identifies the same business; do not substitute paid promotion or a provider's promise for evidence Meta accepts. Then submit through the eligibility flow Meta makes available to your account and keep the supporting details current.
For a recipient, a badge can help distinguish an account Meta recognizes as an official business presence. It does not promise that every message is safe, endorsed, or relevant, and it does not replace your own customer-support and anti-fraud practices. Meta can change or revoke OBA status when an account no longer meets its requirements. A sustained quality downgrade may affect that eligibility, but a rating change by itself does not automatically remove the badge; Meta decides the consequence. Monitor both the account status in Meta and the quality rating shown in your WhatsApp dashboard.
Neither Devotel Orbit nor any messaging provider can promise a green tick or OBA approval. Treat services promising a guaranteed badge as a warning sign; the decision belongs to Meta.
A tenant-owned identity checklist
- Use the same recognizable brand name across WhatsApp, RCS, your website, and sender IDs. Where a channel has a different naming limit or format, keep the relationship obvious to customers.
- Gather current business, trademark, and authorization documents before submitting a name that depends on them.
- Submit a channel-specific logo and brand profile that your team is authorized to use. WhatsApp and RCS reviews are separate.
- Monitor the WhatsApp quality rating after template and campaign waves. Pause to review audience, consent, copy, and cadence when feedback deteriorates.
- Keep the WhatsApp display name stable during number or provider migrations. If a change is necessary, plan for Meta's review rather than assuming the prior approval transfers.
- Recheck Meta's current business-verification and OBA requirements in its official tools. Do not treat Orbit's dashboard data as a Meta approval notice.
Related guides
- WhatsApp Business API guide — account setup, templates, and messaging basics.
- RCS launch checklist — prepare an RCS brand and launch workflow.
- Google Verified SMS and the transition to RCS — background on the earlier verified-SMS-to-RCS transition.
- WhatsApp quality rating and template pauses — understand ongoing quality signals and template status.