RCS Campaigns

The RCS Campaigns module allows businesses to broadcast verified, branded, and interactive rich media experiences (including carousels, action buttons, and rich cards) directly to Android native messaging apps. Manage connected carrier aggregators (JIOCX, Smartping, Sparc), select registered bot agents, upload subscriber contact lists via CSV, segment audiences from CRM data, schedule automated launches, and inspect real-time delivery performance, read rates, and detailed failure logs from one unified dashboard.

---

1. Navigating to RCS Campaigns

Main Sidebar ➔ Campaigns ➔ RCS

1. In the main navigation sidebar on the left, click Campaigns to expand the channel menu.
2. Select RCS from the submenu.
3. The RCS Campaigns dashboard opens, displaying all existing broadcasts, connected sender accounts, rich card template types, execution status, and delivery metrics.

---

2. Managing the RCS Campaigns Table

The main campaigns dashboard provides complete visibility over past and active RCS broadcasts.

Table Controls & Customization Options

• Search Input (Search across all columns...): Search any campaign by name, connected bot account, template identifier, or creation date.
• Refresh Button (🔄): Reloads the campaign list and updates delivery metrics in real time without refreshing your browser.
• Columns Menu (Columns): Toggle the visibility of specific data columns in the table to personalize your view (Campaign Name, Account, Template, Status, Sent / Failed, Created At, Actions).
• Order Menu (Order): Rearrange the sequence of table columns or define priority sorting using drag-and-drop handles.
• Create New Campaign (+ Create New Campaign): Opens the RCS campaign builder wizard.

Table Columns Reference

Column Header	Description	Example / Values
Campaign Name	Internal title assigned to the broadcast campaign.	15K_WG_3108, reddybusinessgroup_2608, test012008
Account	The verified RCS bot or aggregator account used to dispatch messages.	WhiteStart, WhiteStart SmartPing
Template	Pre-approved RCS template name and format type.	whitestart_lanuch_promotion [Rich_card], WhiteStart_Intro [Rich_card]
Status	Current operational status of the campaign batch.	sent, failed
Sent / Failed	Ratio showing successful transmissions versus failed messages.	8,518 / 1,948, 374 / 19, 10,241 / 4,770
Created At	Timestamp when the campaign was created and queued.	Aug 31, 2026 1:02 PM, Aug 26, 2026 6:02 PM
Actions	Action triggers to inspect performance metrics.	Click 👁 View to open detailed campaign analytics.

---

3. Creating an RCS Campaign

Click the orange + Create New Campaign button at the top right of the campaigns page to open the campaign builder.

Step 1: Channel & Sender Account Selection

1. Under the top channel bar, select RCS (highlighted with a purple border, alongside WhatsApp, SMS, Email, and Voice).
2. Review the Sender Account cards:
   • WhiteStart JioCX Bot (jio): Shows the verified Jio Agent ID (e.g., Agent Id: ab4aeebc-96cb-43ca-a3b1-dbcc2c56ae04).
   • WhiteStart SmartPing (smart-ping): Shows the Smartping Agent ID (e.g., Agent Id: WhiteStart_2026).
   • WhiteStart (sparc): Shows the Sparc Assistant details (e.g., Assistant Id: 699bf763c0a936f0f3d8880b).
   • Click to select the sender bot you want to use for this campaign.
3. Enter a descriptive Campaign Name (e.g., New Launch Plan, 15K_WG_3108).

---

Step 2: Message Template Selection

1. Click on the Message Template dropdown to choose an approved RCS template.
2. Select your approved rich card template (e.g., whitestart_lanuch_promotion with the orange approved badge).
3. Once selected, the rich card layout, verified brand header, and action buttons render immediately inside the Mobile Preview pane on the right side of the screen.

Tip

• Take advantage of rich media (high-resolution images, carousels, action buttons).
• Include suggested replies and URL action chips to guide recipient interaction.
• Ensure fallback SMS is configured for devices or carriers that do not support RCS.

---

Step 3: Selecting Target Audience

WhiteStart provides two distinct audience targeting modes:

Option A: CSV Upload

Send broadcasts to imported customer lists or external phone sheets.

