Ushers, Lobby Attendants, and Ticket Takers

The work of Ushers, Lobby Attendants, and Ticket Takers engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.

+29 more via engagesIn

Ushers, Lobby Attendants, and Ticket Takers involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.

+29 more via involvesActivity

Ushers, Lobby Attendants, and Ticket Takers performs 23 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.

+11 more via performs

Ushers, Lobby Attendants, and Ticket Takers is typically employed by 59 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.

+47 more via typicallyEmploys

Ushers, Lobby Attendants, and Ticket Takers is employed across 55 settings — the places where this role's work is done, and where digital employees first sit beside the humans.

+43 more via employs

Ushers, Lobby Attendants, and Ticket Takers uses 6 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.

Ushers, Lobby Attendants, and Ticket Takers relies on 8 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.

The software Ushers, Lobby Attendants, and Ticket Takers reaches for already exposes 12 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.