The developer’s introduction to RCS

Beyond text.
Into conversation.

Bring useful actions into the messaging inbox. Explore RCS: branded messages, rich cards and replies that connect back to your application.

RCS / SMS / MMS

N
North StudioRCS · illustrative sender
Hands shaping clay at a pottery workshop
Your next creative afternoon

A little time to make.

Your pottery workshop is tomorrow at 10:30. Everything you need is waiting.

View booking
ConfirmChange time

Media + action + suggested replies. The next step is part of the message.

N
North StudioSMS · illustrative sender

North Studio: your pottery workshop is tomorrow at 10:30. View your booking or change the time:

north.example/booking

Text + a link. Keep the essential information in a self-contained message.

N
North StudioMMS · illustrative sender
A pottery workshop, attached to an MMS message

North Studio: see you tomorrow at 10:30 for your pottery workshop.

north.example/booking

Media + text. Attachment support and limits depend on the route and device.

Illustrative layouts. Actual appearance varies by messaging app. Photo: Tuan Nguyen / Unsplash.

01 / Understand02 / Build the conversation03 / Plan delivery

01 / The channel

The inbox is familiar.
The possibilities are richer.

RCS stands for Rich Communication Services. RCS for Business lets a business exchange branded, interactive messages with people in supported messaging apps.

Think of an appointment reminder with a reply, an order update with a tracking action, or a support conversation with clear choices. The next step can begin inside the message.

Explore Google’s RCS overview ↗

02 / For developers

A conversation is
an event-driven flow.

Your application sends a message through an API. Incoming replies and message events arrive through webhooks. Design the user journey and the event handling together.

01Your application

A booking, an update,
a customer request.

02RCS message

Content and actions
for the recipient.

03Reply or event

A webhook connects
the conversation back.

Start with one useful exchange. Define what each reply means, how you handle repeated events, and when the conversation is complete.

Read Google’s webhook guide ↗

03 / One journey, different formats

Keep the intent.
Adapt the message.

RCS, SMS and MMS can serve the same customer journey. Their content, reach and delivery behavior differ: check capabilities, write a useful alternative, and decide when fallback should happen.

See the delivery decision diagram ↗

The reading room

Get the foundations right.

All developer guides ↗

Before you build

A few practical questions.

Does RCS work on every phone?

No. Check business messaging availability for your sender and target recipients. Consumer RCS support alone does not establish that a business sender can reach a device.

What is an RCS agent?

An agent represents a business in the RCS conversation. It has a profile and is connected to the application that handles messages and events. In this context, “agent” does not necessarily mean an AI assistant.

What changes between testing and launch?

Testing uses invited test devices. Reaching customers requires brand verification and launch approval for the relevant networks. Read Google’s launch guidance.

From learning to implementation

Meet the Smerio Hub.

Explore the workspace we are building for senders, integration and launch readiness.

Explore the Hub →

Build with a clear starting point

What should your
next message do?

Talk to Smerio about your use case, target market and integration.

Discuss your RCS integration ↗