Google RCS Business Messaging channel activation

Guidelines for the activation of Google RCS Business Messaging in Aura

Create an RBM account

  • First, fill the following form to create an RBM (RCS Business Messaging) account.

  • After that, wait until Google answers your request or contact them to speed up the process.

  • Once you receive the confirmation, you will be sent an email with another form to create your partner account.

  • Following the previous instructions, you will be able to create and configure new agents.

rbm-console

Configure a new agent

  • To create a new agent, go to the RBM console and configure your agent with the desired parameters.

rbm-create-agent

  • After that, configure your channel to handle all the messages. First, create your channel with a configuration similar to this:

rbm-channel-config

There are some fields in the rcs configuration that must be obtained from the RBM console:

  • The agentId value can be found in the overview section in your agent configuration:
    rbm-agent-info

  • The clientToken can be a custom value or a generated one in the web. It will be used later when the webhook is configured.

  • The email and privateKey can be obtained in the RBM console, creating a new private key inside the partner account settings:

    rbm-create-private-key

    This action will return a json file with all the information, including email and privateKey
    rbm-private-key

    Important: the field privateKey must be stored in aura-configuration-api in a base64 format.

  • With the channel configured, add your endpoint to the webhook agent configuration:
    rbm-configure-webhook

To configure the webhook, set the public endpoint of your bridge:

https://svc-{{ENVIRONMENT}}.auracognitive.com/aura-services/v1/rcs/channels/{{CHANNELID}}/messages

And set the client token with the value configured in the field rcs.clientToken within the channel configuration.

If the values are properly configured, the web will return a success message. All these values stored in aura-configuration-api must be consolidated in the aura-config-provision repository.