[Apple Messages overview](/products/apple-messages) # Bird vs LivePerson for Apple Messages Bring Apple conversations into Bird with native choices, routing and a named service owner. If your team relies on Conversational Cloud, evaluate its existing automation, structured templates and integrations before planning a move. [Plan your LivePerson migration](/demo?product=migrate-apple-messages-liveperson) [Read the LivePerson migration guide](/docs/guides/apple-messages/migrate/liveperson) ## Compare the work behind the conversation Compare documented channel support, then verify the complete workflow and access available to your business. | Capability | Bird | LivePerson | | --- | --- | --- | | Native experiences | Send supported native content, including list pickers, forms and time pickers, through an approved business connection. | Use Apple-specific Structured Content templates and metadata. | | Service workflow | Connect approved knowledge, business actions and human service with conversation context and explicit ownership. | Connect the Apple experience to the relevant Conversational Cloud workflow. | | Payment and identity | Connect Apple Pay to the merchant and order system, and authenticate account actions through your identity provider. | Use the documented Apple templates, including authentication with the business OAuth service. | ## Where LivePerson fits LivePerson is a relevant choice for teams invested in Conversational Cloud and its structured messaging environment. Its developer documentation describes Apple native templates, including forms, time pickers, authentication and Apple Pay. ## Keep the customer’s task connected. Choose Bird when your service team wants native messages, AI, human conversations and business actions in one operating environment. Compare the complete customer task, including the merchant, identity and booking connections your service needs. ### From discovery to the right team Connect the business entry point to its intended service task and operating group. ### From a choice to an outcome Return selected details to the order, booking or identity system that can validate and act on them. ### From automation to a person Preserve the customer’s goal and useful context when the request needs human judgment. ## Inspect the parts your team will maintain. LivePerson models Apple interactions through Structured Content templates and metadata. Its authentication template connects to the business’s own OAuth service, while its form template defines native pages and answer structure. Compare how your team authors those experiences and handles the returned input. ## Prove the same task and its difficult case. Use an approved test business and representative devices. Compare what the customer sees, how the team authors it and how the business system records the result. ### Native content Test a choice, a longer form branch and the expected returned input. Check the actual device experience. ### Identity and recovery Verify a permitted action, a refused account request and an uncertain integration response. ### Human service and outcomes Transfer to the real operating team and inspect its context. Join the conversation to the completed task and compare the commercial scope. ## Move the service with its meaning intact. Inventory the business connection, Structured Content templates, metadata, Conversation Builder flows, skills or queues, authentication provider and business integrations. Preserve the meaning of page, choice and account references when translating the experience. ## Questions about Bird and LivePerson ### Can we migrate by replacing the API key? Plan the Apple business/provider connection and the service workflow together. Confirm the supported migration procedure before moving traffic. ### Will native templates transfer unchanged? Map the content, variables, choice identities and response handling to the receiving contract. Verify the actual device experience and business outcome. ### Does provider support make Apple Pay ready for our business? The merchant configuration and payment integration still need to be connected and tested. Confirm the transaction in the payment system before confirming the order. ### Which provider costs less? Compare equivalent usage, service environment, integrations, launch responsibilities and support. Use the published or agreed proposal for that scope. ## Prepare your evaluation - [Migrate from LivePerson](/docs/guides/apple-messages/migrate/liveperson): Map the existing business connection, native content and service workflow. - [Get started](/products/apple-messages/getting-started): Build a complete controlled conversation. - [Measure the outcome](/products/apple-messages/analytics): Separate channel activity from the completed task. - [Compare providers](/products/apple-messages/compare): Evaluate the operating and integration experience. ## Primary documentation - [LivePerson Apple templates](https://developers.liveperson.com/apple-messages-for-business-templates-introduction.html): Review the provider’s documented configuration and behavior. - [LivePerson form template](https://developers.liveperson.com/apple-messages-for-business-templates-form-message-template.html): Review the provider’s documented configuration and behavior. - [LivePerson Apple authentication](https://developers.liveperson.com/consumer-authentication-authenticate-in-apple-messages-for-business-overview.html): Review the provider’s documented configuration and behavior. - [Bird integration guide](/docs/guides/apple-messages/api): Connect the business, native exchange and business outcome. ## Keep the customer’s task intact during migration. Inventory your LivePerson entry points, structured content and team workflows. Review the replacement experience and coordinated cutover. ## Related resources - [What is Apple Messages for Business?](/explained/apple-messages/what-is-apple-messages-for-business) (answer) [Get an implementation brief](/learn/workspace?topic=apple-messages)