Journeys and templates
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.
Explore Apple Messages for BusinessOne task, from hello to outcome
EXAMPLE01 · Welcome
Understand the request
02 · Choose
Collect relevant details
03 · Connect
Check real availability
04 · Confirm
Record the outcome
Illustrative journey design. Preview the content and verify the connected business actions before publishing.
Design the service behind the screen
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 guideReusable 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?
Does a visual preview prove the integration works?
Can we use AI to help author a journey?
How should a coding agent work with the journey?
Build the connected journey
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Design a journey your team can operate.
Bring the request, content and business actions together. Review the branches, recovery paths and handoff before launch.