1. Under 2. Target Audience, select the CSV Upload tab.
2. Click Choose file and select your recipient list (e.g., test2_whitestart.csv).
3. Ensure the CSV includes dedicated phone number columns with country code prefixes. Only .csv files are accepted.
4. Once processed, the validation card confirms:
   • File processed successfully
   • Total count of valid recipient records (e.g., 4 valid records found.).

Option B: CRM Segment

Send broadcasts to dynamically filtered subscriber segments directly from your built-in CRM database.

1. Under 2. Target Audience, select the CRM Segment tab.
2. Click the Select Segment dropdown:
   • All Active Users: Broadcasts to all active registered CRM contacts.
   • VIP Customers: Targets high-value customers and engaged buyers.
   • Inactive > 30 Days: Re-engages dormant leads and inactive users.

---

Step 4: Scheduling & Campaign Launch

Under 3. Schedule, configure when the campaign should be dispatched.

• Immediate Launch: Leave the Schedule Campaign toggle switched OFF and click the orange 🚀 Launch Campaign Now button to start instant delivery.
• Scheduled Launch:
  1. Toggle the Schedule Campaign switch to ON.
  2. In the Select Date & Time picker, configure your target future date and exact time (e.g., September 8th, 2026 at 23:33).
  3. Click the orange 🚀 Schedule Campaign button to queue the batch.

---

4. Viewing RCS Campaign Analytics & Performance

From the main campaigns table, click 👁 View in the Actions column next to any campaign to open its dedicated analytics dashboard.

Top Metric Summary Cards

• Total Messages: Total recipient records queued in the broadcast (e.g., 10,466).
• Success Sent: Total messages successfully transmitted to the RCS network (e.g., 8,518 | 81% success rate).
• Delivered: Total messages delivered to handsets with active RCS capability (e.g., 4,866 | 57% delivery rate).
• Read: Messages opened and rendered in the recipient’s Google Messages / Samsung Messages app (e.g., 1,952 | 23% read rate).
• Failed: Messages rejected due to inactive RCS handsets, network errors, or rate limits (e.g., 1,948 | 19% failure rate).

Visual Analytics & Engagement

• Message States Donut Chart: Visual summary displaying the proportion of Delivered, Failed, Read, and Success sent messages.
• Engagement Timeline Graph: Real-time chronological tracking showing recipient reads and interactions across dates (e.g., spike on Sep 02 tapering through Sep 08).
• Mobile Preview: Exact preview of how the verified RCS card, brand identity (WhiteStart Verified Business), and text look on recipient handsets.
• Top Failure Reasons: Itemized breakdown of delivery errors returned by RCS infrastructure:
  • User Not Found (Handsets without active RCS support or Google Messages disabled)
  • Too many requests (Carrier rate limits)

---

5. Inspecting Detailed Live Message Logs

To audit individual recipient delivery timestamps, statuses, and carrier responses, click the orange View Detailed Logs button in the top right of the campaign analytics view.

Live Message Logs Modal Controls

• Search Input (Search Phone...): Quickly filter logs by typing a specific recipient phone number.
• Status Filter (Failed / No Answer ▾ / All Statuses): Filter the log modal by specific execution status:
  • All Statuses: Shows all records.
  • Sent: Messages dispatched to the carrier aggregator.
  • Delivered: Confirmed delivery to handset.
  • Read / Answered: User opened and read the rich card.
  • Failed / No Answer: Handset delivery rejections (as shown in the filter dropdown).
• Refresh (🔄 Refresh): Fetch live delivery receipts and read statuses in real time.
• Download CSV (⬇ Download CSV): Export the full campaign audit log with all recipient phone numbers, timestamps, and error descriptions into a spreadsheet.

Message Logs Data Schema

Field Name	Description	Example / Values
Recipient	The recipient’s normalized phone number with country code.	918108256227, 918129550141, 918108702817
Status	Current carrier delivery status badge.	failed (red), Delivered (amber), read (orange)
Sent At	Timestamp when the message was dispatched.	Aug 31, 13:16
Delivered At	Exact timestamp when the carrier delivered to the handset.	- (or 13:16:22)
Read At	Exact timestamp when the user opened the chat.	-
Error	Carrier failure reason or handset compatibility error.	not_found User Not Found

Note

If a recipient logs the error not_found User Not Found, the recipient handset or SIM carrier does not have active Google RCS / RBM support enabled. Configure an automated fallback workflow to deliver via SMS whenever RCS delivery encounters not_found.