This guide walks through the five steps to send your first RCS campaign. Each step links to the relevant reference so you can go deeper when you’re ready.
Steps 1–2 can run in parallel with steps 3a/3b. You do not need an approved agent to start importing contacts or building templates.
1

Send your first RCS message — sandbox

Before committing to full agent approval, verify that RCS works on your device and that the API integration is correct. The Test Agent is a shared, already-approved agent — no setup required.What you’ll do:
  • Create an API key in the dashboard
  • Register and verify your phone number (OTP)
  • Send up to 5 real RCS messages to your device — rich cards, text, suggestions all work
This step takes under 10 minutes.

RCS sandbox quickstart

Full step-by-step with curl examples.

Our philosophy

Why we built the sandbox first.
2

Set up your production RCS agent

A production agent is your brand’s identity on the RCS network — name, logo, description, verified website, and industry. It goes through Google and carrier review before you can send to production numbers.What you’ll do:
  • Create a draft agent via POST /v1/rcs/agents or the dashboard
  • Upload brand assets (logo, brand colors, description)
  • Submit for Google/carrier review
Timeline: Approval typically takes days to weeks depending on market and carrier. Start this early — you can build contacts and templates while it processes.
If you plan to use RCS newsletter campaigns, set newsletter_enabled: true at agent creation — it cannot be added later. See Newsletter enablement.

RCS agents (learn)

Lifecycle, approval, and newsletter enablement.

RCS API

Create, submit, and track agent approval via API.
3

Build your audience

Contacts are the people you’ll message. You can import them manually or sync from your existing tools.
Best for: One-time imports, migration from another platform, or smaller lists.
  1. Prepare a CSV with your contact fields (name, email, phone, custom fields).
  2. Use the dashboard Contacts → Import flow to upload and map fields.
  3. The platform deduplicates by email hash and creates or updates records.
  4. Apply tags during import to pre-segment your audience.
Consent records are attached during import — make sure your CSV source reflects valid consent for the channels you plan to use.

Contacts (learn)

PII, consent, tags, segments, and channel addresses.

Landing pages

Opt-in forms, DOI flows, and consent capture.
4

Create your first RCS template

Templates are reusable message definitions — rich card layouts, carousel structures, or plain text — tied to a channel and message type. When your agent is approved, you reference templates in campaign send nodes.What you’ll do:
  • Go to Templates in the dashboard
  • Select your RCS channel and message type (MESSAGE or NEWSLETTER)
  • Build your content: title, description, media URL, and suggestion chips
  • Add brand kit elements (logo, colors) so every send is on-brand
  • Publish the version — campaigns reference immutable published snapshots
You can build and publish templates before your agent is approved. Just make sure the template’s channel matches the agent you’ll use for sending.

Templating (learn)

Versions, brand kits, and channel fit.

Introduction to templates

Concepts: versions, approval state, and API usage.
5

Send your first RCS campaign

With an approved agent, a segment of contacts, and a published template, you’re ready to launch.What you’ll do:
  • Go to Campaigns → New campaign
  • Choose a trigger (scheduled, manual, or API)
  • Define your audience by selecting a segment
  • Add a SEND node, pick your RCS channel and template
  • Review estimated audience size and projected cost
  • Launch — the platform executes each contact’s flow asynchronously
After launch:
  • Monitor delivery rate, read rate, and reply rate in the campaign dashboard
  • If the campaign pauses (balance insufficient or provider issue), fix the root cause and call POST /v1/campaigns/{id}/resume
  • Set up webhooks to receive real-time delivery events in your backend

Campaigns in depth

Node types, execution states, segments, and idempotency.

Campaigns API

Resume endpoint and API-triggered launch.

Webhooks

Real-time delivery and engagement events.

Billing quickstart

Balance, holds, and auto-reload before large sends.

​
What comes next

Once your first campaign is live, these are the natural next areas to explore:

RCS agents

Agent lifecycle, approval, and newsletter enablement.

Events & analytics

Delivery, read, and click events for dashboards and campaign automation.

Email campaigns

Add email as a second channel — same campaign builder, different channel.

A/B testing

Use AB_TEST nodes to split your audience and compare message variants.