# RCS senders & verification

The full registration process for your RCS agent: create the sender, register it country by country, complete the organization and compliance data, and follow every status until it's active.

**Language:** en
**Audience:** platform
**Translation key:** platform.channels.rcs.senders-verification
**Search keywords:** rcs sender, rcs agent, create rcs sender, create rcs agent, add sender, brand agent, rcs verification, agent approval, rcs use case, billing category, non conversational, conversational, register agent country, add country, under review, processing, rejected agent, rcs sender states, registration status, regulatory status, effective status, responsible contacts, rcs consent, test phone numbers, legal profile, registration profile
**Related pages:** /platform/es/channels/rcs/senders-verification, /platform/en/channels/rcs/agent-profile, /platform/en/channels/rcs/agent-best-practices, /platform/en/channels/rcs/availability, /platform/en/channels/countries
**Docs index (every page):** https://docs.instasent.com/llms.txt
**This zone's index:** https://docs.instasent.com/platform/en/llms.txt
**This page:** https://docs.instasent.com/platform/en/channels/rcs/senders-verification/ (HTML) · https://docs.instasent.com/platform/en/channels/rcs/senders-verification.md (Markdown)
**Other language (es):** https://docs.instasent.com/platform/es/channels/rcs/senders-verification.md

Before you can send RCS, you **create a sender**, add the **countries** you want
to operate in, complete the **required data**, submit it for **review** and follow
its **status** until it's active. This page walks through that process end to end.
The agent profile itself — fields, image specs, live previews — has its own page:
[Your RCS agent profile](/platform/en/channels/rcs/agent-profile).

## Senders and registers

A **sender** is your brand identity, created **once** inside the project, just like
an SMS sender. To use it in a country, you **create and get approved a register
specific to that country**. And inside that register you **configure the RCS agent
profile** the contacts in that market will see.

So there are three distinct, nested things: a sender groups the registers for each
country, and each register holds the agent profile for its market. Because each
country is handled on its own, the same sender can be active in one country and
still under review in another — and it can only send to a country once that
country's register is fully cleared.

## Create the sender

Go to **Settings > Project > Channels > RCS**. If you don't have a sender yet, the
**Set up your RCS channel** checklist walks you through the stages: create the
sender, register the agent for a country and send your first campaign.

![The RCS channel page showing the channel status, the Needs your attention section with agents in review, and the stats for the period](/platform/en/channels/images/senders-verification--1-rcs-channel-page.png)
*The RCS channel page on a project that's already set up: the channel status, what needs your attention, and the stats for the period.*

Click **Create Sender**. The **Create RCS sender** form asks for three decisions:

- **Display name** — the name the end user sees for your brand in their messaging
  app.
- **Billing category** — how messages are billed. Both categories have the **same
  features**; what changes is the billing model. **Non conversational** is billed
  per sent / received message; **Conversational** (billed per opened conversation)
  is not available yet and shows a **Coming soon** badge.
- **Use case** — the kind of messages you'll send: **Verification codes (OTP)**,
  **Transactional**, **Promotional** or **Mixed**.

> **Warning**: **These fields cannot be modified after creating the sender.** And the use case
> has a direct consequence: if you select **Transactional** or **Verification
> codes (OTP)** you will not be able to send promotional messages. So when you'll
> combine **transactional and promotional** messages — common in ecommerce, where
> order confirmations and campaigns live side by side — select **Mixed**.

Click **Create Sender**. The sender sheet opens, with no countries registered yet.

![The sender sheet showing the Registered countries section and the Add country button](/platform/en/channels/images/senders-verification--3-sender-details-empty.png)
*The sender sheet gathers its countries, each with its name and its status — here, with Spain already accepted.*

## Register it for a country

Click **Add country**. The **Register RCS agent for a country** form asks for
the **Country**, the **Name** recipients will see (up to 40 characters) and an
optional **Description** (up to 100 characters). Click **Create draft**.

![The Register RCS agent for a country dialog: the country is still to be picked, and the name and description come from the agent profile](/platform/en/channels/images/senders-verification--4-register-country-dialog.png)
*Each country gets its own register and starts as a draft. The name and description come from the agent profile, so you only adjust what changes.*

While the registration is a draft you can edit it freely — but as the form
warns, *this data cannot be modified once submitted for verification*. The draft
opens on a sheet with three tabs: **Agent Profile**, **Organization** and
**Compliance**.

### The Agent Profile tab

