RCS
Connect RCS
RCS (RBM) is a verified sender with rich cards, carousels, and suggested replies. You create an agent, test with allowlisted devices, then submit verification before production campaigns.
In the app: Setup → Channels → RCS
Onboard an RCS agent
- Open Setup → Channels → RCS.
- Create the RCS agent and store messaging credentials when prompted.
- Invite tester devices and send a test rich card.
- Submit verification. Campaigns to unverified agents should stay on testers only.
- Create RCS templates in Library, then use reachability checks before a large send.
Settings and what they mean
Agent ID, brand ID, and messaging client secret are filled after agent creation (encrypted). You do not paste them by hand unless support asks you to recover a failed callback.
| Setting | What it means |
|---|---|
| Agent / brand name | Public RCS sender profile. Logos and legal URLs are submitted with the agent. |
| Testers | Google RCS–capable phones invited during onboarding. They can receive a plain test message with no Library template. |
| Verification | Screenshots from those tests plus KYC. Production traffic to non-testers waits on carrier approval. |
How to test RCS
- Invite at least one tester device on Setup → Channels → RCS.
- Send a test message (plain text is enough during onboarding) or chat from the tester phone.
- Confirm delivery on the device and the thread in Inbox.
- Capture screenshots — verification needs them. After launch, Settings → Try this channel sends an approved RCS template to other numbers; invited testers can still get the plain Setup send.