RCS Broadcasts
RCS Broadcasts lets you send RCS messages in bulk — to a segment of contacts or an uploaded file — with automatic SMS fallback and richer engagement metrics than SMS Broadcasts, such as read receipts and suggestion taps.
RCS Broadcasts requires an Agent attached to a Sender Service. If your Sender Service has no RCS Agent, sending is disabled. See RCS Agents and Sender Services.
Create a new RCS Broadcast
Go to RCS > RCS Broadcasts and choose the source of recipients to use: People or File.
Recipients from People
Select a segment of your contacts. You can choose to include unsubscribed contacts, though we recommend using an unsubscribe-aware segment so messages aren't sent to people who've opted out.
Recipients from a file
Upload a CSV file and indicate which column contains the phone number. The file must meet these requirements:
- Format: CSV
- The file must have a header row
- Header names must be a single word, alphanumeric plus
-and_, under 50 characters - Header names must be unique
- You can choose whether to allow or reject duplicate phone numbers within the file
Composing your message
Provide a name for the broadcast, select a Sender Service, and choose your message content — text, standalone rich card, or carousel. See Supported RCS message types for what each looks like.
You can personalize your message with Liquid syntax, using contact attributes when sending from People, or the file's own column headers when sending from a file.
SMS fallback
Add fallback text to send as SMS to recipients who can't be reached over RCS. See RCS to SMS Fallback.
Scheduling and pacing
An RCS Broadcast can be sent immediately or scheduled for later. You can also spread delivery over a period of up to 24 hours, sending messages gradually rather than all at once — this respects the time windows defined in a Calendar if one is selected.
By default, a message stops attempting delivery after 3 days. This can be customized, with a minimum of 10 seconds — keep in mind that not all validity periods behave identically across RCS and SMS fallback.
Broadcast lifecycle
An RCS Broadcast moves through the following states:
| State | Description |
|---|---|
draft | Being set up, not yet started |
scheduled | Set to start automatically at a future time |
started | Actively sending |
paused | Temporarily stopped, can be resumed |
completed | All messages have been queued for delivery |
canceled | Stopped and cannot be restarted |
Adraftorscheduledbroadcast can be deleted. Once a broadcast has started, it can be paused, resumed, or canceled, but not deleted or partially restarted.
Reviewing analytics
Once a broadcast is sent, you can track its performance from the RCS Broadcasts list: delivery status per recipient, read receipts, and taps on suggested replies or actions.
What's next
Updated 28 days ago