# Keep the next visit close.

Connect the appointment in Messages to a pass in Wallet. Give customers the confirmed details they need, keep the pass current and make it easy to return when plans change.

[Plan your Wallet experience](/demo?product=apple-messages)

[Read the Wallet guide](/docs/guides/apple-messages/wallet)

[Explore Apple Messages for Business](/products/apple-messages)

A visit, always within reach

Find your next travel bag.

DATE

Friday

TIME

LOCATION

City studio

BOOKING

FN2048

FIELDNOTES

Can I move my studio visit to a little later?

We can offer Friday at 11:00 at the same studio. Shall we update your booking?

Confirmed for 11:00. Your Wallet pass now has the new time.

Fictional pass and booking. These controls show the journey without issuing a pass or changing a real appointment.

## Give your next visit a place in Wallet.

An appointment confirmation is useful today. A pass makes the visit easy to find when the customer is on their way. Connect Messages to Wallet so the time, location and booking reference stay together, with a route back to your team when plans change.

Build passes around confirmed visits, reservations, tickets or membership experiences. Your pass service signs and updates the pass; Bird connects its delivery and the surrounding customer conversation.

[Read the wallet guide](/docs/guides/apple-messages/wallet)

## A pass that stays connected to the service.

Build the Wallet experience around a business record that can change. Keep its identity stable, update the relevant details and make the route back to the conversation purposeful.

### Create the pass from a confirmed record

Start with the booking, reservation or membership details your business system has recorded. Choose the appropriate pass type and use your Apple Developer pass identifier and signing certificate.

### Offer the pass in Messages

Return the pass link in the relevant conversation with a clear explanation of what the customer is saving. Keep the important details visible in the confirmation as well, so saving the pass remains a choice.

### Update the existing pass

When a time or location changes, update the underlying business record and publish the new pass details using the same pass identity. Keep the pass and the conversation aligned with the confirmed change.

### Bring the customer back with context

Include a relevant business-contact route in supported pass details. A customer asking about the visit should arrive with the booking context your team needs, ready to change the plan or answer a question.

## Design for the moment the pass is used.

### Put the useful details on the front

Make the time, location and identifying details easy to read. Use the pass’s supported fields for the intended purpose, and review the experience on the devices your customers use.

### Connect updates to the record that changed

A successful chat reply does not update a pass on its own. Connect booking changes to the pass service, handle delivery and refresh separately, and give the customer a clear confirmation in the conversation.

## Wallet questions

### Does adding a pass start a Messages conversation?

Adding a pass and starting a conversation are separate customer actions. The pass provides an entry point; the customer chooses when to message the business.

### Can a pass change after the customer saves it?

Connect pass updates to the issuer and the business record. When a confirmed booking changes, update the same issued pass with the recorded details.

### Does a pass establish permission to send an invitation?

No. Invitation Messages require their own explicit opt-in and Apple approval. Saving a pass does not replace that permission.

### What should happen when a booking is canceled?

Update the pass to reflect the canceled record and give the customer a useful help or rebooking path. Keep the booking system authoritative.

## Connect the pass to the experience

- [Wallet guide](/docs/guides/apple-messages/wallet): Connect the issuer, service record and Messages entry point.
- [Appointments](/products/apple-messages/appointments): Confirm the booking before issuing or updating its pass.
- [Entry points](/products/apple-messages/entry-points): Carry the right service context into the conversation.
- [Journeys](/products/apple-messages/journeys): Keep native interactions and business actions together.

## Give the customer a useful next visit.

Connect your booking or service record to a pass that stays current, with the right conversation within reach.



## Related resources

- [Integrate an Apple Messages customer journey](/docs/guides/apple-messages/api) (docs)
- [What is Apple Messages for Business?](/explained/apple-messages/what-is-apple-messages-for-business) (answer)

[Get an implementation brief](/learn/workspace?topic=apple-messages)
