Channel and Platform Policies
A source-linked guide to channel and platform policy and how this authority layer fits into U.S. A2P messaging programs.
What this authority layer covers
Channel-owner policies and implementation requirements for RCS, WhatsApp, Apple Messages for Business, and Meta business messaging.
Authorities and official sources
Each entry explains what the source says, where its limits are, and what it does not establish.
Channel or platform policy · Current
WhatsApp Business Messaging Policy
How this authority relates to messaging
This source states carrier, registry, or platform requirements for using the relevant messaging path.
What the source establishes
- Businesses must obtain recipient opt-in, honor opt-out requests, use approved message templates for business-initiated messages outside the 24-hour customer-service window, and comply with platform messaging rules.
Limits and important context
- The policy does not supply every template-review, pricing, quality-rating, technical, country-specific, or prohibited-industry rule.
Consent standard stated in the source
- recipient opt-in
Official and supporting sources
Source and review details
- Jurisdiction
- Channel or platform
- Source type
- Channel or platform policy
- Current status
- Current
Platform privacy notice · Current
Apple Messages for Business — Messages for Business privacy notice
How this authority relates to messaging
This source states carrier, registry, or platform requirements for using the relevant messaging path.
What the source establishes
- Apple documents user-initiated conversations, session identifiers, and authorization given directly to a business for subsequent Business Updates.
Limits and important context
- The privacy notice dated February 11, 2026 is not a complete sender rulebook and does not establish all registration, content, automation, routing, or enforcement requirements.
Official and supporting sources
Source and review details
- Jurisdiction
- Channel or platform
- Source type
- Platform privacy notice
- Current status
- Current
Channel or platform policy · Current
Google RCS for Business
How this authority relates to messaging
This source states carrier, registry, or platform requirements for using the relevant messaging path.
What the source establishes
- Google requires partner registration, agent creation, brand verification, prelaunch testing, launch approval, a working website, privacy and terms links, and opt-out capability for RCS for Business agents.
Limits and important context
- Launch is carrier and network dependent; carrier-managed launches may require direct carrier agreements, and verification occurs when launch is requested.
Official and supporting sources
Source and review details
- Jurisdiction
- Channel or platform
- Source type
- Channel or platform policy
- Current status
- Current
Platform change notice · Deprecated
Meta Messenger / Instagram business messaging
How this authority relates to messaging
This source states carrier, registry, or platform requirements for using the relevant messaging path.
What the source establishes
- Messenger Marketing Messages and Recurring Notifications were deprecated effective February 10, 2026, with new integrations closed September 1, 2025.
Limits and important context
- Feature availability and proactive messaging are platform-controlled; remaining business messaging capabilities continue to depend on current Meta product and policy rules.
Official and supporting sources
Source and review details
- Jurisdiction
- Channel or platform
- Source type
- Platform change notice
- Current status
- Deprecated
Continue with the most useful next step
Move from a jurisdiction or authority layer to the sources and tools most likely to answer the next question.
Get a program-specific review
Use an advisory review when the result depends on facts that a public authority index cannot resolve.
