Global - Channel Endpoints: RCS 

RCS or Rich Communication Service messages allow marketers to send messages containing text, images, videos, as well as buttons with links, while at the same time leveraging the RCS specific functionality.
RCS messages require a data connection and need to be activated on the recipient's device.

To enable the sending of RCS messages, you must configure RCS endpoints within the Admin Configuration module. These endpoints serve as the connection points required when setting up and dispatching RCS messages.

Key Configuration Considerations:

  • Message Type-Specific Endpoints: RCS messaging requires different endpoints depending on the message classification:

    • Conversational/Transactional messages require one type of endpoint.

    • Promotional messages require a separate, distinct endpoint.

  • Country-Specific Requirements: Endpoints must be provisioned on a per-country basis. Each country you intend to target must have its own dedicated set of endpoints for the relevant message types.

Example:If you plan to send both conversational and promotional RCS messages across five countries, you will need to configure 10 unique RCS endpoints—two per country (one for each message type).

The following fields can be configured (the ones with an asterisk are required fields) :

  • Name* — Provide a name that reflects the use of this RCS endpoint. This name will be used in the Organization configuration.
  • Type* — Select the type of endpoint here: RCS.
  • Provider* — You must choose the linked RCS plugin to use for this endpoint. Depending on the selected RCS plugin, different connection parameters are required. At this point, Infobip is supported.

    • Note: The type and provider fields can only be selected during creation of a new channel endpoint. When editing an existing channel endpoint, they are read-only and can thus no longer be changed.

  • API-Name* — The API-name attributed to the endpoint and used by the API.
  • Description — Provide a description that reflects the use of this endpoint
  • Channel Opt-out — Select the numeric field, in the main Audience List or extended profile, that should be used to indicate if the contact is opted out for this channel. If for a contact record, this field contains a value that is different from null or zero, this means an opt out for this channel endpoint and the contact will not be targeted by RCS messages based on this endpoint. The value in the OPT-OUT field in the main Audience List is not taken into account in this case.
    Note: When there are multiple RCS endpoints, they can all use the same opt-out field; or each can have their own. This means that a contact might be opted out for certain RCS messages, but not for all.

The following fields are linked to your subscription at the provider:

  • Sender* — This is the Sender ID. It can be numeric (e.g. 74567 or +1-555-987-6543) or alphanumeric (e.g. CompanyName).
  • API key* — The API key required to connect to the Infobip API service.
  • Personal subdomain — This is your personal subdomain at the provider (eg. http://YOUR_NAME. infobip.com). It is sufficient to enter only YOUR_NAME here, not the entire domain name.