> For the complete documentation index, see [llms.txt](https://help.smartico.ai/welcome/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/rcs.md).

# RCS

RCS is a modern, interactive offline communication channel designed to boost player retention by delivering rich media and interactive experiences directly to native messaging apps. With Smartico, you can send highly engaging RCS messages through real-time or scheduled campaigns.

{% hint style="warning" %}
IMPORTANT: RCS is currently in Beta. Because capabilities and payload specifications may vary between the different RCS providers, please verify that the chosen message type and structures are fully supported. Always test your templates before launching the campaigns live.
{% endhint %}

#### Creating & Managing RCS Assets

Before sending an RCS message in a campaign, you must first create an asset (resource).

📌 **Where to Create Assets?**

* Navigate to the Marketing tab in the BO (Back Office).
* Go to the Assets section on the left-side menu and select Instant messages.
* Click **Create** and choose **RCS**.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FJ4rjUvU61OxR6niyxFjh%2Fr2-005-crop-1-66b65d70-29fa45.png?alt=media" alt=""><figcaption></figcaption></figure></div>

#### Key Asset Configurations

The RCS asset configuration is dynamically changing depending on the selected RCS Message Type.

**1. General Section**

* **Name** - used to identify and select this asset within your campaigns.
* **Status** - The lifecycle status of the asset (Active, Draft, or Archived).

{% hint style="info" %}
**Important***:* If an asset is in *Draft* or *Archived* status but is already used in a campaign, the communication <mark style="color:$success;">**will still be sent**</mark>. However, variations within the asset that are in *Draft* or *Archived* status <mark style="color:$danger;">**will not be sent**</mark>.
{% endhint %}

**2. Fallback Section**

* Enable SMS fallback - A toggle switch to automatically send a plain SMS instead if the recipient's device does not support RCS. Recommended for maximum reach.
* **SMS fallback text** - When SMS fallback is enabled, this required field defines the text message sent if RCS delivery cannot be completed. It supports full personalization tags (such as player attributes and brand tags). Note that automated SMS fallback also requires that your configured messaging gateway provider supports SMS failover.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2F2015gRZi2yphIQ9H8Aig%2Fimage.png?alt=media&amp;token=d8a08e76-a46a-433e-be51-29fae6e91eb1" alt=""><figcaption><p>BO: Example of enabled SMS fallback message from the RCS template setup</p></figcaption></figure></div>

#### 3. Interactive Buttons: Suggested Actions vs. Card Buttons

When creating an interactive experience, you can add click actions using two different elements depending on your message setup. Clicking **Add suggested action** or **Add card button** opens the same configuration modal to define the following properties:

* **Action/Button text** - The text displayed directly on the interactive button.
* **Type** - The behavioral action triggered when clicked:
  * **Reply** - Sends a predefined text message response back from the user immediately when clicked (e.g., an easy way for users to tap "Stop messages" or "Subscribe" without typing it out manually).
  * **Open URL** - Navigates the user to a specific website link or deep link (e.g., "Go to Tournaments").
  * **Dial Phone** - Prompts the user's phone application to call a configured phone number (e.g., "Call us").

While they function similarly, they are visually and structurally different:

| <p><br></p>      | Suggested Actions                                                                                                  | Card Buttons                                                                                                     |
| ---------------- | ------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
| Visual Placement | Displayed outside the message container as floating chips or separate standalone action pills under the payload.   | Embedded inside the card layout container itself, stacked neatly right underneath the text body.                 |
| Availability     | Available in Text, Media, Rich Card, and Carousel (displayed below the carousel). Not configured in Template type. | Available exclusively within Card and Carousel structures.                                                       |
| Primary Use Case | Most commonly used for quick-replies, global opt-ins/opt-outs, or general message responses.                       | Used for contextual actions tied directly to the card's specific media/content (e.g., claiming a specific gift). |

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FUgbpZhIgCjBGp7S6KOzI%2Fr2-006-crop-3-494ec2fb-ff0e5e.png?alt=media" alt=""><figcaption><p>BO: Visualization of the differences and placement of "Card Buttons" and "Suggested Actions"</p></figcaption></figure></div>

#### Dynamic Fields by Message Type

The fields in the Message content section are entirely based on your chosen RCS Message Type. You can also see a live mock preview of how your setup will render on a smartphone to the right of the configuration fields.

**🔹 Type: Text**

Plain text message with optional interactive actions. Best for quick updates.

* **Message** - The localized textual content of the RCS message (up to 2,000 characters). This field supports user, label, and campaign tags for personalization, as well as up to 4 Suggested actions.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FAlL0xTY6BSOVpLCXsyrf%2Fr2-007-crop-4-478cacbc-06a755.png?alt=media" alt=""><figcaption></figcaption></figure></div>

**🔹 Type: Template**

Unlike custom rich cards or carousels created directly inside Smartico, the **Template** type relies on structural layouts that you have already registered and pre-approved directly with your RCS provider.

* **Template id** – The exact, unique identifier generated by your RCS provider when your custom template was approved on their platform. Many mobile network operators or local regulations require rich-media messages to be explicitly whitelisted and pre-verified to prevent spam.
  * Seamless Variables Integration: When you use a Template ID, the provider knows exactly where your media files, action buttons, and text belong. Smartico will hand over the payload to your provider to automatically populate the dynamic variables (like customer names, unique promo codes, or deposit balances) within that template layout.
* **Content variables (JSON)** - This field is optional in case your provider expects additional parameters and tags on top of the template ID.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2F2uZE6xaLJ0iQeG3ccckj%2Fr2-008-crop-5-737de3d6-7f218e.png?alt=media" alt=""><figcaption></figcaption></figure></div>

**🔹 Type: Media**

Send a standalone image or video with an optional caption text.

* **Media type** - Choose between Image or Video.
* **Media URL** - Choose from gallery, upload or provide a direct web link to the image or video file you want to attach.
* **Message** - The text caption under the media.

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2FDsdGlLxMoLGHz2rc5DFe%2Fr2-009-crop-6-592f88ec-0ab4a2.png?alt=media" alt=""><figcaption></figcaption></figure></div>

**🔹 Type: Rich Card**

A single dedicated container featuring rich media, headline, description and buttons.

* **Media type** - Choose between Image or Video.
* **Media URL** - Choose from gallery, upload or provide a direct web link to the image or video file you want to attach.
* **Media height** - Adjust the visual height ratio of the media asset container (Short/Medium/Tall)
* **Card title** - Define a headline that captures the user's attention and gives them a clear idea of what your message is about.
* **Card description** - Define a description by elaborating on the title, highlighting key benefits, and driving conversions with a clear call to action.
* **Card Buttons** (Up to 4) - Click "**Add card button"** to easily construct buttons directly attached to the bottom of the card (e.g., URL redirects, deep links, or quick-replies).

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2Fv0gS4gCt9dEyVjS55OzA%2Fr2-010-crop-7-7871719d-429baf.png?alt=media" alt=""><figcaption></figcaption></figure></div>

**🔹 Type: Carousel**

A scrollable, horizontal swipeable gallery containing a minimum of 2 and up to 10 distinct interactive cards. Great for product lists or multiple options.

* **Media width** - Sets a unified horizontal width alignment for all cards in the layout (Small/Medium).
* **Media height** - Adjust the visual height ratio of the media asset container (Short/Medium/Tall)
* **Cards control** - Use the expandable setup to independently configure each rich card. You can use the control icons to reorder, duplicate, or delete cards.

{% hint style="info" %}
**Media width** and **Media height** (here and in a Rich Card) change the preview in the Back Office. Most gateways do not send these values from the asset to the phone. For example, Infobip sends the Medium size. Check with your RCS provider before you rely on a size.
{% endhint %}

{% hint style="info" %}
Need help designing your Carousel?

* To see how a carousel layout actually looks on a mobile screen and plan your image sizes, look at the [Google Rich Card Layout Guide](https://developers.google.com/business-communications/rcs-business-messaging/guides/learn/rich-cards).
* If you need copy-and-paste code examples to help you structure your buttons or card lists correctly, use the [Infobip RCS Outbound Message Documentation](https://www.infobip.com/docs/api/channels/rcs/rcs-outbound-messages/send-rcs-messages) as a blueprint.
  {% endhint %}

<div data-with-frame="true"><figure><img src="https://77049817-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfS5hl0PiysHtKAKMsQTe%2Fuploads%2F0gmsCxNQ0D14qWukysFC%2Fr2-011-crop-8-4cd5ce82-5a1f96.png?alt=media" alt=""><figcaption></figcaption></figure></div>

#### Personalized Content with Content Variations

You can tailor your RCS content based on the end user's profile using Content Variations. This feature allows you to present different text, imagery, or card setups based on user segmentation parameters such as level, language, currency, country, or custom behavioral properties.

💡 How It Works:

1. Configure the targeting rules you want to trigger (e.g., *Language, Level, Currency, Country*).
2. Create different content variations or distinct layout structures optimized for those segments.
3. Once the asset is deployed in a campaign, end users will seamlessly receive the most relevant variation based on their profile and matching conditions.

#### Related Resources

To complete your channel setup, you can learn how to configure the backend connection by checking out our guide on the [Instant Messages Gateway setup](https://help.smartico.ai/welcome/technical-guides/communication-gateways/instant-messages-gateway-guide), and find more details on launching these messages within the customer journey by reviewing the [Activity: SMS, RCS, Viber and WhatsApp](https://help.smartico.ai/welcome/products/crm-automation/activities-of-flows/activity-sms-viber-and-whatsapp) in Campaigns setup.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.smartico.ai/welcome/products/crm-automation/communication-channels/rcs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.