What a wallet pass ticket makes possible across the full visitor journey

The booking agent owns the booking. The operator owns the experience. Neither of those arrangements is changing anytime soon. What can change is what the operator does with the window between booking confirmation and the visitor walking back out the door. This piece makes the case for the wallet pass ticket as a direct visitor relationship channel, from the moment the booking is confirmed.

Somewhere today, a visitor will spend several hours at a destination your team spent months designing. They will buy a ticket, show up, move through the experience, leave. In the Online Travel Agency (OTA) or booking platform's system, they are a confirmed reservation. In yours, they may be nothing: no name, no contact, no record of what they did during their visit, no channel to reach them when you want to bring them back.

This is the foundational tension in tourism distribution. The booking platform owns the distribution and the data. The operator owns the experience — and very often nothing else.

OTAs now account for 37% of all tour and activity bookings, a proportion that has grown consistently and shows no signs of reversing (Arival, 2025). The commission is visible. The data cost is less discussed. When a visitor books through an aggregator, the operator receives a booking reference. The relationship stays with the platform.

The visitor journey is not a single moment. It is a sequence of interactions across days or weeks: researching, booking, preparing, arriving, exploring, leaving, reflecting, deciding whether to return or to tell someone else to go. Most tourism operators are active participants in only two of those stages. The booking platform handles the first. The visit handles the middle. Before and after, the operator is largely invisible.

A digital ticket in Apple Wallet or Google Wallet changes that, beginning at the moment the booking is confirmed.

When the booking confirmation triggers a wallet pass, the operator has established a direct channel before the visitor has set foot through the door. The pass carries the booking details, the entry QR code, and whatever the operator chooses to add: arrival instructions, transport options, what to see first, a reminder that fires on the morning of the visit. None of this requires a dedicated app. None of it requires the visitor to do anything beyond tapping once to add the pass. The channel is open because the visitor is already motivated — they have just purchased an experience they are looking forward to.

On arrival, the entry mechanics are unchanged from any digital ticketing system. The QR code scans. The visitor is admitted. What changes is what the operator can do during the visit itself. A geo-triggered notification when the visitor reaches a particular location within the site. An offer from the cafe that appears at midday. A prompt to visit the new exhibition the visitor has not seen yet. A gamified mechanic: check in at three locations and unlock something. These are not interruptions. They are the kind of contextual, relevant communications that serve the visitor in a way that a one-size announcement over a PA never could.

After the visit, most operators lose the visitor entirely. The pass expires. The booking platform retains the contact. The operator sends nothing, because they have no channel to send through.

This is where the strategic cost of the OTA model is highest, and where a wallet pass programme most directly addresses it. The days before pass expiry are an opportunity: the visitor's experience is fresh, their association with the destination is at its most positive, and they are reachable through a channel they have already opted into. A return offer. An invitation to a member programme. A prompt to write a review or share a recommendation. A seasonal event arriving in the next few months that gives them a reason to come back.

An operator that converts even a fraction of one-time visitors into members or returning visitors has a meaningfully different economics model than one that treats each visit as a standalone transaction. Repeat visitor acquisition costs a fraction of what new visitor acquisition costs. The relationship built through a direct channel is the asset the OTA cannot provide and cannot take away.

The data that flows back through a well-run wallet pass programme is individually attributable in ways that aggregate booking data is not. Not just how many visitors came, but which in-site triggers they responded to, how many days passed before they redeemed a return offer, which segments convert from one-time buyer to returning visitor at what rate. Booking volume tells an operator whether their product is selling. Visitor-level interaction data tells them whether their experience is working.

Wallet pass delivery within the tourism context requires a platform that can handle issuance at booking confirmation, manage pass updates across the visit window, support geo-triggers tied to site locations, and track individual-level interaction data through to post-visit conversion. The Passform platform covers this stack, connecting to ticketing and booking infrastructure via API so the pass is issued automatically when the booking is confirmed and the data flows back into whatever CRM or analytics environment the operator already uses.

The OTA is not going away. For most tourism operators, aggregator distribution is essential and the commission is a cost of doing business in a competitive market. What the OTA cannot give the operator is a direct relationship with the visitor they sent. The wallet pass is how operators take that relationship back, without changing how or where they take bookings. The booking stays with the platform. The visitor journey belongs to the operator.


