Build and publish an Apple Messages journey
Connect native content, customer inputs and business actions into a reviewed service experience.
Prerequisites
Prepare your connected Apple Messages business, customer task, native content, permitted business actions and operating team. Assign owners for the booking, order or identity connections the journey uses. Prepare an authorized test path and representative devices.
1. Map the task and result
Start with the customer’s goal and the record that establishes completion. Work backward through necessary choices, information and identity. Keep messages and business operations distinct.
2. Create reusable content
Prepare the native messages, form pages and choices used by the flow. Give variables clear meaning and use realistic test values. Keep translated action labels and times consistent with the business result.
3. Connect each branch
Route expected answers, free text and unavailable options to useful next steps. Define where the assistant or a person takes responsibility. Avoid a branch that only repeats the same question.
4. Verify the assembled experience
Run the full task on representative devices and inspect the resulting business record. Exercise a refused action, interrupted response and human handoff. Review both the native layout and integration behavior.
5. Publish a reviewed version
Publish the reviewed content, routes, integrations and language variants together. Keep the live version separate from the next draft, and verify that new conversations use the intended release. Keep the operating version identifiable and define who can pause or recover the experience.
Verify a published journey revision
Use a booking journey that collects a preference, presents times and waits for the booking application. Record the content and connected actions included in the revision under review. Test the successful path and a slot that becomes unavailable. Keep in-progress work associated with an understandable revision when a later change is published.
| Test case | Action | Expected result |
|---|---|---|
| The customer replies after a pause | Resume from the recorded request and interpret the reply in its expected context. | The conversation continues at the relevant step. |
| The business action succeeds before the response is observed | Inspect the existing operation during recovery. | The journey uses the recorded result instead of repeating the action. |
| A person takes ownership midway through the flow | Pause automated customer responses and carry the collected context into the handoff. | The customer receives a coherent continuation from the assigned person. |
Troubleshooting
If the preview works but the task fails, inspect the connected operation and its permissions. If a conversation uses unexpected content, identify the running version and branch. A visual sequence alone does not prove that its business actions succeed.
Next steps
- Explore the related Apple Messages capability.
- Find Apple Messages guides and answers.
- Prepare your first complete conversation.
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.
Understand the conceptWhat is Apple Messages for Business?Explore the capabilityApple Messages for BusinessImplementation guideIntegrate an Apple Messages customer journey
Get an implementation brief