# RCS agent best practices

How to design an RCS agent that gets approved the first time and looks right on every phone: a real, lasting brand identity, a logo that isn't cut off in a circular format, contrast, and choosing your use case wisely.

**Language:** en
**Audience:** platform
**Translation key:** platform.channels.rcs.agent-best-practices
**Search keywords:** rcs best practices, agent best practices, rcs tips, logo legibility, logo contrast, dark mode logo, brand impersonation, choose use case, choose billing category, avoid rejection, rejected agent, agent design
**Related pages:** /platform/es/channels/rcs/agent-best-practices, /platform/en/channels/rcs/agent-profile, /platform/en/channels/rcs/senders-verification, /platform/en/channels/rcs/what-is-rcs
**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/agent-best-practices/ (HTML) · https://docs.instasent.com/platform/en/channels/rcs/agent-best-practices.md (Markdown)
**Other language (es):** https://docs.instasent.com/platform/es/channels/rcs/agent-best-practices.md

Your RCS agent is reviewed before it goes live — and once approved, its data can't
be modified. A few design decisions made early save you a rejection round and make
your brand look right on every phone. This page is advice only: the field specs
and limits live in [Your RCS agent profile](/platform/en/channels/rcs/agent-profile),
and the registration process in
[RCS senders & verification](/platform/en/channels/rcs/senders-verification).

## Be a real brand

An RCS agent represents a **business**, verified as such:

- Use the **brand name your customers already recognize** — not a campaign name, a
  slogan or a product variant. The name is what appears in the inbox; if contacts
  don't recognize it, the verification badge works against you.
- **Never present the agent as a person.** Don't use a photo of a real person as
  the logo or a person's name as the agent name — it's misleading and a reason for
  rejection.
- The verification badge is **added automatically** once the agent is approved.
  It can't be added manually, and it's protected against impersonation — the
  identity you register must match your real organization.
- **Keep the profile general and lasting.** Don't tie it to a campaign, a season, a
  promotion or a collection: avoid banners or descriptions like "Summer Sale",
  "Black Friday" or "Summer collection". Since it can't be freely changed once
  deployed, the profile must represent your brand in a stable way.
- **Each registration is for one specific country.** Configure the agent's name,
  description, visible copy, contact details, terms and conditions and privacy
  policy in the **local language**.
- **The agent's responsible contact must be a real person**, with a first name, a
  last name and a **named corporate email**. Avoid generic addresses
  (`info@company.com`, `marketing@company.com`, `support@company.com`): they can
  hold up or trigger the rejection of the verification.

## A logo that isn't cut off in a circular format

In the conversation your logo is displayed **small and cropped as a circle**:

- Prefer a **simple mark over a logotype with text** — text becomes unreadable at
  avatar size.
- **Center the mark and leave a safe margin** around it, so the circular crop
  doesn't cut into it.
- Check it **on both light and dark themes** — phones render both, and a dark
  mark on a transparent background disappears in dark mode.
- Don't stretch or distort the logo to fit; upload a larger image and use the
  built-in cropper instead.

The fastest check is the panel itself: the
[live previews](/platform/en/channels/rcs/agent-profile#available-previews)
show your logo at real size in the notification, the inbox and the conversation.

![The conversation preview showing the agent logo at small circle size](/platform/en/channels/images/agent-profile--3-preview-conversation.png)
*Judge your logo where it matters: at small circle size in the conversation.*

## A color that reads on white

Your brand color is applied to accents over light backgrounds. Pick a tone with
**enough contrast on white** to stay legible — a pale yellow or light gray washes
out. If your brand palette has several tones, pick the one that reads best, and
check the result on the previews in both appearances.

## A banner that frames your brand

The banner is the header of your agent info page, with your circular logo overlaid
on it. Use a **high-quality image with the focal point centered**, and keep
critical elements away from the edges and the area the logo covers.

![The agent info page preview with the banner framing the brand](/platform/en/channels/images/agent-profile--2-preview-agent-info.png)
*The banner and logo work together on the agent info page — compose them as one.*

## A description that sets expectations

You have 100 characters: say **what your messages are about** ("Offers and booking
updates from Aurora Travel Club"), so contacts know what to expect when they tap
your profile. Avoid generic taglines that don't describe the messaging.

## Choose use case and billing category carefully

Both are set when you create the sender and **can't be changed afterwards**:

- The **use case** decides what you may send. Selecting **Transactional** or
  **Verification codes (OTP)** blocks you from later using the agent for
  promotional content. A typical case is **ecommerce**, which combines
  transactional notices (order confirmations, shipping updates) with promotions:
  for that profile, select **Mixed** from the start.
- The **billing category** doesn't change features — both categories have the same
  capabilities; what changes is how messages are billed.

The registration also includes the **Organization** and **Compliance** tabs, with
your company data and responsible contacts. The details of all these decisions are
in
[RCS senders & verification](/platform/en/channels/rcs/senders-verification#create-the-sender).

## Avoid the common rejection reasons

Most rejections trace back to a handful of avoidable issues:

- A brand color with **too little contrast**.
- A **privacy policy or terms-of-service URL that's missing or unreachable** —
  reviewers do open them.
- A brand identity that **doesn't match the registered organization**.
- Content or description that **doesn't match the declared use case**.

If a registration is rejected anyway, the reason is shown on the register and you
can fix and resubmit — see
[what happens on rejection](/platform/en/channels/rcs/senders-verification#if-a-register-is-rejected).

Beyond design, your agent and its messages must stay within the content Google
allows on RCS. What you can't send — and what can get an agent rejected or
suspended — is covered in [RCS acceptable use](/platform/en/channels/rcs/acceptable-use).

---

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.