TAP TAP GO
How the feature helps
Tap Tap Go’s event concept includes NFC check-in, offering a connected way for an organiser to recognise an arrival within the event’s chosen configuration. Confirm how the configured workflow handles repeated attempts and explain the staff response. Keep a manual correction or review process where needed rather than assuming perfect automatic deduplication .
The useful outcome
The attendance record should reflect the intended counting rule and staff should know how to resolve uncertainty. Repeated taps should not automatically become evidence of additional people or stronger event engagement. Clarify how staff should respond when a guest asks whether the first attempt worked. A consistent answer can prevent unnecessary retries before the system’s actual state has been checked.
A hypothetical scene
A guest repeats the check-in action because the first confirmation was unclear. The host checks the event record through the agreed process and avoids treating the second attempt as another attendee.
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.
