Who Infobip is
Infobip is a cloud communications platform founded in Croatia in 2006. It sends messages over SMS, WhatsApp, RCS, Viber, email, voice and other channels through its APIs, and it also builds tools for mobile operators, such as SMS firewalls.
It has worked with the mobile industry from its early years, joining the GSM Association in 2007, and it was among the first business solution providers for WhatsApp. Global brands use it to reach customers on the channels they prefer, which is why it is one of the SMS and WhatsApp providers our notifications module connects to.
What it does in your platform
Notifications
Sends the platform's SMS and WhatsApp messages through one API: payment and security alerts, delivery updates and, for customers who opted in, campaigns. Delivery reports come back to the module in real time, and a message whose first channel fails can move to another.
How the connection works
One connector in the notifications module talks to Infobip's Messages API, at your account's own base URL, with an API key that stays in your platform's secrets. Delivery reports come back to the platform's webhook, which Infobip can reach over mutual TLS.
A large withdrawal is made
The module picks the security alert template your team edited in the backoffice, for WhatsApp first and SMS as the fallback.
Infobip takes it
The module sends the message through the Messages API, a single endpoint for every channel.
WhatsApp, or SMS instead
Infobip delivers it on WhatsApp, and if that route fails, its failover can move the message to another channel such as SMS.
A delivery report comes back
Infobip pushes the delivery report to the platform's webhook in real time.
The module records it
The message's status changes in the backoffice, so your team sees what reached the customer and when.
Another provider stands by
If Infobip itself cannot send, the module hands critical messages to the second provider you chose.
Next to other providers
Each channel runs on the provider you prefer, with a second one standing by for critical messages. Infobip's own failover moves a message between channels, and the module's fallback can also move it to another provider, such as Twilio or Vonage.
Templates, preferences and quiet hours belong to the module, not to Infobip. Moving to another provider later does not change your apps.
When Infobip fits best
A strong fit when
- You reach customers in many countries and want one provider for SMS, WhatsApp and other chat apps.
- You want a message to move to another channel by itself when its first route fails.
- You want WhatsApp from one of its first business solution providers.
Also worth a look
- Twilio, when you want messaging and one-time codes for sign-in from one provider.
- A provider your team already uses: its account becomes a connector too.
How we get you live
The contract
We help you get your Infobip account and contract in place, for the countries and channels you need.
Senders and templates
We register your sender IDs and your WhatsApp sender with you, and submit the templates WhatsApp reviews, in each of your languages.
The keys
The API key goes into your platform's secrets and nowhere else, and the webhook for delivery reports is secured, with mutual TLS where you want it.
A full test run
Every template goes to your team's own phones on WhatsApp and SMS, and the failover is tested, before your first customer message.
