If you run tours, attractions, or transport, you’ve probably dealt with this exact message:
“Hi, I can’t find my ticket.”
You open the thread and realise they do have what they need. They’re just holding the wrong thing and calling it a ticket. Which is understandable, because the travel industry has managed to create three separate things that all look like “the ticket” at first glance.
The good news is this is fixable, and it’s worth fixing. Travellers are increasingly comfortable using their phones for travel. IATA’s passenger survey found that 90% are interested in using a smartphone that combines features such as a digital wallet and travel documents. If customers are going digital, the documents we send them need to be crystal clear.
The short version
- Booking confirmation: Proof that the purchase happened (usually an email and confirmation number).
- Voucher: Proof of entitlement (what the customer shows to redeem the experience).
- Ticket: Proof of entry (what gets scanned or validated at the point of access).
Sometimes one document does two jobs. Sometimes one document tries to do all three jobs and succeeds only in creating support tickets.
Booking confirmation: “Yes, you booked”
A booking confirmation is the message that says:
“You have successfully booked. Here are the details.”
It usually includes:
- Confirmation number
- What was booked
- Date and time
- Customer details
- Payment summary
- Basic instructions (where to go, what to bring)
What it is not
It’s usually not what gets scanned on the day.
It’s like the receipt after you buy shoes. Useful, reassuring, and proof of purchase. Not something you wave at a door person and expect immediate access.
Example
The customer arrives at the meeting point and proudly shows a bank transaction screenshot.
To be fair, they did pay. They just skipped every other step between “money left my account” and “I am now on a boat”.
Voucher: “I’m entitled to this experience”
A voucher is what the customer presents to redeem what they bought.
It might be:
- A QR code
- A barcode
- A PDF with booking details
- A mobile voucher inside an OTA app
- A digital wallet pass
It often includes operational information like:
- Meeting point
- Check-in time
- What’s included
- Redemption instructions
The key thing
A voucher is often designed for staff validation, not gate access.
It’s the “this person is meant to be here” document.
Where vouchers get messy
Vouchers are especially common when bookings come through OTAs or resellers, because the OTA is effectively issuing the customer-facing proof, while you need something reliable that lands in your system.
Ticket: “Let me in”
A ticket is what grants entry.
It might be:
- A scannable QR code that validates against a system
- A barcode that opens a gate or triggers a check
- A timed entry pass
- A ticket that becomes “used” once scanned
The ticket is what makes access control happy.
What tickets are for
- Gate entry
- Boarding validation
- Timed entry validation
- Anti-fraud control (one scan, one entry, or rules around re-entry)
Example
The customer shows a beautifully designed voucher PDF. Staff ask for the QR code. Customer says, “That is the QR code,” while pointing at a logo.
Everyone stays polite. Everyone gets slightly older.
Why do people confuse them
Because customers are trained by other industries to expect “one thing”.
In airlines, it’s a boarding pass. In concerts, it’s the ticket. In e-commerce, it’s the order confirmation. In tours and attractions, it can be:
- An email
- A PDF
- An app screen
- A wallet pass
- A QR code
- A booking reference
- Sometimes all of the above are sent in separate messages
If you don’t label them clearly, customers will guess. And they will guess wrong at the worst possible moment, usually when they have one bar of signal and a mild panic.
A simple real-world scenario
Let’s say someone books a museum entry on an OTA.
- They receive a booking confirmation from the OTA.
- They receive a voucher in the OTA app or as a PDF.
- Your team expects a ticket QR code to be scanned at the entrance.
If the voucher contains the ticket QR code, great. One document, two jobs.
If the voucher is just “proof of purchase” but the ticket QR code is sent separately, confusion is almost guaranteed unless you signpost it very clearly.
Problems checklist for operators
If you’re trying to work out what needs attention, this is the quick diagnostic.
You may have a booking confirmation problem if:
- Customers contact you asking if the booking “went through”
- Confirmation emails land late or not at all
- The confirmation lacks basic “what happens next” info
- Customers show up with a payment screenshot because they never got confirmation
What to fix:
- Confirmation email deliverability and timing
- Clear subject lines (more on this below)
- A simple “what happens now” section
You may have a voucher problem if:
- Staff regularly have to explain what to show
- OTAs send multiple voucher formats, and it’s inconsistent
- Customers arrive with the wrong document open
- Your team spends time manually matching names to bookings
What to fix:
- Clear voucher wording (“Show this voucher to staff” vs “This is your entry ticket”)
- One consistent redemption flow per channel, where possible
- Better on-page and in-email instructions
You may have a ticket problem if:
- Scans fail frequently
- The wrong QR codes are being sent or displayed
- Staff end up doing manual overrides often
- Fraud and duplicate use become a recurring headache
- Customers need to be online to show their ticket, and that regularly fails
What to fix:
- Ticket format consistency
- Validation logic (and clear fallback rules)
- Offline-friendly ticket display where possible
You may have all three problems if:
- Your support inbox has a constant stream of “where’s my ticket?”
- On-the-day staff spend too much time explaining documents
- Different channels send completely different customer comms
- No one in the business can answer “what should the customer show?” in one sentence
How to reduce confusion quickly
You don’t need a full replatforming to fix most of this. Usually, you need clearer labelling and fewer document types pretending to be the ticket.
1. Rename things in plain English
Use labels customers understand instantly:
- “Booking confirmation”
- “Your entry ticket”
- “Your voucher”
- “Show this QR code at entry”
Avoid vague names like:
- “Order details”
- “Travel document”
- “Proof of purchase”
- “Receipt”
2. Fix the subject lines
Subject lines do a lot of the work.
Good examples:
- “Booking confirmation: [experience name] on [date]”
- “Your entry ticket (QR code): [experience name]”
- “Your voucher: show this at check-in”
Bad examples:
- “Thanks for your order”
- “Your booking details”
- “Important information”
3. Put a one-line instruction at the top of the document
Right at the top, before anything else, add one clear line:
- “This is your entry ticket. Show this QR code at the gate.”
- “This is your voucher. Show this to staff at check-in.”
- “This is your booking confirmation. Keep this for your records.”
This alone reduces a surprising amount of confusion.
4. Make the QR code unmissable
If you want it scanned, don’t make it a treasure hunt.
- Put the QR code near the top
- Make it big enough
- Label it clearly (“Scan this code”)
5. Give staff a simple script for exceptions
When something goes wrong, staff need a calm fallback that doesn’t rely on guesswork.
Example:
- “If you have a QR code, we scan it.”
- “If you don’t, we look up your booking by name and confirmation number.”
- “If it’s an OTA voucher, we use the voucher code here.”
When staff are confident, customers relax.
The bottom line
If you sell across direct, OTA, and reseller channels, document confusion tends to grow with that channel mix. The fix is usually not complicated, but it does need consistency across how vouchers and tickets are generated, labelled, and validated.
Read our companion article, The simple content checklist for selling on OTAs, including a section on voucher instructions and meeting point clarity.