AI ASSISTANT
What can AI do for your event?
Extend early-bird by three days and tell everyone who has not booked yet.
- Early-bird ends12 May15 May
- Ticket tierLate rate, opens 16 May
- Announcement email1,284 recipients
Which channel converts best?
The embedded widget — 32% of registrations from 19% of the traffic.
Key features
Ask your event anything
Tickets sold, revenue, check-in pace, campaign open rates, survey results, best-converting channel — the copilot answers from your live event data through the same permissioned APIs your team uses. Ask how to do something and it answers with the steps and a direct link to the right console page — and since it knows which page you are looking at, the answer starts with what you can do right there instead of sending you off to navigate. A Live panel in the same drawer refreshes about once a minute: check-in rate, pace over the last 10 and 30 minutes, throughput by gate, and alerts when a gate surges, stalls, goes quiet, or is nearly done. Those figures are computed from your logs; the assistant explains them, it does not invent a second count. It never invents a number, and it only sees what your role allows.
Build events from a description, a link, or a screenshot
One input box: describe the event, paste the address of last year's site right in the text, or paste (Ctrl+V) a screenshot of a schedule, price table, or form — combine them freely. The assistant drafts the event, ticket tiers, agenda sessions, and registration form fields. When the page carries more — ticket prices, a schedule, registration fields, banner images — everything it found arrives as a tick-list, and only what you tick is imported; a banner image is never taken automatically, only when you pick it yourself. And when a description is too thin to draft from, the assistant asks you one short question instead of inventing details. Everything lands as an editable draft for you to review before anything is created.
Know what to do this week
Ask "are we on track?" and the copilot lays your preparation against a dated plan: tickets, publish, agenda, speakers, email campaigns, check-in prep, and the post-event survey, each milestone dated from your event dates. Done and overdue are computed from your live event data — never guessed — overdue items come first, and every pending item names the console page to fix it on.
Draft a sales organisation from a roster
Paste a name list, a spreadsheet, or a screenshot of an org chart. The assistant drafts the team paths and people as a proposal you review before anything is created. Addresses written in the text are not fetched.
Generate the event website
Give the assistant an existing event page's link or screenshot and it drafts your site: section structure, rewritten copy, and the source's brand colors and light-or-dark feel. The result opens in the website editor as an unsaved draft — refine it, then save it as a reusable template.
Translate the event into another language
Add a language version and the assistant drafts the first translation: the event text, ticket names, form labels, the website, and speakers, sessions, sponsors and exhibitors. It leaves anything a person has already translated alone unless you ask, nothing is published until someone has read it, and a broadcast can go out in each of the event's languages the same way. On the event title, summary and details it can also improve, translate or shorten copy already on the page; HTML is sanitised.
Every change needs your confirmation
When you ask the copilot to change something, it shows a proposal card describing exactly what will happen. Nothing executes until you click Confirm, and the change runs under your own account and permissions. Those cards can create a ticket, change its price, quantity or sales window, and publish or unpublish the event. Changes to forms, refunds, or sending mail are not in that flow yet — the assistant says so and points you to the console page.
Attendee Q&A on your event page
An optional chat widget answers attendee questions about the schedule, speakers, tickets, and venue — strictly from your published event information, including your website's FAQ. It works out times in the event's own time zone and knows whether registration is open. It is off by default, switched on per event from the assistant panel, and rate-limited against abuse.
Plan the on-site operation
Answer a short form — expected arrivals, check-in sites, badge printing — and get a full run sheet: lanes, staffing, devices, power and network per site, a volunteer training plan with scripts, and contingency playbooks. Every number comes from checkable rules drawn from large-conference operations; estimates are flagged for you to confirm. Download it and brief your team.
How it works
- 1
Type, paste a link, or paste a screenshot
One box takes it all: a sentence describing your event, the URL of a page you want to migrate pasted right in the text, and a screenshot pasted with Ctrl+V — in any combination.
- 2
Review the draft
The assistant fills in the event, tickets, agenda, form fields, and website. Anything else it found on the page — including banner images — waits in a tick-list and is only imported when you tick it. Everything is a draft — edit any field before creating.
- 3
Ask, act, confirm
Once live, ask the copilot about sales and check-ins — including the Live panel at the door — or tell it what to change. Every change arrives as a proposal card you confirm or cancel.
Frequently asked questions
No. The assistant can only propose changes. Each one appears as a card describing exactly what will happen, and nothing executes until you click Confirm. The change then runs under your own account, so it can never do anything your role could not do manually. Today those cards cover creating a ticket, changing its price, quantity or sales window, and publishing or unpublishing the event. Forms, refunds and sending mail still happen in the console.
From your live event data, fetched through the same permissioned APIs the dashboard uses. Answers are grounded in real numbers, respect your team-member permissions, and keep masked attendee contact details masked. Check-in pace and door alerts are computed from your logs, then explained — the assistant does not invent a second count.
Yes. Give it a description, the URL of an existing event page, or a screenshot of one, and it drafts the site structure, copy, and color scheme in the website editor. It borrows structure and brand colors — never images or logos — and you can undo, edit, and save the result as a template for future events.
Only what you have published: schedule, speakers, ticket prices, venue details and your website's FAQ. It cannot see orders or personal data, politely declines off-topic questions, and points order or refund queries to the attendee's confirmation email. It is off by default and enabled per event.
No. Requests are processed by leading AI providers under enterprise API terms that exclude training on your data. Attendee personal data stays inside your event platform — the public widget only ever sees published information.
The AI never invents them. Lane counts, staffing, devices, power, and network sizes are computed by fixed rules distilled from real large-conference operations, and every number traces back to a rule you can check. Anything based on a thin evidence base is marked as an estimate and listed in a "Confirm before event" checklist at the end — you verify those before briefing your team.
It works on daily AI credits included with the organisation's plan — no separate AI subscription or per-seat fee. One credit covers one AI request: a chat turn, a draft, or a site generation. A trial organisation gets 10 credits a day; Pro includes 50 per organisation per day and Business 200. The balance resets daily and your remaining count shows right in the assistant.
It asks instead of inventing. A description too thin to draft from gets one short follow-up question — the topic, the date — and the draft comes after you answer. The same restraint runs through everything: a source page without ticket information produces no ticket tiers, and a session whose end time is not stated is never given a made-up one.
Yes. Ask what to do this week and the copilot reconciles a standard preparation plan with your real event: ticket types, publish state, agenda, speakers, campaigns, check-in points and the post-event survey, each milestone dated from your event dates. Done and overdue are computed from the live data rather than guessed, overdue items come first, and each pending item points to the console page where you fix it.
Yes. When you add a language version, it drafts the first translation of the event text, tickets, form, website, speakers, sessions, sponsors and exhibitors. What a person has already translated is left alone unless you ask, and nothing is published until someone has read it. Each translation request uses AI credits like any other.
The language your console is set to: English, Simplified Chinese or Traditional Chinese. Event pages and attendee messages follow the event's own language instead.
Yes. Paste a name list, a spreadsheet, or a screenshot of an org chart. It drafts the team paths and people for you to review. Addresses in the text are not fetched, and nothing is created until you confirm.
Field guides
- How do you measure what each sales invitation and channel is worth?Measure event invitation and channel value with a worked cost comparison, qualification rules, attribution boundaries and practical budget decisions.
- How do you run a conference in more than one language?One event, several languages: shared inventory, what to translate, emails, hreflang, and where a model actually saves time.
0% platform fee on every plan — from $99 a month billed annually, with a 14-day free trial, no credit card, fair use on paid tickets (50 registrations / $500).
See pricingReady to run your next event?
Get started in minutes — or try the live demo to see what your attendees get.
- No credit card required
- DPA on request
- Multi-currency