> ## Documentation Index
> Fetch the complete documentation index at: https://smerio.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# RCS

> Understand branded conversations, rich content and device capabilities with RCS for Business.

RCS for Business lets a business communicate through an **agent**: the identity that represents the business in the conversation. Messages can include text, media, rich cards and suggestions that help the recipient respond or take an action.

## Message content

* **Text and media** communicate the essential information.
* **Rich cards** combine media, a title, a description and suggestions.
* **Suggested replies and actions** give the recipient a way to continue the conversation or complete a next step.

For example, an appointment reminder could pair the appointment details with an action to open a booking page. Keep essential details in the card text and give each action a clear label.

## Device capabilities

The experience should match the recipient’s supported features. Before live sending, the delivery integration needs to check whether the recipient can receive RCS from the agent and which message features are supported. Design content for those capabilities.

When RCS cannot reach a recipient, [SMS](https://smerio.com/docs/channels/sms.md) or [MMS](https://smerio.com/docs/channels/mms.md) may provide another route. That requires a separately configured delivery service and appropriate content for the selected channel.

## Testing and launch

Prepare the business identity, message content and intended destinations before planning a live launch. Confirm the approval requirements and supported routes for the delivery integration.

In Smerio, [RCS setup](https://smerio.com/docs/channels/rcs-setup.md) lets administrators register a test sender, inspect test-device status and prepare a production review. [Inbox](https://smerio.com/docs/workspace/inbox.md) keeps simulated conversations separate from connected live senders. A simulated reply or delivery event does not prove device reachability, sender approval or live delivery.

> [!NOTE]
>
> Real sending requires an activated connection. Test-device verification and production approval are separate states.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.