Move Apple Messages from LivePerson to Bird
Rebuild the Apple Messages interactions and operating process your service uses in LivePerson, then coordinate the provider change. Bird does not automatically import LivePerson conversations, skills, bots, or Structured Content.
Confirm the transition with Bird, LivePerson, and your Apple Business Register account owner before changing a live connection. A template that looks similar in a browser is not proof of equivalent runtime behavior.
Inventory content and service ownership
List the Apple Business ID, entry points, intent and group values, skills, bot flows, agent responsibilities, supported languages, integrations, and pending customer tasks.
Keep the original Structured Content and metadata together for review. LivePerson's rich-messaging documentation and Apple form template describe the source model; Bird's public API uses a different content envelope.
Rebuild the native interactions
| LivePerson element | Bird destination or required work |
|---|---|
| Structured Content text and rich-link elements | Recreate Text or Rich link content; rebuild the request envelope for API sends. |
| List or quick-reply metadata and bubbles | Recreate choices, identifiers, sections, and received/reply bubbles in native templates. |
BusinessFormEvent pages and start page | Rebuild the Form page types and routes. Match identifiers, summary behavior, required inputs, and answer values. |
BusinessChatMessage presentation | Review the received and reply bubble text and images separately from the form pages. |
| Time-picker slots | Recreate dated times and implement the booking step separately. |
| Custom app interaction | Supply the published identity and payload through App experience; verify it on a device. |
Do not paste the LivePerson JSON into Bird's generic send body. Review the Bird API contract and map the content your service needs. Check image formats and sizes against Bird's media requirements.
Map skills and bots to an operating process
LivePerson's entry-point guide describes using intent for its customer-type context and skill routing. Retain the business meaning of those values, then define how your Bird service uses them.
Bird Conversations provides assignment and labels. Identify the operator or connected service responsible for each route, and verify how it receives the conversation. Recreate the staffing and escalation rules your team needs before cutover.
If replacing an assistant, keep one active engine for the channel. Human takeover must pause automated replies. Verify ownership at cutover so an old bot cannot continue answering alongside the new service.
Preserve history and resolve open work
Use LivePerson's supported export or retrieval process for the historical records your organization must retain. Its conversation-retrieval API documents available record types. Keep access and retention controls on the archive; Bird does not automatically display those transcripts.
Inventory open conversations, assignments, unresolved cases, and external operations still awaiting results. Agree their treatment with both providers. Do not assume conversation identifiers, skill IDs, transcripts, or pending actions transfer with the Apple business identity.
Preserve valid customer opt-outs and permissions. Map applicable suppressions by handle and scope rather than importing an unrelated channel's subscription rules.
Rehearse and change the provider connection
Complete Bird's registration and review requirements. Rehearse the supported service on an authorized Apple device, including a form branch, a human takeover, an unavailable external system, and the final business confirmation.
Agree the connection-change owner, timing, operator coverage, and a provider-approved recovery procedure. Confirm the Apple identity and entry-point treatment explicitly. Do not assume simultaneous delivery to both providers or percentage-based traffic splitting.
After the change, follow each live entry point and verify incoming messages, replies, assignment, native answers, and external actions. Inspect message events and metrics. Remove obsolete bot credentials and callbacks through your normal access process after the transition is verified.