Use AI to prepare the door operation and guest list
Check attendees and arrivals, then brief the door team without checking guests in ahead of time.
Try: “Review the guest list and prepare a door-team plan. Do not mark anyone as arrived.”
Define the task
Provide the page, event, date and intended recipients. Agree on totals or a named list. Do not retrieve personal data the task does not require.
Workflow for the AI assistant
- Check the current time and event date. For a past event, produce a retrospective report rather than a future door plan.
- Read the event with events get. Look up events attendees, participants list, checkin stats and checkin list in hap_help.
- Fetch required data with hap_read. Follow every page before calling the result a complete guest list.
- Distinguish invitations, purchased tickets, registered attendees and check-ins. A pending invitation is not an arrived guest.
- Report totals and unresolved differences. An unavailable source does not mean zero guests.
Produce the briefing
Identify the event, report time, expected guests, arrivals and issues needing manual resolution. Agree how to handle missing tickets, duplicate scans and waitlists.
A report does not check guests in. Only use checkin code or checkin scan when the user actually requests a specific arrival and the ticket is identified. Undoing a check-in is also a change.
Sharing and verification
Share a personal list only with the intended team and on instruction. Remote connector exports must return data to the conversation rather than an inaccessible server filename; check command help for the output form.
Reread live statistics at the door. An earlier export does not update itself.