> 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 live the campaigns.
{% 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 to create a New RCS template.
#### 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 **will still be sent**. However, variations within the asset that are in *Draft* or *Archived* status **will not be sent**.
{% 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.
BO: Example of enabled SMS fallback message from the RCS template setup
#### 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:
|
| 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 all message types except Carousel (Text, Media, Rich Card). | 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). |
BO: Visualisation of the differnces and placement of "Card Buttons" and "Suggested Actions"
#### 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.
* **Simple Text** - The localized or exact textual content intended strictly for the text-only RCS payload. This field supports user, label and campaign tags for personalization.
**🔹 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.
**🔹 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.
**🔹 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).
**🔹 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.
* **Card 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" %}
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 %}
#### 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 [RCS Gateway setup](https://help.smartico.ai/welcome/~/revisions/p2Mctke5Ybtsq6IVFnUZ/technical-guides/instant-messages-gateway-guide), and find more details on launching these messages within the customer journey by reviewing the [RCS Activity](https://help.smartico.ai/welcome/~/revisions/p2Mctke5Ybtsq6IVFnUZ/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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://help.smartico.ai/welcome/products/crm-automation/communication-channels/rcs.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.