One sentence instead of a brief.
Tell your assistant what you’re planning: occasion, date, guests, wishes. It asks about brand voice and audience if the brief is still missing.
AI event management software turns a plain-language description of your event into a draft registration page and form that your team reviews. Nothing goes out to attendees until a person approves it.
With AirLST you bring your own AI assistant, such as Claude, ChatGPT or Copilot, and connect it to your event account. In Airstage it builds landing pages and registration forms; other modules follow.
| Item | Status |
|---|---|
| Registration page | Draft |
| Form | Draft |
| Design | Draft |
| Thank-you page | Draft |
Four stages, one rule: AI sets things up, your team decides. Everything after that runs in the regular platform, with your guest list, invitations and check-in.
Tell your assistant what you’re planning: occasion, date, guests, wishes. It asks about brand voice and audience if the brief is still missing.
The assistant creates the building blocks in AirLST, in your branding. The form is built from the event’s guest fields.
The draft sits in your account, and you watch it live in the builder. You review, edit and approve; every action shows up in the history.
Invitations, registrations, RSVPs, tickets and check-in run in AirLST like any other event, on the same guest list.
AirLST is MCP-ready: you connect your AI assistant to your event account, and it works in AirLST with your permissions. AirLST provides the tools and the controls; the language model comes from your provider. How to connect and what the assistant can do is on the AirLST MCP server page.
Airstage, the builder for landing pages and registration forms, is connected. The other Suite modules follow one by one.
| Module | Scope | Status |
|---|---|---|
| Airstage (landing pages and registration forms) | All tools above | Available |
| Other Suite modules | Rolling out module by module | Rollout |
The home page tour shows an event assistant built right into AirLST. It’s a separate project and not available yet; we’ll share a date once it’s set.
In AirLST, AI works inside the permissions, logs and approvals that already apply to your team. Answers for IT are on the MCP server page, documentation in the Trust Center.
An AI connection belongs to one user and inherits that user’s roles and permissions. If that user can’t do something, neither can the assistant.
Every action the assistant takes is logged and shows up in the history; each one can be undone.
The assistant doesn’t send emails or export data. Publishing happens when you tell it to.
Guest and event data stay with AirLST on servers in Germany, GDPR-compliant.
You decide which language model works with AirLST; what it processes itself is governed by your contract with its provider.
You disconnect in your assistant. Without it, AirLST works exactly as before.
AI pays off most where teams run many similar events and each one still needs its own pages, forms and invitations.
Many similar dates in changing locations: one draft per stop instead of copying and editing.
Automotive eventsRecurring formats with their own registration per date, set up quickly and consistently.
Training managementMany departments, one standard: drafts in your corporate design, approval by your own team.
Corporate eventsSeveral clients at once: the groundwork is done fast, so the time goes into the idea.
Event agenciesIn a demo we show you on a sample event how an assistant works with AirLST through MCP: with your permissions, with a log, and with approval by your team.