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.
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.
- 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
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.
The following fields are linked to your subscription at the provider:
- Sender* — This is the Sender ID. It can be alphanumeric or numeric. (eg. Marigold)
- 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)
