RCS messaging is supported with AloAi Text Agents, allowing agents to send and receive RCS messages on Lines with RCS enabled. This lets AI-driven conversations use RCS while continuing to support SMS when RCS is unavailable.
How it works
When an AloAi Text Agent is assigned to a Line with RCS enabled, its outbound messages are sent as RCS.
If the assigned Line does not have RCS enabled, the agent continues to send messages as standard SMS.
If a contact cannot receive RCS because their device does not support it or the carrier does not accept the RCS message, Aloware automatically falls back to SMS so the contact can still receive the message.
Inbound RCS replies are handled in the same way as SMS and MMS messages. The agent can read and respond to RCS replies, including replies that contain a photo or file.
The agent can also handle replies containing only an emoji, sticker, or reaction without errors. Message types that the agent does not recognize, such as rich cards or action buttons, are treated as generic replies.
When RCS provides delivery or read status, the status is available to the agent's decision logic. For example, the agent can use the status when determining follow-up timing.
Setting up RCS for an AloAi Text Agent
RCS uses the existing Line and AloAi Text Agent configuration. To use RCS with an agent:
Use a Line with RCS enabled.
Assign the AloAi Text Agent to that Line.
No additional configuration is required for agents that should continue using SMS. Agents assigned to Lines without RCS enabled continue to send standard SMS.
What to expect
Once configured, the AloAi Text Agent continues to send and receive messages as usual. Aloware sends messages as RCS when the assigned Line supports RCS and falls back to SMS when the contact cannot receive RCS.
The conversation log shows whether messages were sent as RCS, SMS, or MMS, along with their delivery statuses.
Existing SMS and MMS conversations continue without interruption when RCS is enabled.