Define what the customer actually needs at the entrance
An agency can make a correct booking and still leave a traveller unprepared for admission. The confirmation may prove that the service was purchased while directing the customer to collect or retrieve a different ticket.
Start by identifying the item the supplier requires at the entrance. It could be a printable ticket, a mobile wallet pass, an app-based barcode, a voucher exchanged at a desk or another specified document.
Record that requirement for the actual product and booking channel. A rule from another attraction, another country or a previous booking may not apply.
The handover should answer a practical question: what will this traveller present, at this entrance, for this booked service? Once that is clear, the agency can organise delivery, instructions and support around the real admission process.
Keep confirmation, receipt and ticket distinct
Use clear labels in your internal record and customer message. The supplier confirmation identifies the reservation. A receipt records payment. The admission ticket is the item the supplier accepts for entry.
Sometimes one document performs more than one function. In other cases, a confirmation contains a link that must be used to retrieve the ticket later. Establish which situation applies before forwarding material to the customer.
If a document says it must be exchanged, include where the exchange happens, its opening window and the information needed. Do not describe it simply as the ticket if that wording hides an additional step.
If the supplier accepts the reservation reference directly, retain that confirmation and explain the process accurately. The goal is a clear handover, not a rule that every booking must produce the same type of barcode.
Identify the accepted delivery method
Record whether the ticket is delivered as a file, placed in a named account, added through an approved wallet process or collected in person.
For example, Eurostar's ticket help describes options to print tickets or save them on a phone, with retrieval through the booking-management process or app. That provides an example of several accepted routes for one transport provider.
Other issuers use mobile-only admission. Ticketmaster's Mobile Entry guidance says those tickets must be accessed on a phone and cannot simply be printed from the account.
Treat these as supplier-specific examples. The fact that one provider accepts a saved file does not establish that another accepts it. Use the instructions attached to the customer's actual service.
Do not make screenshots the universal backup
A screenshot can preserve information, but its usefulness as a ticket depends on the issuer. It should not become the agency's default answer to every access problem.
Ticketmaster's moving-barcode explanation describes a barcode that refreshes and states that screenshots are not valid for entry. Its guidance identifies approved app and wallet methods for access.
That distinction belongs in the handover. If the issuer requires the live ticket or an approved wallet pass, tell the traveller to use that method rather than sending an image of the code.
For a supplier that permits a printable or downloaded ticket, preserve the complete required document and follow its display instructions. Avoid cropping away the date, ticket category or other information that staff may need.
Use a screenshot for support context only when appropriate, with sensitive codes hidden where they are not needed. Keep that support image distinct from the admission method.
Confirm who each ticket covers
Match the booking's people and categories to the issued tickets. Check the names where relevant, adult and child categories, dates and the number of admissions represented.
One reservation may produce one group code, several individual tickets or a combination of admission and additional-service documents. Count the actual entitlements rather than the number of files.
Ask whether the group must enter together. If one person holds all tickets, confirm how the supplier expects them to be presented and whether separate arrival is possible.
For an illustrative family booking with two adult tickets and one child ticket, three files are not sufficient evidence of a correct handover if one adult file has been duplicated. Match each admission to the relevant guest or category.
Keep the check connected to the supplier reconciliation record so the issued tickets and the original reservation describe the same service.
Record the release status honestly
Some tickets are issued after booking, and some barcodes become available close to the event. Keep the booking-confirmed state separate from the ticket-ready state.
Ticketmaster's delayed-access guidance explains that release timing can depend on the event and directs customers to their confirmation, order or event page for the relevant information.
If delivery is pending, tell the traveller what is confirmed, what remains unavailable and when the agency will check again. Give the issue an owner and an escalation point before departure or admission.
Do not repeatedly resend the same confirmation as if it resolves a missing ticket. First establish whether the supplier's expected release point has arrived.
If a customer is travelling before release, discuss how they will retrieve the ticket during the trip through the approved process. A plan that depends on an account the traveller cannot access needs attention before they leave.
Complete transfers through the issuer's process
Where tickets require an account transfer, use the official method and confirm that the specific order is eligible. The traveller may need to accept the transfer before the ticket appears in their account.
Ticketmaster's transfer guidance explains that acceptance issues a new barcode to the recipient and makes the sender's old ticket invalid.
That means sending an image or keeping an old copy is not the same as completing a transfer. Record whether it was initiated, accepted or still awaiting action.
Let the customer complete sign-in on their own device. Guide them through the official steps without asking them to disclose passwords or authentication codes.
Confirm the recipient address through the agreed booking contact before initiating a transfer. A small typing error can create a significant access problem even where the underlying booking is correct.
Check offline access through the permitted method
A customer who can open the ticket while connected at home may still need an approved way to access it without a reliable signal at the entrance.
Ask the supplier what method it supports. This may involve a downloaded document or an approved wallet or app process. Follow the relevant instructions rather than assuming that every ticket behaves the same way.
Where the issuer recommends opening or saving the ticket before arrival, include that step in the handover and ask the traveller to complete it. Check that the customer can find it again on the device they intend to carry.
A practical rehearsal can happen without using the ticket at an entrance or attempting a validation scan. The customer should identify the event or journey, date, admissions and accepted display method.
Include a charged-phone plan appropriate to a mobile ticket, while keeping any paper alternative conditional on the issuer accepting it. A paper copy of a mobile-only ticket is not a substitute merely because it is convenient.
Explain the time and entrance together
A ticket's printed time can refer to admission, a tour departure, a performance or another service point. Identify what the customer must do at that time and when they should arrive.
Use the supplier's own arrival guidance. Do not invent a universal buffer and present it as the venue's requirement.
Provide the exact entrance or collection point where it differs from the attraction's main address. Include a map link or supplier instruction that helps the traveller recognise the place.
Keep local dates and time zones clear, especially if the agency and customer are in different countries. Preserve the date and named entrance accurately when translating instructions.
Use the translation handover checks for names, times and locations. A fluent message can still send someone to the wrong gate if those details change in translation.
Give named-ticket and identification requirements their own line
If the supplier requires a named ticket or identification, reproduce the actual requirement clearly. Confirm the permitted correction process when a name is wrong.
Avoid assuming that a ticket can be used by another person merely because its barcode opens on a phone. Eligibility and display are different questions.
For a concession, tell the traveller what proof the supplier requires and keep the category matched to the booking. Do not make a general promise based on another venue's student or child policy.
If the requirement is unclear, ask the supplier before completing the handover. The customer should not discover a material condition for the first time at admission.
Keep unnecessary identity documents out of the ticket pack. Share only what the agreed booking and entry process requires through an appropriate channel.
Prepare for groups arriving separately
Ask whether each traveller needs their own ticket or whether the issuer requires a lead guest to present the booking for everyone.
If separate arrival is permitted, complete the official distribution or transfer process and confirm who holds each admission. Keep a record that prevents one ticket from being assigned to two people while another remains undelivered.
If the group must enter together, state that plainly and agree on the meeting point before reaching the admission queue.
For a guided group, make clear whether the guide holds venue tickets or only the agency's service confirmation. A guide may need a separate supplier handover to obtain the actual admissions.
Keep the arrival contact available to the person managing the group. A general sales email is less useful at the entrance than the support route confirmed for that booking.
Reissue the pack after material changes
A changed date, time, guest or product can make an earlier ticket or instruction obsolete. Establish what the supplier has reissued and which old items are no longer valid.
Replace the traveller's operational pack through the agreed channel and identify the change clearly. Ask them to remove or disregard the superseded version where appropriate.
Update linked instructions at the same time. A corrected ticket paired with the old entrance time leaves the handover inconsistent.
Record the current ticket version and the person who checked it. Keep the historical record for reconciliation, while making the valid customer-facing version easy to identify.
For app-based admission, follow the issuer's guidance on refreshing or retrieving the amended ticket. Do not assume that an old downloaded image reflects the change.
Give support a useful escalation record
If access fails, support needs the booking reference, service date, affected guests, issuer, delivery method and a concise description of the problem.
Distinguish the failure: ticket not released, transfer not accepted, account access unavailable, wrong date, unreadable display or admission rejected. Each requires a different next step.
Provide the customer's confirmed contact and the supplier's appropriate support route. Avoid sending full ticket codes into a broad group conversation when a reference and description are enough to begin resolving the issue.
Record the outcome and any replacement issued. If the customer buys another ticket under an agreed resolution, keep the approval and receipt connected to the case rather than leaving the financial decision in an unrelated message thread.
Finish with a traveller-led confirmation
Ask the traveller to confirm three things: they can access the required ticket, they know who it covers, and they know where and when to present it.
That is a stronger completion point than an email-delivered status alone. The agency has checked the practical handover while keeping responsibility for admission rules with the issuer.
Use the same process consistently across transport, attractions and event bookings, adapting the method to each supplier. A reliable ticket pack connects a correct reservation to an entry process the customer can actually follow.
Research was reviewed on 22 October 2026 using Eurostar's ticket-retrieval help and Ticketmaster's guidance on Mobile Entry, moving barcodes, delayed release and transfers. These are provider-specific examples; apply the actual issuer's terms and instructions to each booking.
