YOUR BUSINESS / REQUEST HANDOFFA familiar conversation.
A real service behind it.
The studio recorded this visit as confirmed in the illustration. A subsequent choice starts a separate request; the recorded visit stays unchanged until the studio accepts a change.
The requested time is unavailable. The existing confirmed visit, if any, remains unchanged. Choose a current alternative or ask the team.
The booking result is missing. Keep the original request and reconcile it with the studio before another attempt.
Mia owns this request and its original context. Automated booking actions are paused while the service team helps.
The customer has left the conversation. Ordinary follow-up is blocked. Preserve the business record and use the agreed alternate contact or wait for the customer to start a new conversation.
The selected experience and time are pending with the studio. A native picker has returned a choice; the booking system still checks availability and confirms the visit.
This device cannot use the proposed native interaction. Offer the same useful choices as text or continue through the approved alternate contact.
The customer begins at an approved business entry point. A picker selection is a request; the studio checks availability.
FN–1042 · Confirmed by the studio · Friday No current confirmed visitFieldnotes Studio is fictional. This local example changes no booking; the booking system owns confirmation.
Open entry → customer sends → native list choice → pending request → studio decision → reply or human handoff.
What each channel action establishes
Use the selected Apple business and opaque conversation identity. Ordinary messages reply to an open customer conversation; they do not use a phone number, a WhatsApp service window or a WhatsApp template.
Quick replies suit two to five simple choices. Use a structured list or time picker for a richer decision, retain stable reply references, and validate current availability in your application.
Apple gateway acceptance does not establish device delivery or a completed service. Authentication and Apple Pay use their dedicated setup and owners; a payment authorization still needs the merchant’s confirmed processing result.
Invitation Messages need separate entitlement, explicit consent and opt-out handling. Complete Apple registration, connect your provider and pass Experience Review before launch.
Prepare a launch readiness brief
Add your business, region, entry, service-system owner and staffed handoff, then mark the five checks. After any edit, prepare the brief again. Nothing is submitted.
Trace the native payload ↗Open the full readiness checklist ↗