Event scenarios
Events are one of the quickest wins for an agent: a fixed body of information, many people asking the same questions, and a short window when answers matter.
Event and summit conciergeS21
The situation
For a recurring event, organizers want an AI concierge that answers attendees' questions about the agenda, sessions, venue and dinners.
The design
- Gather the approved program, FAQ, venue details and itinerary in a Command knowledge folder.
- Train them into an event concierge agent.
- Offer it through live chat, SMS or email.
- Attendees open it by scanning a QR code.
Why
It's quick to build and needs nothing more than an agent and its knowledge. Attendees get instant answers to "What time is dinner?" or "Where is my session?" without queuing at the help desk.
Ask first
- Who owns the event information, and how will schedule changes reach the agent?
- Which channels will attendees actually use?
- What should the agent do with questions it can't answer, and who does it hand them to?
Watch out for
- Personal details in public knowledge. Answers like "Which dinner group am I in?" should come from a verified lookup, not from a document containing everyone's assignments.
- Overbuilding. A Loop or several agents are only needed if you add reminders, scheduled messages, registration or other actions.
- Stale information. Retrain or refresh the knowledge whenever the program changes, and test the answers again.