Events / Hospitality / FMCG
Event operations
A global consumer brand ran event programmes where registrations, guest lists, cancellations, communications and logistics each lived somewhere slightly different. At any scale, keeping those in step across separate forms, channels and backend systems becomes the job.
What was built
The pieces, and how they fit
All of it is configuration on a single instance.
One agent handling questions, registrations and event information conversationally
Functions for register, cancel and confirm, plus transport, ticketing and logistics reached through connectors with credentials held as secrets
A store with one entry per guest and registration, so the assistant and the organiser see the same truth across separate conversations
Templates rendered with the guest's details and sent from the instance
Schedules that send reminders before the event and follow-ups afterwards
A management interface reading the same data through named queries, rather than a second system to keep in sync
The result
The conversational experience became a registration channel in its own right. In its first year it carried 50 to 55% of registrations, with a slightly higher attendance rate than the standard web form.
AI agents
Python functions
State stores
Connectors
Secrets
Templates
Scheduled functions
Named queries
Get started