# Build the journey around the customer.

Connect native messages, customer choices and business actions in a journey your team can review and publish. Reuse templates, prepare language variants and resume requests when the next response arrives.

[Plan your customer journey](/demo?product=apple-messages)

[Read the journey guide](/docs/guides/apple-messages/journeys)

[Explore Apple Messages for Business](/products/apple-messages)

One task, from hello to outcome

01 · Welcome

Understand the request

02 · Choose

Collect relevant details

03 · Connect

Check real availability

04 · Confirm

Record the outcome

Studio visit journey

Reviewed content and connected booking logic.

Customer language

Reviewed

Unavailable slot

Recovery path

Human support

Assigned team

A clear version to operate

Connect the running experience to the conversation it creates.

Illustrative journey design. Preview the content and verify the connected business actions before publishing.

## Build the path from “can you help?” to “all sorted.”

A good customer journey connects more than messages. It remembers the selected product, asks for the missing details, waits for a booking result and returns the confirmation. Bird brings those decisions and actions into a journey your team can review and publish.

Reuse native message templates across service flows, prepare language variants and connect the business actions that finish the task. Keep a clear route to a person when the request needs judgment or the customer asks for help.

[Read the journeys guide](/docs/guides/apple-messages/journeys)

## Reusable content. Connected decisions.

Work on the customer experience as a versioned journey: the messages, branches and business actions belong in the same review, so the published path has a clear meaning.

### Start from the customer’s goal

Choose the task and identify what is already known at the entry point. Define the customer choices that change the path and the business record that establishes completion.

### Compose native interactions

Build reusable rich messages, forms, time pickers and other native content. Keep language variants with their source and review the labels, selected responses and next steps together.

### Connect and resume the work

Call the application responsible for the booking, order or service request. Keep the journey’s state while it waits for a customer reply or business result, then continue from that recorded point.

### Review and publish a revision

Preview meaningful branches, including a refusal and a handoff. Review the exact content and actions before publishing, and keep changes deliberate so an in-progress customer request retains an understandable path.

## Let real-world requests take the time they need.

### Recover without repeating the business action

A booking or payment may complete before a response reaches the conversation. Inspect the recorded operation when recovering, and use the existing result to continue the journey rather than issuing a new consequential request.

### Build with your team or a coding agent

Use the same content and integration contracts whether a developer or an agent prepares the journey. Inspect the proposed revision and permissions, test it with authorized examples and approve publication as a concrete change.

## Journeys and templates questions

### Is a message template the same as a complete journey?

No. A template supplies reusable content. A journey connects messages, inputs, routing and business operations toward an outcome.

### Does a visual preview prove the integration works?

No. Verify the native device experience and the connected business operation separately, including failure and recovery.

### Can we use AI to help author a journey?

Use AI to propose copy or flow changes, then review the concrete content, actions and permissions before publishing.

### How should a coding agent work with the journey?

Provide the documented resource and operation contracts, a safe example and the expected outcome. Keep credentials in the execution environment and require the same controlled publishing process.

## Build the connected journey

- [Journeys and templates guide](/docs/guides/apple-messages/journeys): Follow the practical setup and operational steps.
- [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.
- [AI and human service](/products/apple-messages/ai-conversations): Build AI-assisted Apple Messages conversations with Bird, grounded in business context and authorized actions, with a clear handoff to people.
- [Apple Messages resource library](/products/apple-messages/resources): Find setup guides, native experience advice and provider comparisons.

## Design a journey your team can operate.

Bring the request, content and business actions together. Review the branches, recovery paths and handoff before launch.



## Related resources

- [Integrate an Apple Messages customer journey](/docs/guides/apple-messages/api) (docs)
- [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)
