AI chat on the booking page
Instead of a form, an AI chat can guide visitors on your booking page to an inquiry — what it knows, what it never does, what it costs, and what happens when it is unavailable.
On a booking page with the AI chat design it is not a form but a conversation that leads to the inquiry: the visitor describes what they are planning (“wedding, 80 guests, vegetarian finger food”), the chat suggests products from your page and asks for whatever is still missing. At the end there is a summary the visitor can review, change and send themselves. The inquiry arrives in your inbox like any other — with the same line items and the visitor’s wish as the message.
The chat is an extra route to the same destination, not a second form: line items, prices, required questions and the quote draft on arrival stay exactly what your page already has.
Turning it on
- Open Settings → Booking pages and click Configure on the page you want.
- In section 01 Details you find the Design field. Choose AI chat there. Below it, the option says what the page will do: ‘Visitors tell the chat what they need — the AI puts the inquiry together.’
- Save. The page is a chat page from that moment — active or inactive as before, and embedded on your website just the same.
You do not need a switch per page: whether the chat may run at all is a single setting for the whole workspace (see What it costs below). To go back, simply set the design to Inquiry or Webshop again.
What the chat knows
The chat knows only this one page and whatever you explicitly share with the public:
- The products of this page — name and short text, so it can make matching suggestions.
- The rooms and the required questions of this page — it asks for exactly what your form asks for.
- Documents from the knowledge base shared as “Website (public)”. Only those it answers content questions from, such as schedule, directions or allergens. That sharing option is off by default and asks for confirmation with a warning when you switch it on — it applies to anyone who opens your booking page.
It sees no quotes, invoices, customer or contact data, no other events and no other booking pages. It does not know the Univents help articles either.
If it finds no shared document for a question, it says so instead of guessing.
What the chat does not do
- It does not quote amounts in the conversation. Numbers in the chat are blocked outright, so that a casual answer never turns into an agreed price. Univents calculates prices — the summary card shows them only if your page shows prices.
- It never sends anything itself. Whatever a visitor types (‘just send it’): nothing happens. Sending happens only via the Send request button.
- It makes no promises. Words such as ‘guaranteed’, ‘reserved’ or ‘confirmed’ are blocked, and it does not check whether a date is still free.
- It creates and changes nothing in your back office. It only reads and collects.
- It does not store the conversation. What the visitor wrote lives in their browser; all that reaches your inbox is the finished inquiry.
What it costs
Every answered message runs on the same AI credit as the back-office chat and the portals, and typically costs a few cents. Requests that are not answered — limits reached, channel off, model errors — cost nothing.
You steer this in Master data → Knowledge base, in the card AI assistant in the portals, in the Website chat section:
| Setting | Default | Effect |
|---|---|---|
| AI chat on booking pages | on | Turns the chat off for all your booking pages. It applies from the next visitor message. |
| Monthly limit website chat (€) | 10 € | Once reached, the chat pauses until the next month. |
| This month | — | Shows this month’s spend against the limit. |
On top of that there are two limits the visitor never sees: 30 messages per visitor session and day and 300 messages per page and day. They slow down a forwarded link and a page that is having a busy day.
And the same reserve as for the portals: if your AI credit drops below 5 €, the website chat pauses automatically. The chat for your team keeps running. After a top-up it resumes by itself.
When the chat cannot: the form takes over
If a visitor hits a limit, or the monthly limit is reached, or credit falls below the reserve, or the channel is off, or the model does not answer — the page switches to the inquiry form of the same page by itself, pre-filled with everything the chat has collected so far. The visitor reads a calm line such as ‘The assistant is unavailable right now. Your details are already in the form — please send it there.’ So they lose nothing and retype nothing.
The same switch happens when they tap Use the form instead themselves — for example because they would rather see everything at once.
If the session token expires after two hours, the visitor never notices: Univents starts the session again and keeps the history.
Privacy
Above the chat it says AI assistant and, if your page has one, a Privacy link that leads to the privacy address of your booking page. The conversation is not stored — for billing, Univents only counts that a message was asked, never what it said. To let the AI answer, the text of a message goes to the provider of the language model; that is the same basis as for the AI assistant in the portals. The summary always carries the consent (the same wording as the inquiry form); without the tick, Send request stays locked.
Frequently asked questions
Do we see what visitors asked? No. Only messages and costs are counted, never content. What you receive in the end is the submitted inquiry.
Can the chat send an inquiry when a visitor tells it to? No. Sending only happens via the button, and the visitor has to tick the consent. No one can slip an inquiry past you.
Can I stop the chat immediately? Yes. The switch AI chat on booking pages in the knowledge base applies from the next message. If you want out even sooner, set the Design of the affected page back — that applies on the next page load.
Does the design apply to embedded pages too? Yes. Chat and form behave the same embedded as on the page itself. For embedded pages, note the hint about captcha domains when embedding.
What happens to the details if a visitor gives up? Nothing. They stay in their browser until they leave the page. Without a click on Send request, no inquiry reaches you.