In RCS, the content your customers can send is tied to three things they create themselves: a brand, a bot, and templates. Your job is review, vendor submission and cleanup. Here is what each admin page gives you and where the sharp edges are.
RCS Brands
Admin Panel > RCS > RCS Brands
A brand holds company identity, logo, contact and address details, and it is what gets used when a bot is registered with carriers and vendors. Customers create them in the user panel under My Brands. You use this page for support and compliance review.
Filter by ID, user, name or vendor. Rows show the brand profile (logo, name, description, website, industry, contact, city, country), extended brand details, the vendor linkage, and actions to read, delete or export.
Watch out for two things. Logos must meet the size requirement (224 by 224 pixels) on the customer side, and invalid uploads get rejected or cropped there. And deleting a brand that an active bot is using can block sends until the customer picks another brand, so check before you delete.
RCS Bots
Admin Panel > RCS > RCS Bots
The master list of every bot on the platform. Filter by ID, owning user, name or vendor. Each row shows the bot ID, user, logo, registered name, vendor, and status: Approved, Internal approval pending, Disabled or Rejected.
Edit opens a popup where you change status, TPS, capability check, sandbox bot and credentials. Copy for email copies the bot details you need to send for vendor approval, which saves retyping them.
Header actions:
- Sync Bot opens a modal where you pick the vendor and import bots using the credentials stored in RCS Vendors.
- Export downloads the current list.
The usual flow:
- Customer creates the bot in their panel.
- You verify the brand, region and message types here.
- Register it upstream with Create on Vendor or Sync Bot.
- Set TPS and capability check to match your vendor contract.
- Use Map Bot to User if a bot needs to move between accounts.
- Use Update Credentials when the vendor rotates keys.
Before running Sync Bot, confirm the vendor credentials on the RCS Vendors page. A failed sync is almost always stale credentials. Status changes apply to new sends immediately, while messages already queued follow the existing queue rules.
RCS Templates
Admin Panel > RCS > RCS Templates
Templates define the approved layouts: text, rich card, carousel, media, plus the suggested actions. This page is the cross account view.
Filter by ID, user, bot, template name, content type, category, vendor status, system status and creation date range. Rows show identity fields, vendor status, system status, message type, content type, creation time, and actions to read the template payload, delete it, or export (ZIP or CSV).
Status labels match the user panel: Pending, Enabled, Disabled, Deleted, Flagged, Banned, Rejected, Paused. These are what you check first when a customer says their sends are failing. A Flagged or Banned template is a policy problem, not a routing one.
Two behaviours worth knowing. Template names are normalised on save (spaces become underscores) to meet Google’s RCS naming rules, so the name you see may differ slightly from what the customer typed. And deleting an enabled template does not remove it from historical message logs, but any send that references it will fail until the customer uses a new one.
Day to day
Most of your time here is triage: a customer cannot send, so you check the template status, then the bot status, then the brand. In that order, because that is roughly the order things get blocked.
Related articles
- Getting RCS Running on Your Platform
- How to Enable RCS for a Customer Account
- RCS Reports: Message Logs, Summaries and Capability Checks
- RCS Spam Moderation: Approving and Rejecting Held Messages