Answer the visit questions, not the ticket
Opening and last admission, prices and concessions as published, parking, access routes and what is on — from your own pages. Availability itself always goes to your booking page.
Opening and last-admission times, bank-holiday changes, prices and concessions as published, coach and blue-badge parking, step-free routes, what is on in the temporary gallery. Every one already sits on a visitor page, and the chat window on your site reads it back — at whatever hour it is asked, in whatever language. What it will never do is tell somebody a ticket or a timed slot is available: it has no sight of your ticketing system, so that question goes to your own booking page.
Fig. 01.A · Local attractions / museums
Fig. 02.A · pain quotesVisitors plan on their phone, often from the car park: are you open on the bank holiday, when is last admission, is there room for the coach, is there a lift to the upper galleries, is the touring exhibition still up. Meanwhile a teacher's enquiry lands with no year group and no date, so the learning team's first reply has to ask for the basics instead of answering them. A small desk cannot hold that queue and the phone at the same time.
Opening and last admission, prices and concessions as published, parking, access routes and what is on — from your own pages. Availability itself always goes to your booking page.
Party size, year group, date and led-or-self-led, written down in the teacher's own words, so your learning team can answer once instead of asking for the basics.
An access question about one visitor's needs goes to your duty manager. Anything suggesting somebody is in difficulty gets no reply and reaches the person you named.
Opening and last-admission times and bank-holiday changes, prices and concessions as listed, coach and blue-badge parking, step-free routes and assistance dogs, how long to allow, what is on in the temporary gallery and how school visits work — all answered from your own visitor pages, with availability sent to your booking page and access specifics to your duty manager.
A school or group enquiry is unanswerable without the year group, the party size, the date they want and whether they are after a led session or a self-led visit. Adoomi asks for the fields your team sets, and writes the numbers and dates down exactly as the teacher or coach organiser gave them — nothing rounded, nothing confirmed. The enquiry then reaches your education or groups manager as an email alert to the address you set, or on WhatsApp carrying the teacher's own message.
With Adoomi
Fig. 06.A · after-hoursAttraction enquiries follow the weather and the school calendar rather than office hours: a family checking last admission on a wet Saturday morning, a coach organiser working out where to set down, a teacher writing the trip letter after the children have gone home. Adoomi works from your visitor pages right through, 24/7, noting what they leave open for the morning. The one thing it still will not do at midnight is say the timed slots are open — that stays with your booking page.
Opening and last-admission times, prices and concessions as listed, whether the car park takes coaches and where blue badges go, which galleries have step-free routes, whether dogs and pushchairs are welcome, how long a visit usually takes, what is on in the temporary space and when it comes down. It is on your site the day the season opens. Adoomi answers from those pages, so the desk spends the weekend on the people standing in front of it.
Fig. 08.A · controlsThe assistant answers what your visitor pages publish — opening and last admission, prices as listed, parking, what is on, access. It has no link to your ticketing system, so it never says a slot is free or a day is sold out; it points at your booking page and cannot book, hold or refund. Access questions about one visitor's needs go to your duty manager, giving to your donation page, and anything suggesting somebody is in difficulty to the person you named, unanswered.
Opening times, prices and concessions as listed, parking and what is on. If a page does not say, it says it does not know instead of inventing an answer.
There is no link to your ticketing system, so availability is never stated, guessed or implied. Visitors go to your own booking page, and nothing is booked, held or refunded.
Whatever access duties you have are unchanged by this. The assistant repeats your published access statement and no more; one visitor's particular needs reach your duty manager before they travel.
Conversations are EU-hosted with GDPR export and deletion on request, no conversation content is written to logs, and the chat window sets no tracking cookies.
Availability is never confirmed by the assistant. It has no connection to your ticketing system, so it cannot see a timed slot, a sold-out day or a walk-up allowance. It repeats what your booking page publishes and sends the visitor there, and it cannot book, hold, amend or refund a ticket.
School and group enquiries are captured, never confirmed. The assistant explains what your learning pages publish about session types, adult-to-pupil ratios and lunch space, then records the year group, party size and preferred date in the teacher's own words for your education manager.
Access answers come from your own access statement and go no further than it: step-free routes, lifts, assistance dogs, quiet sessions, whatever you have published. A question about one visitor's particular needs is not judged in chat — it reaches your duty manager, because that promise belongs to the building.
Giving and complaints both leave the chat window: a donor is sent to your own giving page rather than paying in chat, and press or complaint enquiries go to your director. Distress is different again — no reply at all, and the conversation reaches the safeguarding lead you named, with their words attached.
Costs start at £0 a month on the Free plan, which includes 50 message credits. Above it sit 200 credits for £8, 500 for £20 and 4,000 for £75. One credit covers one answer from the assistant, and nothing is spent when your own desk writes the reply. Connecting, checking and publishing runs to ~10 min.
Chat data is held on EU-hosted infrastructure, exportable and deletable on request under GDPR, and no conversation content is written to logs. No tracking cookies are set, and nothing is left on a visitor's device once they close the tab. School enquiry details are only the fields you asked for.
Nothing on this page is a measured result. What is described is construction: the assistant draws on your visitor pages and nothing else, it declines the availability question every single time rather than most times, and an access enquiry about one person leaves for your duty manager whether or not the desk is watching. Those hold at half term as reliably as on a wet Tuesday, because they are properties of the rules rather than of anyone's attention.
Opening and last admission, prices and concessions as listed, parking and what is on — answered while the galleries are shut and the desk is unstaffed.
No connection to your ticketing system exists, so the availability question goes to your booking page every time rather than most times.
50 message credits to try it against your own visitor pages, with 200 for £8, 500 for £20 and 4,000 for £75 above it. Setup runs to ~10 min.
Give Adoomi the pages a visitor actually reads — opening and last admission, prices and concessions, parking and coach access, your access statement, what is on, and your school and group information. Then check every answer it proposes yourself. Booking stays on your own ticketing page, access specifics go to your duty manager, and the Free plan is £0 with 50 message credits and no card: enough to put the awkward question to it.
Fig. 12.A · Local attractions / museums