Connect a Wallet pass to Apple Messages

Give a customer a pass they can save and return to for an appointment, event or service. Connect the issued pass to the record that owns its details, then add a Messages entry point for help with that task.

Prepare the business’s pass issuer and signing configuration, the booking or service system, and an approved Apple Messages business. Assign an owner for pass issuance, updates and customer support. Use an authorized test environment and test device.

Start with one confirmed booking or service. Identify the fields that belong on the pass: a recognizable business name, date, time, location and useful reference. Retrieve their values from the record that owns the service.

Keep a proposed booking distinct from a confirmed one. A pass should reflect the state the customer can rely on. Follow the appointment guide when the pass represents a reservation.

Connect the pass issuer to the service record and retain the association between the original pass and that record. Configure the branding and the details the customer needs at the point of use. Follow Apple’s pass identifier and signing requirements and the issuer’s distribution workflow. Configure the pass update service so changes reach the existing pass.

Test the issued pass on the intended device. Confirm that the displayed details match the service record and remain readable at normal text size.

Connect the pass to the approved Apple Messages business with the relevant service intent and receiving group. Use a safe reference for the task; keep account credentials and protected details outside public URLs.

Open the pass entry point, send a first message and confirm that the intended team receives the conversation. Retrieve protected booking or account information through the normal identity checks. Use the entry-point guide for context and routing.

When a customer changes a reservation, validate availability and confirm the change in the booking system. Update the existing pass with the recorded time and location. The saved pass and the conversation should now describe the same appointment.

If the booking result is uncertain, inspect the original operation before issuing another update. Do not replace a confirmed time with an unconfirmed request.

Cancel a test booking and confirm that the pass reflects the canceled state. Check expiry, a changed location, an unavailable update service and a customer who continues through another channel. Preserve a useful way to reach the service team.

Saving a pass does not establish permission for an Invitation Message. Keep the invitation consent and approval path separate from pass distribution.

Save an authorized example pass, then change the appointment in your booking system. Publish the new pass contents through your pass service using the same pass identity and verify the updated details on the device. Also check the customer-facing confirmation in Messages; it should describe the change the booking system recorded.

If the pass is stale, compare the business record, issuer state and update result before generating a replacement. If its Messages link opens the wrong team, inspect the business identity and entry-point context. If a customer cannot add the pass, provide the confirmed service details through an appropriate alternative.