Sender verification
The gate every business-messaging channel puts in front of a brand identity: proof that the sender is who it claims to be, and that whoever operates the integration is authorized to speak for them. The clearest pattern to emerge once this wiki held more than one channel.
The same gate, three implementations
| Channel | What is verified | By whom | What the customer sees |
|---|---|---|---|
| rcs-business-messaging | Agent details and the partner's right to manage the agent, confirmed by an individual brand representative by email rcs-brand-verification | Google, or the carrier | A verification checkmark beside the agent name |
| apple-messages-for-business | Brand registration, plus a one-to-two-week review of the conversation experience on real devices apple-messages-for-business-docs | Apple | Branded presence in Messages |
| whatsapp-business-platform | Business verification against the [[whatsapp-business-account | WABA]], with the message-template gate applied per message | Meta |
And a fourth channel with no gate at all. Telegram's Bot API asks for nothing: you message BotFather, receive a token, and start sending. No brand registration, no authorization of an intermediary, no review of the conversation. That is worth holding beside the table above, because it shows the gate is a policy choice by the operator, not a technical requirement of running a business-messaging channel.
The two things being checked
Verification is doing double duty, and the RCS documentation is the most explicit about it: the agent's information is one assertion, and the messaging partner's right to act for the brand is a separate one rcs-brand-verification. The second is the interesting half. These channels are built on the assumption that an intermediary — a BSP, an RCS partner, an Apple MSP — will be doing the actual sending, so the platform has to bind that intermediary to a brand's consent. Google's insistence on an individual's email rather than a distribution list is that binding made concrete: a shared inbox cannot be held accountable.
Why the gates exist
The channels being defended are ones users did not opt into as marketing surfaces. They are the default messaging app on a phone, alongside messages from family. A verified sender badge is the consumer-facing half of the same policy that produces message-template approval and per-message-pricing's bias toward customer-initiated conversation: the platform sells reach into an intimate space and must be seen to police it.
A fifth arrangement: the gate that sells discovery (2026-09-04)
LINE does not fit either pole. Anyone can open an account and push messages immediately, with no review — like Telegram. But the account is issued unverified, and an unverified account cannot be found in LINE's in-app search. Verification is applied for, takes "5〜10営業日", requires the business's official name (unchangeable afterwards), and returns a green badge, searchability, friend-add advertising, coupon placement and invoice billing.
So identity verification here is not permission to speak. It is distribution, sold as a feature — and the same review doubles as the credit check that unlocks invoice billing (line-official-account-plans). That is a third design beside blocking (WhatsApp, Apple, RCS) and absence (Telegram), and it undercuts the framing of both: a gate can be entirely optional and still decide who gets an audience.
The super-apps: gates on content, not identity (2026-09-22)
The two apps most often called restrictive turn out to gate something different from the table above. WeChat lets a user action open a short reply window (five messages in 48 hours after the user writes), limits push templates to service notices and bans marketing in them, and counts consent per notice: one tap on a subscription pop-up allows one notification. Certification unlocks the subscription channel rather than the right to speak. Kakao sorts by message class: an inspected transactional template (AlimTalk) can reach any phone number, and advertising can reach only channel friends or users who gave marketing consent. Both put the gate on what is sent and to whom, which is where WhatsApp puts its template review, and neither makes identity the main control.
Where the implementations diverge
Apple reviews the conversation itself, not just the identity — recorded demos, agent scripts, a performance review at go-live apple-messages-for-business-docs. Google verifies identity and authorization once, then approves per launch, with carriers able to re-run their own checks rcs-brand-verification. WhatsApp verifies the business once and then polices every message through template approval. Same objective, three different points in the pipeline to enforce it.
Related
rcs-brand-verification · business-solution-provider · message-template · rcs-business-messaging · apple-messages-for-business · whatsapp-business-platform · telegram-bot-api · line-messaging-api · wechat-official-account-messaging · kakao-bizmessage · synthesis