Plan an Apple Messages customer journey

A customer journey describes how your service takes a request from an entry point to a confirmed result. Use this guide to prepare your service design and registration evidence.

Prepare this service plan during onboarding, then follow Build an Apple Messages experience for the message script, menu choices, handoff, and recovery instructions.

Define one complete customer task

Choose a task with a clear finish, such as arranging a store appointment. Describe the entry point, the information needed, the person or system that acts on it, and the confirmation the customer receives.

For an appointment service, a workable design is:

1. Start: The customer opens the store's message button and requests a visit. The website owner maintains the entry point, and the service team monitors incoming work.
2. Choose: The customer selects a visit type and an offered time. An operator or integration obtains current availability and sends a native picker.
3. Reserve: The customer waits while the selected time is checked. The booking system accepts or rejects the reservation.
4. Confirm: After a successful reservation, an operator or integration sends the reference, time, location, and change instructions.
5. Recover: If the slot is unavailable or an error occurs, the service team offers another time or a conversation with a person.

The picker and its returned answer are supported message interactions. The connection between the answer and your booking system must be built or performed by an operator.

Specify the failure paths

Write the response and the responsible person for each realistic interruption:

• The customer cancels, does not answer, or changes the request.
• A native interaction is unavailable on the customer's device.
• A slot or product becomes unavailable after it was offered.
• An external system times out after it may have completed the action.
• The request arrives outside staffed hours or needs a human decision.
• The customer closes the Apple conversation.

For uncertain external results, check the original operation before repeating it. Use a reference that connects the customer exchange with the booking, order, or case. See outcome measurement for how to keep those records distinct.

Prepare content and operations

Create the supported templates and review their language, variables, bubbles, and alternative text or web path. Keep customer-facing wording consistent with what your service can actually do.

Assign ownership of incoming conversations, escalation, and service hours. Practice the handover with the conversation tools. Make the handover explicit: assign a real operator and pause any connected assistant before the operator replies.

If you plan automated assistance, define one active assistant engine for the connected channel and an explicit ownership transfer to a human. Follow AI and human service planning.

Gather launch evidence

Record a complete device-to-operator exchange and the corresponding business result. Include a failed path and its recovery. Inspect the message record, external operation, and customer confirmation separately.

Use the readiness forms and submission controls described in registration. Use the recorded customer exchange and business result as evidence for the review.