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

# Introduction

> Send rich mobile messages via RCS from the dashboard or API, with images, buttons, and delivery tracking.

<Tip>
  RCS is **SMS with superpowers**: when the device and carrier support it, you send **images, buttons, and carousels**, still to a **phone number**.
</Tip>

## What is RCS on Notifique?

It's the channel for **rich mobile messages** (Rich Communication Services). The destination is still an **international phone number** (E.164, no `+`), like SMS, but content can go beyond plain text.

You can:

* **Send** text (**BASIC**), image cards with buttons (**CARD**), carousels (**CAROUSEL**), or files via URL (**FILE**)
* **Dispatch** to 1 to 100 numbers per call (one message per number)
* **Schedule** sends for a future date and time
* **Query** status of each send by id
* **Cancel** while queued or scheduled
* **Track** short-link or button clicks via webhook

Think of a digital flyer in the pocket: more visual than SMS, but only reaches devices on RCS-capable networks.

<Note>
  Unlike WhatsApp, RCS **does not use a channel instance**. You only need an API Key with the right scopes and numbers in international format (e.g. `5511999999999`).
</Note>

## When to use it?

Works great for **campaigns with images and buttons**, **promotional alerts**, and **better conversion** than plain SMS, for RCS-capable recipients. For **OTP** that must reach **any** phone, prefer [SMS](/en/sms-api/como-funciona/introducao). Not every device delivers RCS; have a plan B (SMS, WhatsApp, or email) when delivery must be guaranteed.

## Message types

* **BASIC**, text only
* **CARD**, image, title, description, and buttons
* **CAROUSEL**, multiple cards in one message
* **FILE**, file via public URL + filename

Field details per type: **API reference** on the RCS tab.

## How it works in practice

1. **Create** an API Key with `rcs:send` (and `rcs:read` / `rcs:cancel` to query or cancel)
2. **Send** with `POST /v1/rcs/messages`, `to` as an array, `type` and `payload` per format
3. The platform **queues, sends, and updates status**; your backend gets alerts if you configured [webhooks](/en/rcs-api/como-funciona/eventos-do-webhooks)

<Info>
  Each **API Key** belongs to **one** workspace. On v1 **do not send** `x-workspace-id`.
</Info>

## Message lifecycle

After send, RCS moves through statuses like `QUEUED`, `SCHEDULED`, `PROCESSING`, `SENT`, `DELIVERED`, `CLICKED`, `FAILED`, or `CANCELLED`. API cancellation works while status is **`QUEUED`** or **`SCHEDULED`**.

With **short links** enabled, the first click on a **clicar.co** link from the send may mark **`CLICKED`**, webhook **`rcs.clicked`**.

## What you can do

* **Send** to 1 to 100 numbers per call (**60 credits** per message)
* **Schedule** with `schedule.sendAt`
* **Query** one send by returned id
* **Cancel** while queued or scheduled
* **Idempotency** with `Idempotency-Key` header
* **Per-send webhook** in `options.webhook` (that batch only)

See [Billing](/en/guides/introducao/cobranca-e-pague-pelo-uso). Error details: **API reference** on the RCS tab.

## After your first send

* **Track** delivery, clicks, and failures via [webhooks](/en/rcs-api/como-funciona/eventos-do-webhooks) (`rcs.sent`, `rcs.delivered`, `rcs.clicked`, `rcs.failed`)
* **Handle `FAILED`** with SMS or another channel when the network does not deliver RCS
* **Test** in [Sandbox](/en/guides/sandbox/index) with `sk_test_...` before production

## Next steps

* [Quick Start](/en/rcs-api/como-funciona/quick-start): first BASIC send
* [API Key scopes](/en/rcs-api/como-funciona/escopos-da-api-key): permissions
* [Webhook events](/en/rcs-api/como-funciona/eventos-do-webhooks): what hits your URL
* [Get started](/en/guides/introducao/comece-aqui): general platform integration