Connect Wallet passes to Apple Messages

A Wallet pass can give a customer a route back to your business in Messages. Your pass issuer creates, signs, distributes, and updates the pass. Bird's Apple Messages integration does not provide a dedicated pass-issuance or pass-update workflow.

Add a contact route to an existing pass

Work with the team or provider that owns your Wallet pass to add a contact action using the business's Apple Messages entry-point URL. Keep the action wording clear, such as contacting the service team about a booking.

Use an intent appropriate to the pass, and keep sensitive account or booking details out of the URL. A pass can be shared or captured in a screenshot; its contact link must not act as an authentication credential.

On a test device, open the pass, follow the contact action, send a request, and confirm that it appears under the correct business in Conversations.

Share an externally issued pass

If your pass issuer provides a secure distribution page, you can send a rich link to that page in an open conversation. Check that the destination verifies the customer's right to the pass and provides a useful explanation if it has expired or been revoked.

The issuer remains responsible for the pass's identity, signing certificate, validity, updates, and revocation. Sending the link does not prove that the pass was downloaded or added to Wallet. Use the issuer's supported evidence for those outcomes.

Test the pass lifecycle

Verify the flow on a supported Apple device with fictional customer data. Check a new pass, an updated booking, an expired pass, and a revoked entitlement. Confirm that a customer can still reach your service team when the pass cannot be used.

If the Messages link opens the wrong business, compare the Apple Business ID in the URL. If the pass fails to install or update, investigate the issuer's response and signing configuration. If the link message itself fails, inspect Messages and events.