Can a digital ticket in Apple or Google Wallet replace a paper or PDF entry ticket for a tourist attraction?

Yes. A wallet pass carries the entry QR code or barcode for scanning at the gate, displays booking details, and updates in real time if details change. It works the same way as a paper or PDF ticket at the point of entry. What it adds is a direct communication channel that functions before, during, and after the visit: pre-visit notifications, on-site location triggers, and post-visit engagement mechanics that paper tickets and PDF codes cannot support.

What can a tourism operator do with a wallet pass ticket during the visitor experience?

The operator can push location-triggered notifications when the visitor reaches specific areas of the site, surface time-sensitive offers at relevant moments (a cafe discount at midday, a last-chance gallery reminder before closing), run gamified check-in mechanics, and deliver content that serves the visitor in real time without requiring a dedicated app. All of this uses a channel the visitor has already opted into by adding the ticket.

How does a visitor get a wallet pass ticket after booking through an OTA?

The wallet pass can be issued automatically when a booking is confirmed, regardless of which channel the booking came through. A link is sent by the operator via SMS or email at confirmation, and the visitor adds the pass to their wallet in one tap. The pass can carry the operator's branding and content independently of the OTA's booking confirmation email. The operator's channel is established before the visit begins.

What happens to the wallet pass after the visit?

The pass can be configured to expire after the visit, or it can transition the visitor onto something that persists: a loyalty pass, a return visit offer, or a membership card. The days immediately following a visit are when the visitor's association with the destination is strongest and the conversion to a repeat or member relationship is most likely. A post-visit notification sent through the wallet pass reaches the visitor in a platform they are still using rather than in an inbox where the moment has passed.

How does Passform connect to existing ticketing and booking systems?

Passform connects to ticketing and booking infrastructure via API, so wallet pass issuance can be triggered automatically at booking confirmation without manual intervention. For operators using established ticketing platforms, Passform adds the wallet layer on top rather than replacing the underlying system. The integration approach depends on what the existing stack supports, and Passform's team works through the right connection method for each environment.

Can a digital ticket in Apple or Google Wallet replace a paper or PDF entry ticket for a tourist attraction?

Yes. A wallet pass carries the entry QR code or barcode for scanning at the gate, displays booking details, and updates in real time if details change. It works the same way as a paper or PDF ticket at the point of entry. What it adds is a direct communication channel that functions before, during, and after the visit: pre-visit notifications, on-site location triggers, and post-visit engagement mechanics that paper tickets and PDF codes cannot support.

What can a tourism operator do with a wallet pass ticket during the visitor experience?

The operator can push location-triggered notifications when the visitor reaches specific areas of the site, surface time-sensitive offers at relevant moments (a cafe discount at midday, a last-chance gallery reminder before closing), run gamified check-in mechanics, and deliver content that serves the visitor in real time without requiring a dedicated app. All of this uses a channel the visitor has already opted into by adding the ticket.

How does a visitor get a wallet pass ticket after booking through an OTA?

The wallet pass can be issued automatically when a booking is confirmed, regardless of which channel the booking came through. A link is sent by the operator via SMS or email at confirmation, and the visitor adds the pass to their wallet in one tap. The pass can carry the operator's branding and content independently of the OTA's booking confirmation email. The operator's channel is established before the visit begins.

What happens to the wallet pass after the visit?

The pass can be configured to expire after the visit, or it can transition the visitor onto something that persists: a loyalty pass, a return visit offer, or a membership card. The days immediately following a visit are when the visitor's association with the destination is strongest and the conversion to a repeat or member relationship is most likely. A post-visit notification sent through the wallet pass reaches the visitor in a platform they are still using rather than in an inbox where the moment has passed.

How does Passform connect to existing ticketing and booking systems?

Passform connects to ticketing and booking infrastructure via API, so wallet pass issuance can be triggered automatically at booking confirmation without manual intervention. For operators using established ticketing platforms, Passform adds the wallet layer on top rather than replacing the underlying system. The integration approach depends on what the existing stack supports, and Passform's team works through the right connection method for each environment.