Wallet passes
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.
Explore Apple Messages for BusinessA visit, always within reach
EXAMPLEFind your next travel bag.
DATE
Friday
TIME
10:00
LOCATION
City studio
BOOKING
FN2048
Fictional pass and booking. These controls show the journey without issuing a pass or changing a real appointment.
The useful thing customers keep
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 guideA 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?
Can a pass change after the customer saves it?
Does a pass establish permission to send an invitation?
What should happen when a booking is canceled?
Connect the pass to the experience
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
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.