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 |
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.
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 · synthesis