Integrations / Customer.io
Customer.io SMS, delivered by Bird
Add Bird as an SMS provider in Customer.io. Your Bird phone numbers sync as senders, your campaigns, broadcasts and transactional messages go out through Bird, and delivery status and replies come back over a webhook.
Drag an icon onto the dots. Use arrow keys to move a focused icon. Press Escape to cancel a drag.
A key, an ID and one webhook
Customer.io connects to one Bird workspace per connection and syncs its SMS-capable phone numbers as senders. Numbers still pending registration in Bird are not ready to send, so they do not sync. Add a connection per workspace if you send from more than one.
- Developers
- API keys
- Create key
- API key
- bk_eu1_…
- Workspace ID
- ws_…
Both must come from the same workspace.
What to expect once connected.Customer.io composes and reports; Bird delivers.
SMS from your synced numbers. No MMS: a message with an image fails, so leave the image field empty. For an alphanumeric sender, claim it in Bird and add it in Customer.io as a manual sender identity.
$ SMS
$ Phone numbers
A category on every message. Customer.io transactional messages go out as transactional; automations and broadcasts go out as marketing. Register your sender in Bird for the categories you send where a country requires it.
$ Transactional
$ Marketing
Status and replies over the webhook. Delivered maps to delivered; failed, rejected, expired and undelivered map to bounced with Bird's error code; a send refused for an opt-out maps to dropped. A STOP reply, or a Bird or carrier opt-out, marks the person as opted out of that sender.
$ delivered
$ bounced
$ dropped
Put it into practice.
Continue with the documentation, guides and examples for this topic.