Attendee-facing work is fast, high-volume, and easy to lose track of. A single unanswered accessibility request or an unlogged friction pattern is often what attendees actually remember about the event. CT Networks turns attendee-facing work into a tracked workflow where questions, escalations, and recurring friction are all visible inside the event workspace instead of scattered across inboxes, DMs, and on-site conversations.
Attendee questions and support requests attached to the event workspace with registration and session context
Attendee support playbook decides which questions the Guest Concierge can answer and which need a human
Guest Concierge answers inbound questions using event-scoped context and logs activity to a shared history
Operators review and handle anything sensitive, unfamiliar, or outside playbook bounds
Command center surfaces attendee friction patterns and unresolved issues alongside the rest of the event
Instead of scattered inbox threads, DMs, and on-site support conversations that leave no trail, attendee-facing work becomes a tracked workflow with visible escalation, a shared context, and a source of truth for what attendees actually experienced.
The system needs a Guest Concierge coworker, event-scoped attendee context, an attendee support playbook, approval rules for sensitive escalations, and an attendee friction view in the command center.