Skip to content

Help / Entry staff

Connection problems at the door

Keep uncertain requests separate from confirmed admission.

Limited · rollout dependentContent reviewed
Before you begin

Offline check-in queues and synchronization are planned, not available. Printable-roster production use still requires privacy/retention approval and an exercised operating process.

Prepare a fallback

  1. Name a gate supervisor before the event.
  2. Test the venue network and identify one organizer-approved alternate network.
  3. Make sure staff know the venue’s exception process and do not share accounts.

Intermittent connection

If a request is slow or unclear, stop rapid retries and read the attendee’s current state when possible. Retry only after the previous outcome is known; otherwise escalate.

Offline

Tell the supervisor. Do not describe a local scan, cached screen or unconfirmed attempt as a successful Kitix check-in. Follow the venue’s exception process without pretending it is a server record.

After connection returns

Have the supervisor resolve provisional exceptions against current server state. A planned offline feature is not permission to improvise synchronization or change ticket records.

This manual covers implemented web features and clearly marked future work. Production availability depends on rollout and your permissions. About status and legal documents.