RCS messaging allows approved RCS senders to send branded messages through Aloware. Recipients can see the sender's logo and display name. Messages support plain text and basic media.
RCS messaging is available across supported Aloware workflows and CRM integrations, including Sequences, Broadcasts, AloAi Text Agents, HubSpot, Salesforce, and HighLevel.
RCS sender and fallback
RCS messaging requires an approved RCS sender. When RCS is unavailable for a recipient, Aloware automatically falls back to SMS or MMS on the same channel the recipient uses to receive text messages.
This fallback allows messages to reach recipients who cannot receive RCS without requiring a separate workflow.
RCS in Sequences
RCS messages can be added to a Sequence as part of an automated messaging workflow. The RCS message step is available when the Sequence uses a Line with RCS enabled.
An RCS step can be used alongside SMS and MMS steps, allowing different mesage types to be included in the same sequence.
For instructions on adding and configuring an RCS message step in a Sequence, see Configure RCS messaging in Sequences.
RCS in Broadcasts
RCS messaging can be used in Broadcasts to send branded messages to multiple contacts. When the selected Line has RCS enabled, RCS is available as a message type alongside SMS and MMS.
Recipients are handled according to their RCS capability. RCS-capable recipients receive the message as RCS, while recipients who cannot receive RCS receive the applicable SMS or MMS fallback.
RCS Broadcasts follow existing carrier throttling and compliance limits. Sends are paced as needed rather than exceeding these limits. An empty or invalid contact list is blocked with a clear validation message.
For detailed instructions on configuring an RCS Broadcast, see How to send a broadcast in Aloware Talk.
RCS with AloAi Text Agents
AloAi Text Agents support RCS messaging on Lines with RCS enabled, allowing AI-driven conversations to send and receive RCS messages.
Outbound messages are sent as RCS when the assigned Line supports RCS. If RCS is unavailable for the recipient, Aloware automatically falls back to SMS.
AloAi Text Agents can process inbound RCS replies, including messages containing photos or files. Emoji-only replies, stickers, and reactions are handled without errors, while unsupported message types, such as rich cards or action buttons, are treated as generic replies.
When available, RCS delivery and read statuses can be used by the agent's decision logic, such as when determining follow-up timing.
RCS with CRM integrations
RCS messaging is supported through Aloware's HubSpot, Salesforce, and HighLevel integrations.
RCS can be used through supported workflows in these integrations.
Supported RCS content
RCS messages support plain text and basic media. Interactive content such as carousels, rich cards, quick replies, chip lists, and web views is not included in the current RCS messaging functionality described in this article.
RCS availability
RCS Business Messaging is available for approved US RCS senders. Canadian carriers do not currently support RCS Business Messaging.
When RCS is unavailable for a recipient, SMS or MMS fallback is used where applicable.
Getting started
If your account already has an approved RCS sender, the supported RCS capabilities become available as they are enabled.
No additional RCS registration is required for an already approved sender.
If your account does not yet have an RCS sender, RCS registration follows the existing process for ordering and approving an RCS sender.