Move Apple Messages from Infobip to Bird
Plan the provider transition and rebuild the parts of your Apple Messages service that depend on Infobip. Start with a working inventory of the customer experience, not a direct copy of the old dashboard configuration.
Bird does not provide an automated Infobip history or workflow importer. Confirm the Apple account transition with Bird, Infobip, and the person who owns the account in Apple Business Register before changing the provider connection.
Inventory what the service uses
Record the Apple Business ID, account owner, approved entry points, service hours, languages, native message types, operator responsibilities, and external integrations. Export the records you need to retain using Infobip's supported process and your retention policy.
Use Infobip's current Apple message-type documentation and channel setup guide to identify the features your current flow actually uses.
Map content and behavior
| Infobip service element | Bird destination or required work |
|---|---|
| Text replies | Recreate approved wording in the reply composer or a Text template. |
| Quick replies and list pickers | Recreate choices, sections, selection rules, and received/reply bubbles in Templates. |
| Rich links with automatically fetched metadata | Author the title and PNG preview, or explicitly prepare a supported Apple preview. Do not assume Infobip's automatic metadata behavior carries over. |
| Images and documents | Rehost or retain authorized file URLs and check Bird's media requirements. |
| Time picker | Recreate dated slots and reconnect the booking action; selection does not reserve a slot. |
| Saved selection attributes, repeats, or fallback actions | Implement the corresponding response handling in your service. A Bird template does not execute those Infobip flow actions. |
| Agent queues and routing rules | Map the intended owner and labels to Conversations. |
Check variable values and identifiers in each recreated message. Bird template examples are preview data and its drafts are browser-local. They do not import Infobip attributes, publish a bot, or become a shared content library.
Plan records and open work
Keep historical transcripts in an authorized archive or their existing system. They do not appear in Bird automatically. Record how operators will look up an old case without copying sensitive history into a new message.
Assign a person to each open conversation or pending booking before cutover. Agree with both providers how active sessions and pending messages are handled. Do not assume provider conversation IDs, API credentials, suppressions, or delivery records are portable. Confirm the treatment of the Apple identity and existing entry-point URLs as part of the transition.
Inventory opt-outs and applicable permissions. Preserve them in the new operating process; a provider change does not authorize renewed contact. Recreate relevant suppressions using the correct handle type and scope.
Verify before changing the provider
Complete Bird registration and readiness review. Rehearse a supported customer task with an approved test business and device, covering text, each native type you use, assignment, and a failed external action.
For an API integration, replace Infobip authentication, requests, response parsing, and callbacks with the Bird API flow. Verify duplicate handling and the distinction between gateway acceptance and the business result.
Before cutover, demonstrate every required customer task using the proposed Bird workflow and connected systems. Keep the existing service available until an agreed alternative works for any task you cannot yet complete.
Coordinate cutover and recovery
Agree a change window, provider-connection owner, operator coverage, and criteria for stopping the transition. Keep a record of the previous configuration and a provider-approved recovery procedure. Do not assume that both providers can receive the same live business traffic or that you can split it by percentage.
After the connection changes, test the real entry points, send in both directions, inspect Messages, and confirm the external business result. Monitor failures and unassigned conversations before widening entry-point exposure. Retain the old records for the approved retention period and remove obsolete credentials through your normal access process.