Who Bird is
Bird was founded in 2011 as MessageBird, starting with SMS, and now goes by Bird. It added email with SparkPost and real-time infrastructure with Pusher, and today covers email, SMS, WhatsApp, Apple Messages for Business and voice, with verification and number lookup on top.
It offers official WhatsApp Business access, and it is opening its platform to AI agents through an MCP server and a command line tool. 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: payment and security alerts, delivery updates and, for customers who opted in, campaigns. Each step of a message's life comes back to the module as a signed event, and in supported countries Bird turns a STOP reply into an opt-out for that sender.
How the connection works
One connector in the notifications module talks to Bird's API with a workspace API key, scoped to what the platform needs. Bird's events reach the platform as webhooks signed under the Standard Webhooks specification.
KYC is approved
The module picks the template your team edited in the backoffice and sends an SMS to tell the customer their account is open.
Bird accepts it
Bird takes the message and reports it accepted, then sent once it is handed to the carrier.
The carrier answers
The carrier's delivery receipt becomes a final event: delivered, undelivered, failed or expired.
Events are signed
Each event reaches the platform's webhook with an ID, a timestamp and a signature made with the endpoint's secret, which the platform checks before using it.
Replies come back too
If the customer replies, Bird passes the message on, and in supported countries a STOP turns into an opt-out for that sender.
A fallback for what matters
If a critical alert fails, the module sends it again through another channel or provider within seconds.
Next to other providers
Each channel runs on the provider you prefer, with a second one standing by for critical messages. Bird can carry your SMS and WhatsApp with Twilio, Vonage or Infobip as the backup, or the other way round.
Templates, preferences and opt-outs belong to the module as well, so they survive a change of provider. Moving away from Bird later does not change your apps.
When Bird fits best
A strong fit when
- You want SMS and WhatsApp, and perhaps email later, from one provider.
- You want every event signed under a public webhook specification.
- You send to many countries and want to switch each destination on deliberately.
Also worth a look
- Infobip, when you want a message to move between channels by itself.
- A provider your team already uses: its account becomes a connector too.
How we get you live
The contract
We help you get your Bird account and contract in place, for the countries and channels you need.
Senders and destinations
We set up your numbers and sender names with you, enable the countries you send to, and submit your WhatsApp templates for review.
The keys
The scoped API key and the webhook signing secret stay in your platform's secrets and nowhere else, so every event is proven to come from Bird.
A full test run
Bird sends a test event to the platform's webhook to prove it is accepted, then every template goes to your team's own phones before your first customer message.
