Samsung RCS MaaP

Generate revenue in new and powerful ways.

Business to consumer messaging is a significant revenue generator for operators, while Chatbots and their ecosystems have begun to flourish around the world. Both have become increasingly popular ways for brands and individuals to interact with each other and complete tasks that previously required a separate app. For example, people can order food or a taxi through the appropriate company’s Chatbot. They can receive flight reminders and boarding passes, book and receive movie tickets, and purchase goods from an online store. Samsung RCS Messaging as a Platform (MaaP) provides operators with an entire Chatbot ecosystem and a digital storefront that offers new ways to generate revenue.

Request Specifications



  • Chatbot discovery is built directly into the messaging app via its search and directory functionalities.
  • Search for businesses, brands and services, and select the corresponding Chatbot.
  • Or browse available Chatbots via the directory function.
  • When a Chatbot is selected, the user is brought to an introductory screen that provides more information and allows the user to add the Chatbot to their contacts list.

Rich Content Experience

  • Chatbots can use any of the RCS advanced messaging services, including animated or static images, audio, video, suggested replies, and action buttons.
  • Operators have full control over which RCS services are available to a Chatbot.

Privacy Through Aliasing

  • By default, conversations with Chatbots are in anonymous mode, where an alias is used in place of a person’s identity.
  • Users have full control over their privacy settings on a global and Chatbot-by-Chatbot basis.

Spam Protection

  • Users are only able to receive messages from Chatbots that have their explicit consent.
  • All Chatbots on this service must obey the STOP rule.
  • Users are able to block (and unblock) individual Chatbots, and report Chatbots for violations.


  • The availability of Chatbots (online or offline) are indicated to the user.


  • Users can search, browse, purchase and download stickers directly from the messaging app.
  • Search results include name, descriptions, digital good type indicator, price with tax, and an option to preview image.


  • The Sticker Store also provides users with custom emoji packs for purchase.


  • Any connectivity between the RCS MaaP-enabled client and the Sticker Store is secured end-to-end.

Content Control

  • A staging environment provides review and approval of digital content before being deployed to the storefront.
The RCS Developer Portal provides Chatbot developers with the information and tools they need to deploy Chatbots on the service. Access to technical documentation such as a Getting Started Guide, Chatbot API documentation, tutorials, release notes and FAQs are also provided.



  • During onboarding, information is added that describes the Chatbot and its purpose, including a name, brief and full descriptions, preview image, as well as sandbox and production configurations.
  • Information provided during onboarding is used to facilitate Chatbot discovery through the messaging app.


  • The RCS Developer Portal provides access to a device emulator, which allows a developer to interact with a Chatbot they created and receive responses without needing access to an actual device.

Sandbox Configuration

  • When a Chatbot is first created, only a sandbox configuration is used.
  • Allows Chatbot developers to perform development and test activities with production devices, while being constrained with more constrictive policies regarding file sizes, quotas, and other items.
  • Uses white lists to control which numbers the Chatbot will be able to find and interact with when published.
  • Developer has full control over publishing and un-publishing sandbox Chatbox configurations.

Production Configuration

  • A production configuration allows access to the environment in which the Chatbot exists. This environment has a much less constrained set of policies.
  • When a production configuration is requested to be published by the developer, it is first put into a pending state.
  • Upon approval, the Chatbot production state is changed to published and is accessible by general users.
  • The developer has control over publishing and un-publishing a production configuration.


  • The RCS Developer Portal provides transaction data analytics on a Chatbot-by-Chatbot basis.
  • Data includes messages by type and size, as well as the number of unique subscribers by week, day, hour or minute for the previous 30 days.
The RCS Content Developer Portal is a central location where authorized content providers add and manage digital goods offered through the Sticker Store.


Content Staging and Approval

  • Content developers have access to a staging environment for review and approval of their content before it reaches the production storefront.


  • Products added to the Sticker Store include metadata (names, authors, description, preview icon, etc.).
  • The metadata is used to enhance the search capability of the Sticker Store.
  • For speed and ease of publishing to the Sticker Store, content developers can bulk load digital goods onto the service and add metadata accordingly.

Auditing Tools

  • Content developers are provided with access to the edit history of a digital good, including date and time of a change, type of change (add, update, delete), and what user ID made the change and state (staging, in-approval, published).

Reports generated by monitoring services are accessed from a central location, and provide an in-depth look at how users are taking advantage of MaaP services, as well as how content providers are using it to offer value to subscribers.


Chatbot Monitoring

  • RCS-based events exchanged in either direction are measurable for each Chatbot on a per user and per service (such as 1-to-1 Chat, Group Chat, File Transfer) basis.
  • Traffic that contains payment information, advertising, delivers premium value content, and subscription information are categorized and labeled accordingly.
  • Chatbot monitoring reports include Bot Responses (200, 403, 500 and others), Carrier Responses (200, 403, 500 and others), session length information, number of concurrent sessions, Chatbot data use (total, messaging and file transfer), and the number of users registered with a specific Chatbot (measures popularity).

Sticker Store Monitoring

  • Sticker Store reporting includes the number of sticker packs downloaded by MNO handsets, the most popular sticker packs, the number of unique users downloading packs, and any failed sticker pack downloads.
  • If available, reporting also includes the number of individual stickers sent to non-MaaP clients, the number of stickers sent to other MaaP clients, and the number of stickers sent by sticker name in a conversation.
  • Each digital good includes a unique ID that allows for tracking and facilitates the creation of logs (CDRs).

Payment Monitoring

  • Traffic associated with making payments is labeled and identified as such and made available through reporting.
  • Includes referrals to any third-party websites that are needed to complete a transaction.
  • Reports of all payment requests that have been processed are made available for auditing and remediation purposes.

Request Specifications

Request Specifications