RCS Campaign Management
RCS Platform & AI Agent Setup Guide — a comprehensive, step-by-step implementation manual for designing templates, mapping them to agents, launching campaigns, and analyzing delivery reports on the Fonada RCS platform.
About this guide
This document is a comprehensive operational manual structured as an end-to-end workflow from template design through post-launch analytics. Each step includes detailed explanations, best practices, and screenshots of the live UI.
RCS is the next generation of business messaging — supporting high-resolution images, video, carousels, suggested reply chips, and action buttons. Combined with an AI agent, it becomes a two-way conversational channel.
How to read this document
The guide is organized into six core sections that build on each other:
- Template creation
- Template library
- Mapping templates to agents
- Campaign creation
- Campaign dashboard
- Per-recipient reports
| Section | Topics |
|---|---|
| 1. Creating a Template | Basic Identification · Media and Content · Interactive Elements |
| —. Additional Template Types | Carousel · Stand Alone · Text Message |
| 2. List of Created Templates | Anatomy of a Tile · Filtering and Managing |
| 3. Mapping Templates to the Agent | Screen Overview · Filtering by Bot · Mapping Strategy |
| 4. Creating an RCS Campaign | Basics · Select Template · Upload Audience · Review and Launch |
| 5. List of Executed Campaigns | Columns Explained · What to Watch For |
| 6. Reports of Campaigns | Report Types · Filtering · Reading a Row · Export |
What you will be able to do
- Design rich, branded message templates with images, descriptions, and interactive buttons.
- Choose between Rich Card Stand Alone, Rich Card Carousel, and Text Message layouts.
- Manage a centralized library of templates with search and filtering.
- Bind specific templates to specific AI agents for consistent branding.
- Launch mass campaigns by combining a template, audience list, and delivery schedule.
- Monitor delivery in real time and download granular reports in Excel format.
Key concepts at a glance
| Field / Element | Description |
|---|---|
| Template | A reusable, pre-approved message design with layout, media, and interactive elements. Referenced by agents and campaigns. |
| Bot (RCS Bot) | The verified business identity that appears as the sender. Every template is associated with one bot. |
| AI Agent | A conversational entity using an LLM to interpret and respond to messages, configured with mapped templates and a knowledge base. |
| Campaign | A specific outbound send combining a template, audience list, and schedule. Produces analytics in Sections 5 and 6. |
1. Creating a template
A template is a reusable, structured message format. The builder has three sections — basic identification, media/content, and interactive elements — with a live mobile preview on the right.
1.1 Basic identification
| Field / Element | Description |
|---|---|
| Template Name | Short internal ID (max 20 characters, no spaces). Example: welcome_offer_v1. |
| Select Bot | Verified RCS bot; branding inherited from the bot. |
| Template Type | Rich Card Stand Alone, Carousel, or Text Message. |
| Card Orientation | Vertical (image on top) or Horizontal (image beside content). |
1.2 Media and content
RCS supports static media (upload) and dynamic media (variable URL at send time).
| Field / Element | Description |
|---|---|
| Media Height | Short, Medium, or Tall — controls vertical space for imagery. |
| Image / Video / PDF | Direct upload — JPG, PNG, GIF, video, PDF. |
| Variable Image/Video/PDF URL | Dynamic URL with placeholders such as {{mediaUrl}}. |
| Card Title | Bold headline; up to 200 characters with {{firstName}} variables. |
| Card Description | Body copy up to 2,000 characters with formatting and variables. |
1.3 Interactive elements
Up to four suggested replies or actions per template.
| Field / Element | Description |
|---|---|
| Reply | Display Text (user sees) + Postback (machine-readable, max 2048 chars). |
| Open URL | Opens a web link in the device browser. |
| Dial Phone | Initiates a phone call. |
| View / Request Location | Map at fixed address or request user location. |
| Create Calendar Event | Pre-fills a calendar event. |
Click Create Template to save to the central template gallery.
Additional template types
Three layouts optimized for different conversational patterns.
| Need | Choose |
|---|---|
| Single hero card with one CTA | Rich Card Stand Alone |
| 2–10 items in one message | Rich Card Carousel |
| Short utility or transactional message | Text Message |
| Device may not support RCS | Text Message (safest SMS fallback) |
Rich Card Carousel
2–10 horizontally scrollable cards; each with own media, body (160 chars), and up to 2 buttons.
Rich Card Stand Alone
Single media-rich card — ideal for promotions, alerts, and onboarding.
Text Message
Lightweight formatted text without media — OTPs, notifications, reminders.
2. List of created templates
The central template library — single source of truth with filtering, search, and previews.
2.1 Anatomy of a template tile
| Field / Element | Description |
|---|---|
| Preview thumbnail | Scaled-down mobile rendering. |
| Template Name | Internal name from creation. |
| Bot Name | Verified business identity (e.g. Fonada AI). |
| Type tag | Standalone, Carousel, etc. |
| Created date | First saved date. |
| Unique ID | Auto-generated API identifier. |
2.2 Filtering, searching and managing
- Click a tile for read-only preview.
- Action menu: duplicate, edit, archive, delete. Live-bound templates are protected.
3. Mapping templates to the agent
Choose which library templates this agent may send — keeping responses on-brand.
3.1 What the screen shows
| Field / Element | Description |
|---|---|
| Template name | Friendly internal name. |
| Type | rich_card, carousel, text_only — agent treats each differently. |
| Internal ID | Fully qualified ID with bot prefix and suffix. |
| Parameters | Count of dynamic variables ({{firstName}}, {{orderId}}) required at send time. |
3.2 Filtering by bot
Use Filter by Bot in multi-brand environments to narrow visible templates.
3.3 Mapping strategy
- Welcome/onboarding → inbound support agents.
- Promotional templates → outbound marketing agents.
- Appointment reminders → scheduling agents.
- Transactional (OTP, orders) → dedicated agent only.
4. Creating an RCS campaign
A campaign is a controlled mass-send of a template to a list of recipients — a five-step wizard: basics, template, audience, scheduling, and review.
4.1 Step 1 — Campaign basics
| Field / Element | Description |
|---|---|
| Campaign Name | Short unique ID. Convention: channel_audience_offer_date (e.g. rcs_existing_diwali_2024-10-15). |
| Campaign Description | Objective, audience, success metric, approvals — for future hand-offs. |
4.2 Step 2 — Select your template
- Zero-parameter templates need no audience mapping.
- Parameterized templates require matching CSV column headers.
- Return to Step 2 from later steps without losing progress.
4.3 Step 3 — Upload your audience
Upload CSV, XLSX, or XLS with international-format mobile numbers plus parameter columns.
| Field / Element | Description |
|---|---|
| Download Sample CSV | Exact column headers including template parameters. |
| Accepted formats | CSV, XLSX, XLS. Split very large files into batches. |
| Extra columns | Additional metadata columns are welcome for personalization. |
| Validation | De-duplication, invalid format filtering, missing parameter flags. |
4.4–4.5 Scheduling and review & launch
Step 4 sets schedule and speed. Step 5 consolidates all decisions with a summary card.
| Field / Element | Description |
|---|---|
| Launch Immediately | Starts on Launch Campaign click. |
| Schedule for Later | Queued until chosen date/time. |
| Sending speed — Auto | Optimal throughput (up to ~500 TPS per tenant). |
| Sending speed — Manual | Cap 1–10 messages/sec for slow-burn flows. |
5. List of executed campaigns
Operational view for drafts, scheduled, in-flight, and completed campaigns.
5.1 Columns explained
| Field / Element | Description |
|---|---|
| Campaign Name | Internal name; re-runs show "[relaunched]" suffix. |
| Template | Bound template; click to preview. |
| Campaign Status | Draft, Scheduled, Running, Paused, Completed, Failed. |
| Submitted | Messages attempted after validation. |
| Message Status | Sent, Delivered, Read, Failed counters. |
| Success Rate | Share of submitted messages delivered. |
| Created | Launch date/time in local timezone. |
| Actions | Re-run, pause, refresh, download report, upload addendum audience. |
5.2 What to watch for
- Status — Failed rows are urgent (credentials, balance, template approval).
- Success rate — below baseline → drill into Section 6 reports.
- Read counter — drops often signal content issues; A/B test creative.
6. Reports of campaigns
Per-recipient diagnostics with full Excel export for offline analysis.
6.1 Report types
| Field / Element | Description |
|---|---|
| Detailed Report | One row per recipient: phone, reference ID, RCS-capable, statuses, timestamps. |
| Click Report | One row per button tap — measures creative performance. |
6.2 Filtering the data
| Field / Element | Description |
|---|---|
| Date range | From/to dates (default last 30 days). |
| Campaign | Restrict to a single campaign. |
| Search by phone | 10+ digit search for individual enquiries. |
6.3 Reading a row
| Field / Element | Description |
|---|---|
| RCS Capable | "Yes" = RCS delivery; "No" = fallback (e.g. SMS). |
| Sent / Delivery / Read | Independent statuses with Sent At, Delivered At, Read At timestamps. |
| Reference ID | Unique per-send ID for support tickets. |
6.4 Exporting to Excel
Export Excel downloads the filtered dataset as .xlsx. Use Refresh for the latest statuses.
Conclusion
You have walked through every stage — rich-card, carousel, and text-message templates, mapping to agents, launching campaigns, and analysing per-recipient reports. Use this guide as a first-time walkthrough and long-term reference.
Recommended next actions
- Build one end-to-end test: one template per type, one agent, ~20 internal numbers.
- Document naming conventions for templates, agents, and campaigns.
- Decide which template type fits each use case using the guide tables.
- Operationalise analytics: daily dashboard checks and weekly Excel exports.
- Plan A/B tests on imagery, copy, send time, and CTA wording.