Infobip Mobile Messaging

Integrate WhatsApp and RCS mobile messaging channels using Infobip's cross-channel solution to send and receive messages and engage in two-way conversations.

Set up the integration

To set up your Infobip Mobile Messaging provider integration:

1. Open your Bloomreach Engagement project and click Data & Assets > Integrations > + Add new integration.

2. Search for "Infobip Mobile Messaging" and click + Add integration.

   

3. The integration settings page appears. Fill in the fields shown using the account details your CSM or CS team provided.

   1. API Key: Your authentication key, provided for each service plan. You can find it in the Infobip console.
   2. Entity ID (optional): This is your unique identifier for each service plan. It is used to validate API call requests.
   3. Endpoint region: Choose your region based on your domain location and data protection requirements. Options are EU and US.
   4. Sender: Sender name or number to use for sending messages. You must use one of the predefined senders in your Infobip account.

4. Click Save integration to complete your integration.

   

5. Copy the callback URL in the Two-Way mobile messaging field. This URL must be set up in your provider account (Infobip or Sinch) to receive incoming messages.

6. Provide the callback URL to your CSM. They will help set this up on the provider side.

7. Start using the mobile messaging integration and configure any project settings.

Configure default providers

If you have multiple mobile messaging integrations, you can set a default provider for RCS and WhatsApp. This is required to enable two-way messaging.

Your user role must have admin rights to set default provider integrations.

RCS

Set the default provider by going to Project Settings > Channels > SMS / MMS / RCS > RCS provider integration. This default provider will be preselected in any new RCS nodes you create.

WhatsApp

Set the default WhatsApp provider by going to Project Settings > Channels > Mobile messaging > WhatsApp messaging integration. This default provider will be preselected in any new WhatsApp nodes you create.

Event tracking and reports

By default, event tracking for mobile messaging is mapped to the campaign event with the action_type specifying the channel (whatsapp or rcs).

You can optionally map events to a different event name in Project settings > Campaigns > Mapping > Campaign events.

Mobile message event properties

Refer to Two-way messaging and keywords auto responses - Event tracking for more details on event tracking for two-way messaging.

Delivery and read reports

For each mobile message you send, the integration provides real-time Delivery reports and Read/seen reports. These reports help you track when messages are sent, delivered, and seen, offering clarity on message delivery and customer reactions for campaign evaluation.

• Delivery reports: In case of a failure, you will receive a delivery failure status event immediately and an error explanation indicating the reason behind it.
• Read/seen reports: In case the message was delivered successfully, this report will additionally inform you whether the recipient has seen the message. To receive read reports, you must enable receiving read receipts in your WhatsApp > Settings > Privacy section. When disabled, both personal and business accounts have read indicators disabled.

In cases of messages returning rejected or failed statuses, the integration provides error explanations in the error property of the campaign event. For more information on error explanations, see the list of Infobip Error Codes.

Message statuses

Mobile message statuses are as follows: