STRAX Reach · Omnichannel hubs
Bird SMS and WhatsApp in Reach
Bird, formerly MessageBird, moved its messaging to a new platform API. This adapter uses that API for SMS and WhatsApp and files every reply on the client record.
- Bird platform API
- SMS and WhatsApp
- Token-checked events
Built on Bird's current platform
Reach calls Bird's regional platform host with your workspace API key. SMS and WhatsApp use their own endpoints, and Reach picks one from the address, with a default for numbers that carry no prefix.
Bird delivers received-message events to a webhook you create through its API. Reach reads the event type, takes the sender and text, and lands the message with the channel in the address so the reply returns the same way.
Every send carries the Reach message id as an idempotency key, which means a retried request after a timeout does not deliver the message twice.
Workspaces that started on the older MessageBird dashboard keep their numbers when they migrate, so clients see the same sender before and after the switch. Reach only needs the new platform key and the regional host.
Where it helps
Card activation prompts
Remind a client to activate a new card and answer their activation questions on WhatsApp.
Loan instalment nudges
Send an SMS a few days before an instalment and file the client's reply for the loans team.
Consolidating suppliers
Move SMS and WhatsApp to one Bird workspace while agents keep working in the same console.
Diaspora remittance recipients
Recipients abroad who registered a WhatsApp number get payout notices there, and local senders keep receiving plain SMS receipts.
What you need
-
A Bird workspace
On the current platform, with SMS and WhatsApp numbers set up in your region.
-
A workspace API key
Stored in the STRAX credential vault and sent as a bearer token.
-
A public HTTPS address
For the received-message webhook, with a secret token appended.
-
Reach Core
The records and console behind the channel.
Good to know
This package uses Bird's current platform API. Accounts still on the older MessageBird or Bird Channels API need to move first, following Bird's migration guide.
Questions
Which region host do we use?
The one your workspace lives in, for Europe or the United States. Set it once per environment in the Reach settings.
Does Bird sign its webhooks?
Bird signs with the Standard Webhooks format, which STRAX does not verify yet. Until then a long secret token in the webhook address protects it.
Can we send WhatsApp templates?
Templates are the next addition. Free text works within 24 hours of the client's last message.
What if a send times out?
Reach retries with the same idempotency key, so Bird treats the retry as the same message.
Read more
-
The whole Reach family →
Reach Core and every channel package, with what each one needs.
Add Bird to Reach
Tell us which channels your clients use and we will plan the rollout with your team.
Premium Requires STRAX Reach - Core, which is licensed.
About this listing
| Version | 1.0.0 |
| Author | STRAX |
| Category | Communication |
| Published | 2026-09-24 |
What's inside
| Credential | 2 |
| Global variable | 4 |
| Workflow | 2 |
What happens on install
After the import, and only with your consent, the installer runs:
- Reach - Register Channel : Registers the Bird channel with Reach Core, disabled until its credentials are entered
Free listing
Install it from Feature Marketplace inside STRAX
It builds on STRAX Reach - Core, a premium package. Ask us for a quote to license it first.
Open Feature Marketplace
In your STRAX installation, open Feature Marketplace from the navigation.
Find "STRAX Reach - Bird"
Search or browse to this listing and review the contents disclosure; every package shows what it contains before anything runs.
Install
Choose Install, or "Customise with AI" to adapt the package to your environment first. No licence is needed for free listings.
Bird, MessageBird and WhatsApp are trademarks of their owners, named here only to identify the service this package connects to.
See it on your own systems.
A demo takes an hour, on your data landscape rather than ours.