Put the feature into the journey
Tap Tap Go’s ticketing concept connects the event invitation with an organiser-defined attendance process. Define which record the organiser uses and who may correct it. Keep the correction distinct from an attendee transfer or any separate identity requirement. Confirm the actual event workflow before promising self-service editing, and avoid asking guests to create another registration just to fix an ordinary error.
What changes for the reader
The guest should receive a clear explanation of the required next step. Staff can preserve an accurate attendance record without treating every spelling difference as a new person or assuming a digital ticket proves more than its actual event entitlement.
A hypothetical scene
A guest’s booking uses an abbreviated name. The authorised organiser checks the relevant context and handles the correction through the agreed route instead of creating a second attendee record while the guest waits.
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.
