Keep the guest's journey in order

An event offer explains what attendance includes. The supported purchase process addresses payment, while ticket entitlement and check-in answer who may attend and who actually arrived. Presenting these stages separately helps guests understand the sequence and gives organisers a clearer way to resolve questions when the purchaser and attendee differ.

Design for an ordinary exception

Explain what a guest should do if the confirmation is missing or the ticket was bought by someone else. Use the current organiser configuration rather than inventing automatic integrations between financial records and entrance systems.

Imagine this

Hypothetical worked scene

In a hypothetical workshop, a manager purchases a place for a colleague. The organiser connects the appropriate order record to the attendee details and follows its configured check-in process. The financial event and arrival remain distinct, allowing reception to welcome the guest without demanding that the attendee's name match the purchaser's financial record.

Make it practical.

Use this checklist as you read. Checks are not stored.

References & further reading

Tap Tap Go Journal: publisher and product context ↗

Published by Tap Tap Go. Product availability and eligibility vary by programme and market. About our stories.