# Build with your code. Or your coding agent. Build native Apple conversations from your application or with an agent connected to Bird. Create content, connect journeys and operate the customer exchange through the same business identity, permissions and service context. [Discuss your Apple Messages integration](/demo?product=apple-messages) [Read the integration guide](/docs/guides/apple-messages/api) [Explore Apple Messages for Business](/products/apple-messages) One complete native exchange 01 · Business Approved identity 02 · Conversation Customer context 03 · Native message Useful content 04 · Response Connected action The response was interrupted. Check the original operation before deciding to retry. Retain Request and conversation identity Inspect Recorded outcome Continue Documented recovery path YOUR REQUEST Build a studio-visit journey with a native form, available times and a Wallet pass. Show me the changes before publishing. Business Fieldnotes Prepared Form · time picker · pass Connected Booking · service team Example revision published The reviewed journey is ready for the next customer conversation. Reviewed: the booking confirms before a pass is issued. Unavailable times return fresh choices. A person owns escalated requests. Fictional integration and agent workflow. The example controls do not publish a real journey. Use the API contract for exact fields and permissions. ## Keep the conversation close to the business action. Your application knows which appointments are available and when a booking is confirmed. Bird connects that business logic to the Apple Messages conversation: send native content, receive the customer’s response and return the result of the action they chose. Build with your API client or a coding agent connected through Bird’s MCP server. Use the published operation contract and scoped workspace permissions to inspect businesses, prepare content and connect customer journeys to your application. ## Build the complete exchange. Treat the integration as a conversation with a result. Keep its references intact across the native response, application request and customer confirmation. ### Resolve the business and conversation Use the intended workspace and approved Apple business with credentials scoped to the operation. Ordinary replies use the open conversation’s Apple identity; phone-addressed invitations follow their separate approved contract. ### Send native content with a defined response Choose the content type and expected answer. Preserve the message, request and conversation references so a list selection, form submission or time choice can be matched to the intended next step. ### Validate and perform the business action Check the response against current business data and customer permissions. Use your booking, commerce or identity application to carry out the action, with that application’s authorization and recovery behavior. ### Return the recorded outcome Correlate the result and continue the conversation. If an observation repeats or arrives late, resolve it against the existing operation; keep an accepted send separate from the business outcome the customer is waiting for. ## Give a coding agent the same clear contract. ### Inspect and prepare with real context Connect the agent to Bird’s MCP server and provide the relevant integration guide, workspace and redacted business model. Have it inspect existing configuration before preparing content or changes, and keep credentials in the execution environment. ### Review the change before publishing Inspect the exact native messages, journey branches and connected actions. Test a successful exchange and a materially different refusal or uncertain result, then publish the reviewed revision with the permissions your team has approved. ## API and agent integration questions ### Can we copy an Apple gateway request directly into Bird? Use Bird’s current contract, which retains native meaning while applying its own naming, addressing and authentication conventions. ### Can a coding agent build and operate the experience? Connect the agent to Bird’s MCP tools to inspect the workspace, prepare native content and work with journeys. Apply the same permissions, review and confirmation to publishing and customer actions. ### Can a coding agent read the product guides? Use the Markdown alternatives and linked guides alongside the authoritative API description. Marketing examples do not replace the operation contract. ### What should the first integration test prove? Verify the approved message exchange on a real intended device, the returned input, the business outcome and a failure or uncertain-response recovery case. ## Build the connected journey - [API and agent integration guide](/docs/guides/apple-messages/api): Follow the practical setup and operational steps. - [Business registration](/products/apple-messages/registration): Register your brand for Apple Messages for Business with Bird. Prepare the business identity, provider connection, test experience and launch review. - [Rich messages](/products/apple-messages/rich-messages): Create native Apple Messages experiences with Bird using rich links, attachments, quick replies and list pickers matched to the customer’s task. - [Apple Messages resource library](/products/apple-messages/resources): Find setup guides, native experience advice and provider comparisons. ## Connect the exchange to a real result. Review your application, permitted operations and test plan with an Apple Messages specialist. Prove the reply and recovery paths before launch. ## 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)