Your brand identity: name, description, color, logo, banner, contact details and
legal URLs, with a live preview of how contacts will see it. Every field and its
limits are detailed in
[Your RCS agent profile](/platform/en/channels/rcs/agent-profile).

### The Organization tab

Here you state who's behind the brand and how you collect consent from your
contacts. This is the information Google and the operators review to approve the
agent, so it's worth filling in carefully: incomplete or unconvincing data is a
common reason for rejection.

- **Contacts responsible for the agent** — at least one, up to five. Each contact
  has a **Full name**, **Job title** and **email**, added with **Add contact**. It
  should be a **real person** at the organization, with first and last name and a
  **named corporate email** (`firstname.lastname@company.com`). Avoid generic
  addresses like `info@company.com` or `support@company.com`: this person *will
  receive an email from Google to approve brand usage*, and a shared inbox often
  goes unread and stalls the approval.
- **How do you obtain consent to send messages?** — describe how you collect
  consent from the people who'll receive the messages (up to 1000 characters). The
  panel puts it this way: *"It is important to provide details on how you obtain
  consent. If acceptance is done through a website or app, please include links or
  URLs to screenshots."* Be specific about the moment and the mechanism — for
  example, "The user agrees to receive communications when signing up on our website
  through an explicit consent checkbox" — and, if acceptance happens on your website
  or app, add **links, URLs or screenshots** as evidence. It's required for the
  **Transactional**, **Promotional** and **Mixed** use cases, and optional for
  **Verification codes (OTP)**.
- **Test phone numbers** — optional, up to five. Added with **Add phone**, each
  with its country prefix (for example `+34`). The panel describes them as
  *"Optional — we may send test messages to these numbers during registration."*:
  they let the review check the agent on a real device, so it helps to include at
  least one.

![The Organization tab of the RCS register, with the contacts responsible for the agent and the consent question](/platform/en/channels/rcs/images/senders-verification--organization.png)
*The Organization tab: responsible contacts and how you obtain consent.*

### The Compliance tab

This is where you complete the legal side of the register. It has two elements:

- **Filing** — only appears when the country has a regulator. It sets how the
  request is filed with the regulator. **I'll file it myself** comes selected, and
  it's the recommended option: it's the short path, for when you've already
  registered the alias yourself. The alternative is **Instasent files for you**,
  which adds the paperwork we have to fill in on your behalf.
- **Legal profile** — required for **every** register, whether or not the country
  has a regulator. It holds the **legal-entity data** (registered company name, tax
  ID) submitted to the regulator and the operators. These are the same legal
  profiles used for SMS senders, so if your organization already registered SMS
  senders you can **reuse the same one**. You pick it with **Select profile**.

This data weighs directly on the decision: a correct legal profile and an entity
consistent with the agent's brand help the approval go through, while incomplete
data, a company name that doesn't match the brand, or an unconvincing responsible
contact are frequent reasons for rejection. Neither the filing type nor the legal
profile has its own save inside the tab — both are saved when you **Save draft**.

