> 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/technical-guides/communication-gateways/supported-rcs-gateways.md).

# Supported RCS gateways

Smartico sends RCS (Rich Communication Services) messages to players through RCS providers: text, media, rich cards, carousels and templates, with buttons and an optional SMS fallback.

RCS gateways are configured in the Back-Office under **Label Settings → Gateways → Instant messages**. For the RCS asset and the message types, see [RCS](https://help.smartico.ai/welcome/products/crm-automation/communication-channels/rcs).

{% hint style="warning" %}
RCS is in Beta. Providers support different message types, so test each message type with your gateway before you launch a campaign.
{% endhint %}

***

## How RCS Gateway Configuration Works

RCS gateways are added in the Back-Office under **Label Settings → Gateways → Instant messages**. Adding a gateway opens a wizard:

<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%2Fgit-blob-db05e097a829062cb31d9dba7b6c847f59949c97%2F26fe054172-rcs-type-92a5216a-5f07df.png?alt=media" alt=""><figcaption><p>Label → Gateways → Instant messages → Create: 1 — Instant messages, 2 — Type: RCS, 3 — the RCS providers</p></figcaption></figure></div>

1. **Add IM gateway**: Select **Type: RCS**, then select the provider from the list. The list shows only the providers of the selected type.
2. **Conditions**:
   * **Name**: A name for internal identification.
   * **Brand**: On multi-brand labels, restrict the gateway to one brand, or leave **Any**.
   * **Set as default gateway**: Only one gateway can be the default at a time. Turn off the current default first.
   * **Gateway selection properties**: If gateway selection properties are set up for your label, the screen shows one field per property, named after the property (such as country or language). Pick the values for which this gateway is used during automatic selection. Ask your Smartico Success Manager to set the properties up.
3. **Authentication & Configuration**: Enter the credentials and settings the provider needs. The fields depend on the provider (see the catalog below).
   * **Additional parameters**: A key-value editor to pass extra settings that the form does not show. Use it only for keys your Smartico contact names for the provider.
   * **Callback URL**: For providers that report delivery statuses to Smartico, the full Callback URL for your environment is shown on this screen. Copy it into the provider account (or into the callback field of the form, when there is one).
4. **"From" config**: Enter the sender value. For providers with an SMS fallback, this value can also be used as the SMS sender.

If you change "From" values that existing campaigns use, a **'From' changes** screen asks you to confirm how those campaigns are updated before saving.

***

## Supported RCS Gateways Catalog

Below is the list of RCS providers supported by Smartico, with the fields the Back-Office asks for (names as in the wizard) and the provider-side setup.

***

### 1. Comtele RCS

* **Provider links**: [Website](https://comtele.com.br) · [Comtele API – Send RCS (Basic) message](https://developers.comtele.com.br/send-rcs-basic-message-23747431e0) · [Comtele API – Webhook: Status (delivery reports)](https://developers.comtele.com.br/webhook-status-2259798m0) · [Comtele API – Routes (route id the Smartico form asks for)](https://developers.comtele.com.br/routes-23747437e0) · [Comtele API – Home (x-api-key from Configurações > Chaves de API)](https://developers.comtele.com.br/home-2184257m0)
* **Back-Office Configuration Fields**:
  * `API Base URL` *(Required, Default: `https://api.comtele.com.br`)*: Comtele RCS API base URL. The type-specific path (basic/card/carousel/file) is appended automatically.
  * `API Key` *(Required)*: Comtele API key, sent as the x-api-key header.
  * `Route ID` *(Required)*: Comtele RCS route identifier (integer).
  * `Tag` *(Optional)*: Optional message tag/label for tracking in the Comtele back office.
* **What this gateway supports**:
  * Text, media, card, carousel and template messages are sent to separate Comtele endpoints; the base URL is enough.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 2. Conecta RCS

* **Provider links**: [Website](https://conectastartup.com.br) · [Solvefy CPaaS API reference (SMS, RCS, Bearer API key, callbackUrl)](https://solvefy.com/api) · [Solvefy CPaaS OpenAPI spec](https://solvefy.com/openapi.json)
* **Back-Office Configuration Fields**:
  * `API Base URL` *(Required)*: Conecta/Solvefy CPaaS RCS URL. Ex: <https://cpaas-api.solvefy.com/cpaas/v1/rcs/messages>.
  * `Bearer JWT Token` *(Required)*: Paste the RAW token WITHOUT the 'Bearer ' prefix — the sender adds it automatically.
  * `RCS Agent ID` *(Required)*: Approved RCS agent id used as the message from/sender.
  * `SMS Failover Sender` *(Optional)*: REQUIRED if SMS fallback is on: Conecta rejects a fallback without a sender, and the RCS Agent ID is not a valid SMS sender. If empty the asset from-number is used; if that is also empty the message is sent RCS-only.
  * `Enable SMS Fallback` *(Optional, Default: `On`)*: Uncheck to send RCS-only and never fall back to SMS (the asset Message is then used for card titles only).
* **What this gateway supports**:
  * SMS fallback is on by default. With fallback on, set `SMS Failover Sender`: Conecta rejects a fallback without a sender.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 3. Disparo Pro RCS

* **Provider links**: [Website](https://disparopro.com.br) · [Solvefy CPaaS API reference (SMS, RCS, Bearer API key, callbackUrl)](https://solvefy.com/api) · [Solvefy CPaaS OpenAPI spec](https://solvefy.com/openapi.json) · [Disparo Pro RCS API (product page)](https://disparopro.com.br/api-rcs/)
* **Back-Office Configuration Fields**:
  * `API Base URL` *(Required, Default: `https://cpaas-api.solvefy.com`)*: DisparoPro/Solvefy CPaaS base URL. The /cpaas/v1/rcs/messages path is appended automatically.
  * `Bearer JWT Token` *(Required)*: Paste the RAW token WITHOUT the 'Bearer ' prefix — the sender adds it automatically.
  * `RCS Agent ID` *(Required)*: Approved RCS agent id used as the message from/sender.
  * `SMS Failover Sender` *(Optional)*: REQUIRED if SMS fallback is on: DisparoPro rejects a fallback without a sender, and the RCS Agent ID is not a valid SMS sender. If empty the asset from-number is used; if that is also empty the message is sent RCS-only.
  * `Enable SMS Fallback` *(Optional, Default: `On`)*: Uncheck to send RCS-only and never fall back to SMS (the asset Message is then used for card titles only).
* **What this gateway supports**:
  * SMS fallback is on by default. With fallback on, set `SMS Failover Sender`: DisparoPro rejects a fallback without a sender.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 4. GOSAT RCS

* **Provider links**: [Website](https://gosat.org) · [GOSAT API docs (login /api/v2/login, RCS /api/v3/message/send/rcs, callback\_url)](https://api.gosat.org/message/doc)
* **Back-Office Configuration Fields**:
  * `API Endpoint` *(Required)*: Enter the Gosat RCS API base URL.
  * `API Login Endpoint` *(Required)*: Enter the Gosat RCS login API URL.
  * `Username` *(Required)*: Login username for Gosat API.
  * `Password` *(Required)*: Login password for Gosat API.
* **What this gateway supports**:
  * Media messages and templates are not supported: send an image as a card instead. Suggested actions are not sent.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 5. Infobip RCS

* **Provider links**: [Website](https://www.infobip.com) · [Send RCS messages (API, webhooks.delivery / seen)](https://www.infobip.com/docs/api/channels/rcs/rcs-outbound-messages/send-rcs-messages) · [Receive RCS delivery reports](https://www.infobip.com/docs/api/channels/rcs/rcs-logs-and-status-reports/receive-outbound-rcs-message-delivery-reports) · [Create an RCS sender (agent) - get started](https://www.infobip.com/docs/rcs/get-started) · [API authentication / API keys](https://www.infobip.com/docs/essentials/api-essentials/api-authentication)
* **Back-Office Configuration Fields**:
  * `API URL` *(Required)*: e.g. https\://{subdomain}.api.infobip.com/rcs/2/messages.
  * `API Key` *(Required)*
  * `Platform entity ID` *(Optional)*
  * `Platform application ID` *(Optional)*
  * `Track delivery reports` *(Optional)*: Receive delivery reports (default: on).
  * `Track seen (read) reports` *(Optional)*: Receive seen (read) reports (default: on).
  * `Seen report URL` *(Optional)*: A different URL for seen (read) reports. By default the Callback URL is used.
  * `Intermediate delivery reports` *(Optional)*: Also receive intermediate delivery reports (default: off).
* **What this gateway supports**:
  * Delivery reports and seen (read) reports can each be turned on or off; an intermediate delivery report is optional.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 6. Interativa Conect RCS

* **Provider links**: [Website](https://enriquecimento.interativaviews.com.br)
* **Back-Office Configuration Fields**:
  * `API Base URL` *(Required, Default: `https://enriquecimento.interativaviews.com.br`)*: Interativa Views base URL. The send path is appended automatically.
  * `RCS Bearer Token` *(Required)*: RCS-type token generated in the Interativa panel.
  * `Default Campaign ID (partner_id)` *(Optional)*: Optional fixed partner\_id; defaults to the engagement UID when sending.
* **What this gateway supports**:
  * Templates are not supported.
  * Delivery statuses are not reported to Smartico (Interativa keeps them in its own reports).
* **Provider-Side Setup**:
  * Get your RCS agent (brand sender) approved with the provider.

***

### 7. MailerWeb RCS

* **Provider links**: [Website](https://www.mailerweb.com.br/) · [MailerWeb (Scatha) Transactional API docs: authentication, SMS, WhatsApp, RCS](https://api.mailerweb.com/transactional/docs)
* **Back-Office Configuration Fields**:
  * `API Base URL` *(Required, Default: `https://api.mailerweb.com/transactional`)*: MailerWeb transactional base URL. The /rcs/send path is appended automatically.
  * `API Key (username:key)` *(Required)*: MailerWeb API key in username:key format, sent as the x-api-key header.
* **What this gateway supports**:
  * Templates are not supported.
* **Provider-Side Setup**:
  * Get your RCS agent (brand sender) approved with the provider.

***

### 8. MEX10 RCS

* **Provider links**: [Website](https://www.mex10.com) · [MEX10 API docs – RCS > Enviar RCS (rcs.aspx, token, authorized source IP)](https://mex10.com/docs/#rcs-send-7)
* **Back-Office Configuration Fields**:
  * `API Endpoint URL` *(Required)*: e.g. <https://mex10.com/api/rcs.aspx>.
  * `API Token` *(Required)*
* **What this gateway supports**:
  * Carousels are sent as their first card only.
  * The Mex10 RCS integration does not process delivery reports.
* **Provider-Side Setup**:
  * Get your RCS agent (brand sender) approved with the provider.

***

### 9. Plugni RCS

* **Provider links**: [Website](https://plugni.com.br) · [Plugni API docs – RCS endpoints (/rcs/bulks, Bearer token)](https://api.plugni.com.br/docs#tag/rcs) · [Plugni API docs – Webhook (delivery reports; set in panel settings)](https://api.plugni.com.br/docs#section/Webhook) · [Plugni OpenAPI spec (YAML)](https://api.plugni.com.br/swagger)
* **Back-Office Configuration Fields**:
  * `API Base URL` *(Required, Default: `https://api.plugni.com.br/v1`)*: Plugni API base URL. The /rcs/bulks path is appended automatically.
  * `Bearer Token` *(Required)*: Plugni API token (Bearer/JWT). Template (SINGLE) sends require a SINGLE-type token.
  * `RCS Agent ID` *(Optional)*: Optional override for the Plugni RCS agent ID (number), from GET /rcs/agents. Defaults to the message from-number.
* **What this gateway supports**:
  * Media and carousel messages must be defined as a Plugni template and sent with the template type. The SMS fallback text is passed to Plugni with each message.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 10. Pushfy RCS

* **Provider links**: [Website](https://pushfy.com) · [Pushfy API docs (Swagger UI)](https://portal.pushfy.com/docs/) · [Pushfy OpenAPI spec – /rcs, /apircsnativo, Bearer / X-API-TOKEN auth](https://portal.pushfy.com/docs/openapi.yaml) · [Pushfy official docs repository](https://github.com/PushfyCpaaS/Pushfy)
* **Back-Office Configuration Fields**:
  * `Pushfy URL` *(Required)*: URL of Pushfy RCS API.
  * `Authorization` *(Required)*: Full Authorization value for the Pushfy API (including any prefix).
* **What this gateway supports**:
  * Text, media and card messages.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 11. SendWork RCS

* **Provider links**: [Website](https://www.sendwork.com.br) · [SendWork API – Send RCS v4 (/api/v4/sendrcs)](https://docs.sendwork.com.br/#send-rcs-v4) · [SendWork API – Authentication](https://docs.sendwork.com.br/#authentication) · [SendWork API – RCS webhook](https://docs.sendwork.com.br/#webhook-rcs)
* **Back-Office Configuration Fields**:
  * `API Endpoint URL` *(Required, Default: `https://api.swork2.com.br/api/v4/sendrcs`)*: Enter the URL for the SendWork RCS endpoint where the RCS request will be sent.
  * `User Api ID` *(Required)*: Enter your application ID for authentication.
  * `Api Key` *(Required)*: Enter your application Key for authentication.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 12. Short Code RCS

* **Provider links**: [Website](https://shortcode.com.br) · [Short Code API docs – RCS: envio (api.shortcode.com.br/rcs/messages)](https://shortcode.com.br/documentacao.html#rcs-envio) · [Short Code API docs – RCS webhooks (status, delivery, click, received)](https://shortcode.com.br/documentacao.html#rcs-webhooks)
* **Back-Office Configuration Fields**:
  * `Base URL` *(Required, Default: `https://api.shortcode.com.br`)*: Enter the base URL for the ShortCode API.
  * `Bearer Token` *(Required)*: Enter the bearer token for authentication.
  * `RCS Agent ID` *(Required)*: ID of the RCS agent approved for this ShortCode account.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 13. Sintalk RCS

* **Provider links**: [Website](https://sintalk.com.br/) · [Getting started: create the API key](https://docs.sintalk.com.br/docs/getting-started) · [Send messages (SMS / RCS / voice)](https://docs.sintalk.com.br/reference/sendmessages) · [Create a webhook endpoint (delivery status)](https://docs.sintalk.com.br/reference/createwebhook) · [Message status update event (webhook payload)](https://docs.sintalk.com.br/reference/messageupdateevent)
* **Back-Office Configuration Fields**:
  * `API Endpoint URL` *(Required)*: Sintalk messages endpoint. Default: <https://api.sintalk.com.br/v3/messages>.
  * `API Token` *(Required)*: Sintalk API key, sent as the X-API-Key header.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 14. Twilio RCS

* **Provider links**: [Website](https://www.twilio.com) · [Get started with branded RCS messaging (register RCS sender, add to Messaging Service)](https://www.twilio.com/docs/rcs/onboarding) · [Twilio API requests – Account SID + Auth Token (HTTP Basic)](https://www.twilio.com/docs/usage/requests-to-twilio) · [Track the message status of outbound messages (StatusCallback URL)](https://www.twilio.com/docs/messaging/guides/track-outbound-message-status) · [RCS Business Messaging overview](https://www.twilio.com/docs/rcs)
* **Back-Office Configuration Fields**:
  * `API Endpoint URL` *(Required)*: Twilio Messages API URL, e.g. <https://api.twilio.com/2010-04-01/Accounts/{AccountSid}/Messages.json>.
  * `Twilio Account SID` *(Required)*
  * `Twilio Auth Token` *(Required)*
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

### 15. Yup Chat RCS

* **Provider links**: [Website](https://yup.chat) · [Yup Chat RCS API (HTTP Basic auth with ID + token; JS-rendered page)](https://yup.chat/api/rcs) · [Yup Chat Public API Gateway OpenAPI spec (raw JSON; /v1/rcs/messages, basicAuth)](https://api.yup.chat/docs)
* **Back-Office Configuration Fields**:
  * `API Endpoint URL` *(Required)*: Enter the Yupchat RCS API base URL.
  * `Username` *(Required)*: Username for YupChat API.
  * `Password` *(Required)*: Password for YupChat API.
* **Provider-Side Setup**:
  * Set the **Callback URL** from the gateway configuration screen in the Back-Office as the delivery status URL in your provider account (or paste it into the callback field of the form, when there is one).
  * Get your RCS agent (brand sender) approved with the provider.

***

## SMS Fallback

When **Enable SMS fallback** is on in the RCS asset, the fallback text is sent as an SMS if the RCS message cannot be delivered (for example, the device does not support RCS). The fallback needs support on the provider side. **DisparoProRCS** and **ConectaRCS** also have an **Enable SMS Fallback** switch in the gateway settings.

***

## Frequently Asked Questions (FAQ)

### Where do I find the Callback URL for delivery reports?

Open the gateway in **Label Settings → Gateways → Instant messages** and go to the **Authentication & Configuration** screen. The Callback URL is generated for your environment and shown there for every provider that reports statuses. Do not build it by hand.

### How does automatic gateway selection work when several RCS gateways are configured?

When a campaign uses automatic selection, Smartico picks the gateway at send time from the gateways whose **Brand** and gateway selection property values match the player. Use **Set as default gateway** on the gateway that should be used by default.

### What should I do if our preferred RCS provider is not listed?

1. **Your secured gateway**: Connect your own sending service through the [Secured Messaging Gateways (Email/SMS/IM)](https://help.smartico.ai/welcome/technical-guides/communication-gateways/secured-messaging-gateways-email-sms-im.md) API.
2. **Request a new integration**: Contact your Smartico Customer Success Manager or Integration Manager with the provider's API documentation.

### Where are the general instructions for instant message gateways?

See the [Instant Messages Gateway guide](https://help.smartico.ai/welcome/technical-guides/communication-gateways/instant-messages-gateway-guide.md).


---

# 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/technical-guides/communication-gateways/supported-rcs-gateways.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.
