An AI chatbot for a visitor attraction answers the practical questions people ask before they set off, at any hour, from the information you already publish. Opening times, parking, access, dogs, buggies, what's included in a ticket and whether the light trail runs if it rains. These aren't glamorous questions, but they're the ones standing between someone and a booking.
We work with attractions including Eureka! The National Children's Museum, Castle Howard and Magna, and the pattern is the same across all three. A small number of practical questions make up most of the volume, they arrive at the worst possible times, and they multiply enormously the moment a seasonal event opens.
Key takeaways
- The questions are duller than anyone expects. Parking beats philosophy. So do dogs, buggies, toilets and whether the café is open.
- Your enquiries don't follow your opening hours. Families plan on Sunday evenings, and that's precisely when nobody's on the desk.
- Christmas breaks the usual approach. A festive event changes your times, prices, access and rules all at once, and every copied answer on your site goes stale on the same day.
- Seasonal accuracy matters more than seasonal volume. A wrong answer about a Santa slot costs you more than an unanswered one.
- Some conversations must reach a person quickly. Accessibility needs, safeguarding-adjacent questions and anything about a booking that's already gone wrong.
- International visitors are a bigger share than most attractions think, particularly at heritage sites, and they rarely ask in English.
What visitors actually ask
Ask a marketing team what people want to know and you'll hear about exhibitions and collections. Read a month of real enquiries and you'll find something far more practical.
- Getting there and parking. Where, how much, is it far, is there a drop-off, what about coaches.
- Opening times, especially on bank holidays, in school holidays and over the festive period.
- What's included in a ticket, and what costs extra once you're inside.
- Access. Step-free routes, wheelchair loan, quiet hours, changing places facilities, carer tickets.
- Dogs. Whether they're welcome, where, and whether that changes indoors or during events.
- Buggies and babies. Where to leave a pram, feeding facilities, whether under-twos need a ticket.
- Food. Whether the café is open, whether you can bring a picnic, whether there's anything for a coeliac child.
- Age suitability. Whether a five-year-old will enjoy it, whether a teenager will be bored, whether it's too dark or too loud.
- Weather. How much is indoors, whether the outdoor trail runs in the rain, whether tickets transfer.
- Groups and schools. Rates, ratios, risk assessments, lunch space, coach parking.
Almost all of it is already published somewhere on your site. The problem isn't that you haven't answered these questions, it's that the answer sits three clicks deep, or in a PDF, or in a paragraph halfway down a page nobody scrolls to.
Why attractions are different from other sectors
Plenty of businesses get repetitive questions. A few things make attractions genuinely harder.
A visit is a plan, not a purchase. Somebody booking a day out is coordinating grandparents, a car, a nap schedule and the weather. One unanswered question, such as whether there's somewhere to warm a bottle, is enough to make them choose somewhere else, and you never hear about it.
Your information changes constantly. Opening times shift with the season, events come and go, a gallery closes for maintenance, prices change in April. Any answer you write down starts going out of date immediately.
Most enquiries come from people who've never visited. They don't know your language. They'll ask about "the big shed" or "the steel place" or "the one with the dinosaurs", and a keyword search will fail them where a person wouldn't.
The stakes on practical detail are high. Get an access answer wrong and someone has a genuinely bad day. This is why the escalation route matters as much as the answering.
What happens at Christmas
Every attraction we work with describes the same shape. Enquiries climb from late October, peak hard through December, and consist of a narrow set of questions asked over and over by people who are anxious about getting it right.
Festive programming makes it worse in a specific way. A Christmas event usually changes several things at once:
- Different opening times, often later, and different again between the event and the daytime attraction.
- Different prices, and a different booking route, which sends people to the wrong page.
- A different route around the site, so your usual access information no longer describes what visitors will meet.
- New rules, about pushchairs on a light trail, dogs at an evening event, or whether under-twos need a ticket for a grotto.
- Time slots, which generate a whole category of question that doesn't exist the rest of the year: what happens if we're late, can we swap, how long before our slot should we arrive.
So the festive season doesn't just add volume, it invalidates a chunk of what your website says while adding a new set of questions nobody has written answers for. And it does this at the point in the year when your team has the least slack.
The organisations that cope best treat their assistant as part of the event build rather than something to sort out afterwards. When you write the event page, you write the twenty questions that come with it at the same time.
The questions that only appear in December
Worth writing down before the season starts, because they'll arrive whether you've prepared or not:
- Is the light trail on if it's raining, and do we get a refund if it's cancelled?
- Can we arrive early and look round the daytime attraction first?
- Does my toddler need a ticket for the grotto, and will they get a present?
- How long does the whole thing take, and is there a point of no return once we've started?
- Is there parking for an evening event, and will it be lit?
- Can we bring the dog on the trail?
- Are the toilets open along the route?
- What happens if we miss our slot?
None of those are difficult. They're just numerous, and they all arrive between six and nine in the evening.
Where an AI agent helps, and where it must not
Being honest about the boundary is what separates a tool visitors like from one they resent.
It handles well: opening times, prices, parking, access facts, what's included, age suitability, dogs, food, directions, group rates, and the whole evening and weekend when nobody's at the desk. It's also good at the same question asked a hundred different ways, which is where people get bored and inconsistent and software doesn't.
It should escalate immediately: anything where a visitor has a complex access need, anything safeguarding-adjacent, complaints about a visit that's already happened, and anything about a specific booking the system can't see. An automated apology for a ruined birthday makes things considerably worse.
The measure of a good setup isn't how much it deflects. It's whether the right things reach a person quickly, with enough context that the reply can answer rather than ask.
How Eureka!, Castle Howard and Magna use it
The three are quite different organisations, which is part of the point.
Eureka! The National Children's Museum in Halifax is built entirely around families with young children, so its enquiries skew heavily towards the practical logistics of a day out with a toddler. In its first month with Holp, the assistant answered 360 customer conversations.
Now Holp is part of our core customer service strategy – we couldn't imagine not having it.
Sophie Ballinger, Head of Communications & Customer Service, Eureka!
Castle Howard is a working historic house and estate in North Yorkshire with grounds, a farm shop and one of the more ambitious Christmas programmes in the country. Its enquiries change shape completely between summer garden visits and a fully themed festive house.
We really value Holp — it's been answering questions left, right and centre since the day we launched, and we couldn't be happier.
Georgie Sykes, Marketing & PR Manager, Castle Howard
Magna, run by the charity Magna Trust, sits in the former Templeborough steelworks in Rotherham and has been telling the story of steel through hands-on science since 2001. As a charity operating a very large indoor site alongside an events and venue-hire business, it fields a mix of family day-out questions and enquiries that have nothing to do with visiting at all.
What the three have in common is that none of them added headcount to cope. The assistant absorbed the repetitive layer so the team could spend its time on the enquiries that genuinely needed a person.
Keeping seasonal information from going stale
This is the part that matters most for attractions, and it's where a lot of chatbot projects come unstuck.
If you copy your opening times into a knowledge base, you now maintain them in two places, and the copy will be wrong within weeks. For anything that changes often, live website search is the better answer. Your assistant reads the actual page on your website at the moment someone asks, and answers from what it finds right then, so there's no second copy to keep up to date.
That suits exactly the things attractions struggle with: what's on, seasonal times, event availability, ticket prices and anything with a date attached. Write down the things that don't change, which is your access information, your dog policy, your parking, and let live search handle the rest.
One caveat worth knowing. The pages have to be publicly reachable, so anything behind a login, a form or a cookie wall can't be read.
International visitors
Heritage sites in particular see a much larger share of overseas visitors than their enquiry inbox suggests, mostly because people who can't ask in English tend not to ask at all.
Holp answers in over 50 languages and always replies in the one the visitor wrote in, from a single knowledge base and with no translated website to maintain. You write your access information once, in English, and a family from Madrid planning a half-term trip gets it in Spanish. There's more on how that works in the multilingual guide.
Beyond your website
Not every question happens before the visit, and this is where attractions have an advantage over most businesses, because they have physical space to work with.
QR codes put your assistant on a poster at the car park barrier, on a sign at the start of a trail, on a table talker in the café or on the back of a ticket. Someone standing in the cold wondering how much further it is to the next installation can get an answer without finding a member of staff. Each code tracks its own scans, so you learn which placements are actually used, and a code can be scoped to a particular part of your knowledge so a trail sign answers trail questions.
A public link does the same job in an email signature, a booking confirmation or an Instagram bio, which is often where the pre-visit questions start.
What to measure
Most dashboards offer a dozen numbers and about three of them matter here.
- Knowledge gaps. The questions your assistant couldn't answer, which is the most actionable list you'll get. During a seasonal event, read it weekly.
- Conversation volume against the same period last year, which tells you whether people are finding it rather than whether it's working.
- Escalation by topic. Rising escalation on one subject is a precise signal that your knowledge on that subject is thin.
Don't chase a deflection rate. A high one achieved by hiding the route to a human is a worse outcome than a low one, and in a sector where access questions arrive daily it's actively risky.
The knowledge gaps guide and the Insights dashboard cover the mechanics.
Getting ready before the season starts
If you're reading this in autumn and wondering whether it's too late, it isn't, but the order matters.
- Collect the real questions, from your inbox, your phone notes and whoever staffs reception. Aim for thirty and expect ten to cover most of the volume.
- Write the answers that don't change, meaning access, parking, dogs, facilities and anything about the site itself.
- Point live search at the pages that do change, which is your what's on, your times and your ticket pages.
- Write the event questions when you write the event page, not in December.
- Decide what happens when it can't help, including who gets notified and how fast someone replies. A widget that collects enquiries nobody reads is worse than no widget.
- Test it as a visitor would, in visitor language, including three awkward ones: something you have to say no to, something from a frustrated parent, and something it can't possibly know.
The software takes an afternoon. The content is the variable, and it's the bit that decides whether this works.
Frequently asked questions
Will it replace our front-of-house team?
No, and it shouldn't. It handles the repetitive practical questions that arrive out of hours and in volume, which frees your team for the conversations that need a person. Nothing about a complex access requirement or an upset visitor belongs with software.
How does it cope when our opening times change?
Point it at your live pages rather than copying the times in. It reads the current page when someone asks, so there's no second copy to update and nothing to go stale when the festive timetable starts.
What if it gets something wrong about accessibility?
This is the right thing to worry about. Write your access information yourself rather than letting it be inferred, keep it specific, and make the route to a human obvious on every access-related answer. An assistant that says it isn't certain and offers a person is working correctly.
Can it handle our Christmas event and our normal admission at the same time?
Yes, provided you've written both down clearly and said which is which. The most common failure is having festive and daytime information on the site without ever stating plainly that they're different things, at which point both people and software get them muddled.
Do we need a developer?
Only to paste one line into your website, and most content management systems have a field designed for it. Everything else, including the knowledge, the branding and the tone, is managed in the product.
How long does it take to set up?
The software is an afternoon. Expect a week or two of writing if you're starting from nothing, and less if your website already answers most of it. Plan for weekly reading of the conversations for the first month.
What about visitors who don't speak English?
They're answered in whatever language they wrote in, across more than 50 languages, from the same knowledge base you wrote in English.
Where to go next
If you're weighing up whether this suits your site, what is customer chat support covers the wider ground, including the difference between live chat, rule-based bots and AI agents. If you'd rather get started, the setup guide walks through it end to end, and pricing starts at £25 a month with a 30-day trial, and nothing charged until it ends.
Or talk to us if you'd like to work through what your busiest month actually looks like.
