Keeping Your AI Assistant on Script: Why a Secure Knowledge Base Matters
Keeping Your AI Assistant on Script: Why a Secure Knowledge Base Matters
An AI assistant is only as good as what it knows. It should only ever say what your park would say.
When I talk to park owners about AI, one question comes up more than any other: "What stops it making things up?"
It's the right question to ask. In eleven years of selling holiday homes, I learnt that getting a price or a policy wrong costs you more than one sale. It costs you trust, and trust is hard to win back. A guest quoted the wrong price for a lodge, or told dogs are welcome when they aren't, doesn't blame the software. They blame the park.
That's why ParkPilot is built so that the AI assistant answers from a secure knowledge base that your park controls, and why keeping that knowledge base up to date is something your own team can do in minutes.
The Problem with General-Purpose Chatbots
Most AI tools people have used are general-purpose. They've learnt from huge amounts of text from across the internet, and they're designed to give an answer to almost anything.
That's useful for writing an email. It's a risk on a holiday park website.
A general-purpose chatbot asked about your pitch fees might give a figure that sounds about right for a park in your area. Asked about your pet policy, it might describe what's typical rather than what's true for you. Asked about an offer that ended last month, it has no way of knowing it ended.
None of these answers are malicious. They're guesses. And a confident guess presented to a prospective owner as fact is exactly what a park can't afford.
A Secure Knowledge Base Your Park Controls
ParkPilot takes a different approach. The assistant is contained to a knowledge base built for your park and managed by your team. That's where its answers come from:
- Holiday home prices, pitch fees and what's included
- Touring and holiday hire rates, including seasonal pricing
- Park policies: pets, arrival and departure times, quiet hours, vehicles
- Facilities and opening times: pool, clubhouse, shop, restaurant
- Current offers and events
- Owner information: services, the season, who to contact for what
The assistant doesn't go looking for answers on the wider internet, and it isn't filling gaps with what other parks do. It answers from what you've told it.
When a question falls outside that knowledge, the assistant shouldn't guess. You decide which questions go to your team, using the escalation rules your park sets, so a person picks up anything the knowledge base doesn't cover.
Update Prices and Information on the Fly
A knowledge base is only useful if it's current. Holiday parks change all the time: new holiday homes arrive, prices are reviewed, offers start and finish, the pool closes for maintenance, opening times change for winter.
With ParkPilot, your team manages all of this from the admin panel. Make a change, and the assistant's answers update instantly. There's no need to raise a support ticket, wait for a developer or retrain anything.
A few examples of how that looks day to day:
- A lodge price changes on Friday afternoon. Your sales manager updates it in the admin panel, and the enquiry that arrives at 8pm that evening gets the new price.
- You open a new development. Add the details, prices and available plots once, and the assistant can talk about them straight away.
- The shoulder season starts. Change the touring pitch rates and opening times, and every answer reflects the new season from that moment.
- An offer ends. Remove it, and the assistant stops mentioning it. No more prospective owners asking for a deal that finished weeks ago.
The people who know your park best stay in charge of what the assistant says about it.
Why This Matters for Holiday Parks
Accuracy builds trust
Guests and prospective owners make decisions based on what they're told. An answer that is fast and right builds confidence in the park before anyone has visited. An answer that's fast but wrong does the opposite.
Your team stays in control
AI should give your team time back without taking control away from you. A contained knowledge base means you decide what the assistant knows and says, and every conversation is logged so you can see exactly what was asked and how it was answered.
Fewer awkward corrections
Every wrong answer creates work: a phone call to put it right, an apology, sometimes a disappointed guest. Keeping the assistant to approved information prevents most of those conversations happening at all.
It fits how parks actually work
Prices and policies on a holiday park aren't fixed for the year. Being able to change them yourself, and see the change straight away, is what makes an AI assistant practical rather than a project that needs constant support.
Questions to Ask Any AI Provider
Whether or not you choose ParkPilot, these are worth asking any provider before you put an AI assistant in front of your guests:
- Where do the assistant's answers come from? Your information only, or anything it has learnt elsewhere?
- Who can update that information, and how quickly do changes take effect?
- What happens when the assistant doesn't know the answer?
- Can you see every conversation it has had?
- Who signs off anything involving money? With ParkPilot, financial transactions always need human approval.
If the answers aren't clear, that tells you something.
See It for Yourself
The best way to understand it is to try it. Our demo park, Havenwood Lodge Park, is a fictional park built to show the ParkPilot AI assistant in action. Ask it about prices, pets or facilities at demo.parkpilot.uk, and you'll see it answering from the park's own information.
Want to see how it would work with your park's information? Book a 30-minute demo and we'll show you the admin panel and how quickly changes go live.