After you build an RCS template, you can send it to your users in a standalone campaign or through a journey. This article explains the various ways to send RCS campaigns with Iterable.
# In this article
# Required permissions
To create and send RCS campaigns, you need the Manage and Launch Campaigns permission for the RCS message medium.
# About RCS campaigns
Every RCS campaign uses an RCS template, which sets the message content and the verified sender that delivers it.
A campaign only reaches users who are subscribed to that template's RCS
message type and have a phone number in the phoneNumber field. Recipients
must also be in a country where the sender is approved. When the sender is
Partially approved, Iterable can deliver only to carriers that have
approved the sender; other recipients bounce. For the full list of
requirements, see RCS Audience and Segmentation.
You can send RCS as a blast campaign to a list or segment, as a triggered campaign that responds to user activity or an API call, or from a journey.
Some campaign features are not available for RCS, including Frequency Management, Send Time Optimization, Experiments, and Campaign Alerts. See Current feature limitations in RCS Overview.
# Sending standalone campaigns (blast and triggered)
You can schedule and send a blast or triggered RCS campaign from the Campaigns page. Go to Messaging > Campaigns and click + New Campaign. Select RCS, then configure your campaign details.
For step-by-step instructions, see Sending or Scheduling a Blast Campaign and Activating a Triggered Campaign.
# Campaign delivery settings
# Quiet Hours
RCS campaigns support Quiet Hours. Quiet Hours are off until you enable them. For blast and triggered campaigns, turn them on in Delivery and Compliance. For journeys, turn them on in the RCS tile settings. See RCS tiles in Message Tiles.
NOTE
Quiet Hours can help you avoid sending promotional RCS at nighttime in each recipient's local time. They do not guarantee compliance with regional sending-time rules. Check with your legal counsel, and see Best Practices for RCS Compliance.
# Send Rate Limit (beta feature)
RCS supports using a Send Rate Limit when Iterable has enabled that feature for your project.
BETA FEATURE
Rate limits for campaigns and data feeds are a beta feature. Talk to your customer success manager to enable campaign and data feed rate limits for your account.
# Sending journey campaigns
The RCS tile in a journey sends a specified RCS campaign to users who pass through it, letting you automatically deliver RCS messages at the right time in a customer flow.
Iterable does not automatically send a fallback message when RCS delivery fails. To send a fallback on another channel after a failed RCS send, use a journey. For instructions on configuring an RCS tile, adding fallback logic, and using RCS events as journey entry sources, see Sending RCS from a Journey.
# Sending with the API
To send a triggered RCS campaign to a specific user, use
POST /api/rcs/target.
To cancel a scheduled send, use
POST /api/rcs/cancel.
To trigger a journey with an RCS campaign, use
POST /api/workflows/triggerWorkflow.