> **Note**: In Spain, the CNMC regulation that applies to SMS senders is **not active for
> RCS yet**, so an RCS agent in Spain doesn't go through the CNMC today — it's
> cleared once the operators approve it. You still assign a legal profile here
> (see below). More in [Spain](/platform/en/channels/countries/spain#does-it-apply-to-rcs-too).{/* VERIFY: confirmar con producto/legal cuándo se activa CNMC para RCS — hoy solo (sms,ES) enforced */}

> **Warning**: The legal profile is required for **every** register, whether or not the country
> has a regulator: *assign a legal profile in the Compliance tab before submitting
> for review*. Without it, the panel won't let you submit the request.

![The Compliance tab of the RCS register, with the Filing block and the selected legal profile](/platform/en/channels/rcs/images/senders-verification--compliance.png)
*The Compliance tab: the filing with the regulator and the register's legal profile.*

## Submit it for review

With the three tabs complete, the draft's footer offers two actions: **Delete
draft**, to discard it, and **Submit request**, to send it for review.

Click **Submit request**. The **Submit RCS agent for review** form sums up what
to verify before confirming: name and description, logo and banner dimensions,
legal URLs, contact details and organization information — *once approved, the
agent data cannot be modified*.

![The Submit RCS agent for review confirmation dialog with the pre-submit checklist](/platform/en/channels/images/senders-verification--7-submit-confirm.png)
*One last check before the point of no return.*

Click **Confirm and submit**. The registration moves to **In review**:
Instasent reviews your agent and manages the registration with the operators on
your behalf. The first review may take up to **48 hours**; full approval with the
operators can take up to **4 weeks**, depending on the country.

![The sender sheet with the country registration under review](/platform/en/channels/images/senders-verification--8-sender-in-review.png)
*The register, submitted and under review.*

Meanwhile the channel keeps you posted: the **Needs your attention** section of
the RCS channel shows **Agents in review**. Watch out for one detail that catches
people out: registrations still in **draft** are counted there too, so the number
isn't only the ones awaiting a decision — some of them are waiting on you.

![Close-up of the Needs your attention section with the Agents in review card and its counter](/platform/en/channels/images/senders-verification--9-channel-overview-in-review.png)
*The card sits on the RCS channel overview, gathering the registrations that aren't active yet — in review or still drafts.*

## Following your register's status

Each country row on the sender sheet shows a single **status** that tells you where
the register stands and whether the sender can send there. Behind it are two
layers, and the sender can send only once **both** are clear:

- The **operator layer** — where the agent stands with Instasent and the mobile
  **operators**.
- The **regulator layer** — where it stands with the country's **regulator**, when
  that country has one. Most countries have no RCS regulator and skip this layer.

| Status             | What it means                                                  | Clear to send? |
| ------------------ | -------------------------------------------------------------- | -------------- |
| **Draft**          | Saved but not submitted. Fully editable.                       | No             |
| **In review**      | Submitted; Instasent is reviewing the agent.                   | No             |
| **With operator**  | Passed the first review; being registered with the operators.  | No             |
| **With regulator** | Submitted to the country's regulator, awaiting their response. | No             |
| **Accepted**       | Approved — the agent can send in this country.                 | Yes            |
| **Rejected**       | Declined, with the reason shown on the register.               | No             |
| **Revoked**        | A previously granted authorization was withdrawn.              | No             |
| **Archived**       | Retired. Register a new version to replace it.                 | No             |

```mermaid
stateDiagram-v2
    state "In review" as InReview
    state "With operator" as WithOperator
    state "With regulator" as WithRegulator
    [*] --> Draft: create register
    Draft --> InReview: Submit request
    InReview --> Draft: Cancel review and edit
    InReview --> WithOperator: first review passed
    WithOperator --> WithRegulator: sent to regulator (if any)
    WithOperator --> Accepted: approved (no regulator)
    WithRegulator --> Accepted: regulator authorizes
    InReview --> Rejected: declined
    WithOperator --> Rejected: declined
    WithRegulator --> Rejected: regulator declines
    Accepted --> Revoked: authorization withdrawn
    Accepted --> Archived: retire or replace
    Archived --> [*]

    class Accepted success
    class Rejected destructive
    class Revoked destructive
```

> **Note**: While a register is **In review** you can use **Cancel review and edit** to take
> it back to **Draft** and keep editing. Once it moves to **With operator** there's
> no going back until there's a decision.

> **Warning**: Once an agent is **Accepted**, its data can't be modified. To change it, archive
> it and register a new version.

> **Note**: Each country is tracked on its own, so the same agent can show a different status
> in each destination.

## If a register is rejected

When a register is rejected, the reason is shown on the register. A rejected
register is final: to try again you register a new version of the agent — and
**contact support** if you need help. The common reasons — and how to avoid them
up front — are in
[RCS agent best practices](/platform/en/channels/rcs/agent-best-practices#avoid-the-common-rejection-reasons).

A previously approved register can also be pulled back — for example if an
operator suspends the agent, or a regulator revokes a granted authorization. If
that happens, Instasent handles the next steps; contact support if you need help
moving forward. Country-specific rules live in
[Countries & regulation](/platform/en/channels/countries).

## Reach more countries

From the sender sheet, **Add country** opens a new registration with the form
**pre-filled from your existing profile** — name, description, images and contacts
included. You only adjust what changes for that destination and submit. The
regulatory classification is not inherited: it's specific to each country.

Once a registration is approved, your sender is **Active** in that country and you
can select it when creating a campaign. Each country's status is visible at a
glance in the channel's senders list.

![The RCS senders list with the agent and its per-country status](/platform/en/channels/images/senders-verification--11-senders-list.png)
*The senders list: every agent and its status per country, at a glance.*

Whether RCS is available in a country, and for which contacts, is covered in
[Availability & rollout](/platform/en/channels/rcs/availability).

---

This is one page of the Instasent documentation. For the complete machine-readable index of every guide and API reference, fetch https://docs.instasent.com/llms.txt — start there for full context.