How it works

RCS (Rich Communication Services) is the evolution of SMS, not a separate channel. Messages are delivered in the same native messaging app your recipients already use for SMS — there's nothing new for them to install.

Compared to SMS, RCS lets you send richer content and get more visibility into how your messages perform:

• Verified sender branding, so recipients see your business name, logo, and colors instead of an unfamiliar number
• Rich media: images, videos, and rich cards with titles, descriptions, and buttons
• Carousels of multiple cards in a single message
• Suggested replies and suggested actions (call, open a map, open a URL, add a calendar event)
• Read receipts and typing indicators
• Longer message content than a standard SMS allows

If a recipient's device or carrier doesn't support RCS, or the message can't otherwise be delivered as RCS, Naxai can automatically fall back to SMS so the message still reaches them. See RCS to SMS Fallback.

Agents and Brands

To send RCS, you need an Agent — a verified sender identity tied to your Brand. Think of it as the RCS equivalent of registering a Sender ID for SMS: it's what lets recipients see your business identity instead of a raw number.

Today, creating and launching an Agent isn't self-service — reach out to your Naxai account manager to get one set up. Once it exists, you can view your Agent's details, use case, and performance directly through the API. See RCS Agents.

Before an Agent is fully launched, you can validate your messages on real devices using the Testers feature. See Testing RCS Messages.

Message types

RCS supports more than plain text: standalone rich cards, carousels, and file messages, each with optional suggested replies and actions. See Supported RCS message types for the full list with examples.

Sending RCS

Naxai offers two ways to send RCS depending on your use case:

• RCS API: send individual messages programmatically, with full control over message type, suggestions, and fallback.
  See Sending RCS Messages via API.
• RCS Broadcasts: send RCS to a segment of contacts or an uploaded file in bulk.
  See RCS Broadcasts.

Receiving replies

When a recipient replies to an RCS message or taps a suggested reply, Naxai delivers it to you via webhook. See Receiving Inbound RCS Messages.

Reports and status

Every RCS message goes through a lifecycle — submitted, delivered, read, or one of several failure states — that you can track through the API or webhooks. See RCS Status & Error Codes.

What's next?

• RCS Agents — view your Agent and Brand details
• Supported RCS message types — text, rich cards, carousels, and files
• Sending RCS Messages via API — send your first message
• Testing RCS Messages — validate on real devices before launch
• RCS Broadcasts — send RCS in bulk
• RCS to SMS Fallback — keep messages reaching recipients when RCS isn't available
• Country & Carrier Availability — where RCS works today