Samsung RCS MaaP

Generate revenue in new and powerful ways

Chatbots are a way for users to interact with brands and complete tasks using conversational interfaces. For example, a restaurant can provide its customers with a chatbot that lets them easily place delivery orders within a conversation. Samsung RCS Messaging as a Platform (MaaP) enters this space on behalf of mobile network providers to provide an entire RCS-based chatbot ecosystem with a digital goods storefront. These work together to offer mobile network operators with new ways to generate revenue, give users new features that don’t require them to download another app and enable brands to interact with their customers in new ways.

Request Specifications

Features

Chatbots are the central component of Samsung RCS MaaP. They enable user functionality through conversational interfaces that simulate human conversation and allow brands to interact with their customers in new ways. For example, a taxi company can provide its customers with a chatbot that lets their customers easily request a taxi using conversational language.

Chatbot features include:

  • Discovery
    • Chatbot discovery is built directly into the messaging app through search and directory functionalities.
    • Search for businesses, brands, and services, and select the corresponding chatbot.
    • Browse available chatbots using the directory and select a chatbot.
    • When a chatbot is selected, the user is brought to an introductory screen that provides details about it and lets the user add it to their contacts list.
  • Rich content experience
    • Chatbots can use any of the RCS advanced messaging services. This includes animated or static images, audio, video, suggested replies, and action buttons.
    • Mobile network operators have full control over which RCS services are available to a chatbot.
  • Privacy through anonymization
    • By default, conversations with chatbots are in anonymous mode. This is 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 to contact them.
    • Users can block individual chatbots and report chatbots for violations through the messaging app.
  • Availability
    • The availability of chatbots (online or offline) is indicated to the user.

A RCS powered sticker store that can be visited directly within the messaging app. This allows users to browse, buy, and download content to enrich their conversations. This storefront supports both free and paid content.

  • Discovery
    • Users can search, browse, purchase and download stickers directly from the messaging app.
    • Search results include name, descriptions, a digital good type indicator, price with tax, and an option to preview image.
  • Emoji
    • Custom emoji packs are available for purchase.
  • Security
    • 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 made available on the storefront.

The Samsung RCS Developer Portal provides chatbot developers with the information and tools that they need to deploy chatbots on the service. This includes access to technical documentation such as a Getting Started Guide, chatbot API documentation, tutorials, release notes, and FAQs.

  • Onboarding
    • 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.
  • Emulator
    • The Samsung RCS Developer Portal provides access to a device emulator. This emulator allows developers to interact with chatbots that 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.
    • A 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.
  • Reporting
    • 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 Samsung RCS Seller Portal is a central location where authorized content providers can 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.
  • Metadata
    • 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