Your RCS audience is made up of users who are subscribed to receive messages for an RCS message type. You can use this audience to send messages to your users.
You can also use Iterable's segmentation to build audiences of users who have a history of events with your RCS channel, and analyze your RCS audience in general.
# In this article
# User requirements to send RCS messages
To send RCS messages, your users must:
- Be subscribed to the RCS message type associated with the message you send.
- All RCS message types require an opt-in subscription policy.
- Have a valid phone number in the
phoneNumberfield. - Have a device and service carrier that supports RCS.
- Have a phone number from a country where you have an approved RCS sender.
For Iterable to log RCS Seen (rcsSeen) events, the user must have read
receipts available and enabled on their device.
NOTE
When your sender is Partially approved, you can only send messages to users whose carrier has approved your RCS sender. This isn't possible to determine in segmentation, so RCS messages to these users will be bounced and an RCS Bounce event will be logged.
# Building a segment for RCS-eligible users
You can't segment on carrier support or destination approval. A segment based on phone number and message type identifies users who are potentially eligible. Iterable still evaluates carrier and destination at send time.
To build a segment of potentially RCS-eligible users, add the following criteria:
- Find users with All of the following criteria:
- User profile field: Phone number (
phoneNumber) - is set - User profile field: Is eligible to receive message types - equals - Your RCS message type
- User profile field: Phone number (
# Building segments for RCS events
All RCS system events are available in segmentation. Use them to build audiences of users who have a history of events with your RCS channel.
# Example: Building a segment for RCS bounces
To build a segment of users for whom an RCS message has bounced, use the following criteria:
- Find users with All of the following criteria:
- Event: RCS Bounce - occurred any # of times
# Example: Identifying users who cannot receive RCS
When a recipient can't be reached through RCS, Iterable logs an RCS Bounce
(rcsBounce) event. For recipients who can't receive RCS, the bounce event
contains errorCode 7002. Because Iterable doesn't automatically send a
fallback message, if you want to reach these users on another channel, you must send a fallback from a journey.
To build a segment of users who have bounced because they can't receive RCS, use the following criteria:
- Find users with All of the following criteria:
- Event: RCS Bounce - occurred - at least once - with
errorCodeequal to7002
- Event: RCS Bounce - occurred - at least once - with
# Next steps
- RCS System Events — event fields and bounce codes.
- Sending fallback campaigns for users who cannot receive RCS