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

# RCS Agent types

> Understand the four RCS Agent types supported by Kero and choose the right type for your messaging use case.

The **RCS Type** describes the kind of messaging your Agent will send to customers.

Kero supports four RCS Agent types:

> **Transactional**
>
> For notifications and updates relating to an existing customer relationship, service or transaction.
>
> **Examples:** Order confirmations, delivery updates, account notifications and service messages.

> **Promotional**
>
> For marketing, sales and promotional messaging.
>
> **Examples:** Special offers, discounts, product promotions and marketing campaigns.

> **OTP**
>
> For authentication and verification messaging.
>
> **Examples:** One-time passwords, login verification, password resets and transaction verification.

> **Multi-use**
>
> For an Agent that needs to send both **Transactional and Promotional** messages.
>
> **Examples:** Order updates, customer service messages and promotional offers from the same Agent.

> [!WARNING]
>
> Choose your RCS Type based on the messages you intend to send. The messaging sent through your Agent must remain consistent with the use case submitted for review.

## Compare RCS Agent types

| RCS Type | Use it when | Typical messages | Don't use it for |
| - | - | - | - |
| **Transactional** | Messaging relates to an existing transaction, service or customer relationship | Order confirmations, delivery updates, account notifications, service messages | Marketing or promotional offers |
| **Promotional** | The purpose of the messaging is marketing, sales or promotion | Offers, discounts, product promotions, marketing campaigns | OTP or authentication |
| **OTP** | You need to authenticate or verify a user or transaction | One-time passwords, login verification, password resets, transaction verification | Transactional or promotional messaging |
| **Multi-use** | The same Agent needs to send both transactional and promotional messages | Order updates, customer service messages and promotional offers | OTP messaging |

## Transactional vs Multi-use

These two RCS Types can look similar, so the key question is whether the **same Agent will also send promotional messages**.

> If the Agent will never send promotional messages, choose Transactional. If the same Agent will send both transactional and promotional messages, choose Multi-use.

### Transactional

A customer places an order.

The Agent sends:

**Order confirmed → Payment received → Delivery update**

The messages relate directly to the customer's existing transaction, so this is a **Transactional** use case.

### Multi-use

A customer places an order and receives:

**Order confirmed → Payment received → Delivery update**

Later, after separately opting in to promotional messaging, the customer receives:

**Enjoy 20% off your next order this weekend.**

Because the **same Agent** sends both Transactional and Promotional messaging, this is a **Multi-use** use case.

> [!NOTE]
>
> If you choose Multi-use, make sure your use case explains both the transactional and promotional messaging you intend to send and how customer consent is managed for each.
>
> Multi-use does not automatically include OTP messaging. Authentication is a separate Agent type in Kero.

## Still not sure?

Ask yourself: **What is the purpose of the message?**

* The message is triggered by an existing transaction, service or customer relationship → **Transactional**
* You want to advertise, promote or encourage a purchase → **Promotional**
* You need to authenticate or verify a user or transaction → **OTP**
* The same Agent needs both transactional and promotional messaging → **Multi-use**

> [!WARNING]
>
> Don't choose an RCS Type simply because it appears to offer more flexibility. Choose the type that accurately represents your intended messaging use case.

Once you've chosen your RCS Type, return to your Agent and complete your use case information.

For guidance on completing the questions, see [RCS Agent use case examples](https://kero.chat/help/product/channels/rcs-for-business/rcs-agent-use-case-examples.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.