RCS gives your customers branded, interactive messages with images, carousels and suggested replies on supported Android devices and networks. On your side it is a full product with its own bots, templates, pricing and reports, so the order you set things up in matters. Do it backwards and your first customer hits a wall.

RCS admin pages live under Admin Panel > RCS.

The order that works

  1. RCS Settings. Platform limits, API access and your admin alerts.
  2. RCS Vendors and Vendor Pricing. Your upstream aggregator connection and what it costs you.
  3. Users. Enable RCS per account and set that account’s rates.
  4. Brands, Bots and Templates. Review these as customers onboard.
  5. Reports and Spam Moderation. Day to day running.

Skipping step 2 is the usual mistake. Without vendor pricing in place you have nothing to check customer rates against, so you can sell below cost without noticing.

RCS Settings, field by field

Open Admin Panel > RCS > RCS Settings. Everything here is platform wide.

Defaults for reseller created accounts

  • Default User Status When Reseller Creates New RCS Users: start them as Pending, so you approve each one, or Active if you trust your resellers to onboard without review. Pending is the safer default while you are learning the product.

General

  • Allow User to Enable Sandbox: lets customers test without live carrier delivery.
  • Maximum Comma Separated Mobiles: the cap on quick send recipient lists. 1000 is the recommended maximum.
  • Maximum Numbers in Opt-in Add: cap when customers bulk add opt-in numbers. 5000 recommended.
  • Max Chat Records: recipients shown per page in live chat, when the chat module is on.
  • Enable Embedded Sign up and Partner Embedded Signup Link: shows a partner signup flow so customers can onboard bots faster.
  • Enable Subscription Expiry Reminder and Send Subscription Reminder Before: reminder emails to the customer and to you, a set number of days before an RCS subscription expires. Worth turning on. Expired subscriptions turn into angry support tickets otherwise.
  • Enable Live Chat Menu for Agents and Users and Live Chat Menu’s Title: adds the live agent chat entry to the top menu with your own label.

API

  • Enable/Disable RCS API: the master switch for programmatic access.
  • RCS API Message if disabled: the message API clients get when it is off. Write something a developer can act on, not just “disabled”.

Admin alerts

Three separate alert groups, each with an on/off toggle, a Telegram ID and one or more email addresses. Invalid email or Telegram values are rejected when you save.

  • Hourly RCS Summary Notification: periodic traffic summary.
  • RCS File Upload/Campaign Notification: fires when customers submit file or campaign sends.
  • RCS Scheduled Notification: scheduled message activity.

Turn on at least the campaign and scheduled alerts before your first real customer. They are how you find out about a large send before the carrier does.

Click Save Changes when you are done. Some fields only appear once their parent toggle is enabled, and saving needs the right role permission.

Related articles