RCS has a lot of reporting pages. In practice you will live in four of them. Here is what each one is for.
RCS Message Logs
Admin Panel > RCS > RCS Message Logs
Per message delivery detail. This is your troubleshooting and billing dispute page.
Filter by user, bot, mobile number, transaction ID (uuId), global code, message text keyword, and a date range with a calendar picker. With no search applied it defaults to today, and single day navigation shortcuts let you step back and forward a day at a time.
Rows give you the uuId, message ID, mobile, bot, message text, billed amount, message type (TEXT or RICH), direction (A2P or P2A), channel, global code, vendor error code, submit and delivery times, the vendor transaction ID, and the campaign name where it is stored.
Two columns do the heavy lifting. Global Code tells you how your platform classified the outcome. Vendor Error Code is what you quote when you raise a ticket with your aggregator, along with the Vendor Txn ID.
Sensitive JSON keys such as password and username are stripped from the displayed text, so you can share a screenshot with a customer without leaking credentials.
Export uses the same filters as your current search. Narrow the date range first, because wide ranges take a while.
RCS Message Summary
Admin Panel > RCS > RCS Message Summary
Aggregated counts, with a Group By of none, date, user, sender ID or bot ID. Filter by user, bot, sender name and date range.
Columns cover direction, country, message type, and counts for total, success, failed, pending, not sent, others and refund.
How to use it:
- Daily ops review: group by user and date.
- Comparing bots: group by bot ID.
- Refund analysis: the refund column, after a moderation run or a vendor adjustment.
RCS Capability Check History
Admin Panel > RCS > Capability Check History
When capability check is enabled on a bot, the platform asks the vendor whether a handset supports rich content before sending. This page is the audit trail: user, bot, mobile checked, result, the vendor response, and the timestamp, with filters for all of those plus a date range.
Three reasons to open it:
- A customer asks why rich messages fell back or were blocked for specific numbers.
- Capability results come back empty or error, which usually means a vendor API problem rather than a handset one.
- You need the volume of capability API calls, because your vendor may bill for them.
RCS Bot Incoming
Admin Panel > RCS > RCS Bot Incoming
Inbound messages on customer bots: replies, button postbacks and conversational events forwarded by carriers. Filter by ID, user, bot, mobile and date range. Rows show the incoming ID, user, bot name, mobile with a copy control, vendor message ID, event type, the payload, and the received time.
Customers see their own subset in their panel, and bots can forward the same events to a webhook URL configured in the bot settings. Pair this page with Message Summary grouped by P2A direction when you want inbound volume trends rather than individual events.
Which to open first
| The complaint | Start here |
|---|---|
| “My campaign did not deliver” | Message Logs, filtered by transaction ID |
| “The numbers in your report do not match mine” | Message Summary, grouped by date |
| “Rich cards are not showing for some users” | Capability Check History |
| “We are not receiving replies” | Bot Incoming, then the bot’s webhook settings |
| “I was charged for messages that failed” | Message Logs for the amount column, then Message Summary for the refund column |
Related articles
- Getting RCS Running on Your Platform
- RCS Vendors, Vendor Pricing and Customer Rates
- RCS Brands, Bots and Templates: What Admins Need to Check
- RCS Spam Moderation: Approving and Rejecting Held Messages
- How to Set Up Global Error Codes