AI chatbot
Turn website visitors into real conversations.
HeyLeo answers questions from your approved content, guides visitors to the right offer, captures requests completely and hands over to your team when it matters.
- Answers from approved content
- Handover to your team
- Visible AI notice
Website assistant
AI assistant
Try a question:
Sample conversation on a fictitious website. Independent of HeyLeo on this site.
Who this service is for
For websites where the same questions are asked again and again, or where visitors do not immediately find the offering that suits them. A very small site with few questions often gets by with a good FAQ section.
What we deliver
- HeyLeo chatbot, integrated into your website and adapted in appearance
- Knowledge base built from content you have approved (website, FAQs, price lists, documents)
- Defined topics where visitors are referred to your team, and handover routes (form, callback, phone)
- Visible notice that an AI is answering
- Tests with typical customer questions before launch
- Evaluation of conversations after launch and adjustment of the knowledge base
Costs
- One-off
- No flat price. One-off costs cover building the knowledge base, integration, customisation and tests; the quote follows after the intro call.
- Ongoing
- Ongoing costs cover operation and licensing of the technology used, language and model usage depending on conversation volume and, if desired, maintenance and evaluation. Shown separately in the quote.
- Depends on
- Amount of content, Number of languages, Connection to form, appointment booking or CRM, Conversation volume, Scope of maintenance
What we need from you6
- Approval of the content the chatbot may answer from
- FAQs, price lists and documents, as far as it is to use them
- Decision on which topics it does not answer itself
- A contact person who receives enquiries, and a contact route for handover
- Access to the website; for integration with appointment booking or a CRM, also access to those systems
- Notification when prices, hours or services change
Requirements and limits5
- The chatbot does not replace personal advice on contracts, health or money.
- It only knows the knowledge base; outdated content leads to outdated answers.
- It is set up so that, when information is missing or uncertain, it does not guess but points to contact or a callback. Mistakes are still possible; that is why we test before launch and spot-check in operation.
- Whether it takes load off your team only becomes clear from the conversations after launch.
- Privacy notices must match the integration and the AI provider; the legal review lies with your data protection adviser.
The difference
Same website. Two visits.
On the left a visitor searches alone and leaves. On the right they get an answer and find the way to contact you.
Without chatbot
The visitor searches alone.
Questions after closing time go unanswered
Someone who wants to know at 9 pm whether you deliver, have appointments free or are the right contact rarely waits until tomorrow. Often they ask the next provider who answers faster instead.
The same questions, every single day
Opening hours, process, requirements: by email and phone, your team answers the same ten questions again and again. That costs time that is then missing for customer conversations.
Visitors can't find what they're looking for
With a larger offering, a menu is not always enough. Visitors who cannot immediately find their way leave the site without ever making an enquiry.
Enquiries arrive incomplete
“Please call me back” with no number, no reason, no time slot. Then the follow-up questions begin before the actual conversation has even started.
Visitor leaves the website
With chatbot
The visitor gets a conversation.
Hello! How can I help?
Do you also deliver to Austria?
Yes, according to our delivery information. Shall I pass your request about the terms on to the team?
Yes, please. Call back on 0123 456789.
Request to your team
- Request
- Delivery to Austria
- Contact
- Call back, 0123 456789
- Source
- Website chat
- Answer to the question
- Relevant page
- Contact or callback
Schematic illustration, not a real customer conversation.
Which questions do your visitors keep asking?
In the intro call we clarify which of them a chatbot can sensibly handle.
Where the answers come from
A chatbot only knows what you give it
A chatbot only knows what it is given. That is why most of the work goes into the knowledge base: we prepare your content with you, check the answers and keep them up to date when something changes.
Your content
Only what you approve for it.
- Website content
- FAQ
- Price lists
- Documents
Approved by you
Knowledge base
We prepare the content with you, check the answers and adjust them when something changes.
HeyLeo chatbot
Answers based on the knowledge base and should not guess when information is missing.
Answer for the visitor
With a pointer to the next step: page, form, callback or team.
How an answer can be traced back
ExampleHow long does delivery take?
Conversation scenarios
How a conversation can go
Four typical situations as examples. Choose a scenario.
Until when can I still cancel an appointment?
According to our notes, we ask for cancellation at least one day in advance. Shall I give you the contact details for that?
I have complaints and need information about my treatment.
I'm not able to give information on that. Your practice team will go through it with you personally. I can give you the phone number or take a callback request.
- 1Standard question answered
- 2Sensitive topic detected
- 3Handover to people
Typical use case
Fewer FAQ emails at the practice
A dental practice answers questions about procedure, directions and appointment booking automatically. Medical information deliberately stays with the staff.
We would like to outsource our bookkeeping.
Gladly. Two quick questions first: what legal form is it, and what's the best way to reach you?
Ltd., by email: anna@example.org
Request to your team
- Request
- Outsource bookkeeping
- Legal form
- Ltd.
- Contact
- anna@example.org
- Source
- Website chat
- 1Understand the request
- 2Ask follow-up questions
- 3Hand over in structured form
Typical use case
Advice on services
A tax firm lets visitors briefly describe what it is about and directs them to the right intro call. The firm receives the request right along with it.
I urgently need someone for my heating at night.
I'll gladly take that. Where is the system, and what exactly happened?
In Sampletown, it's no longer producing heat.
Request to your team
- Request
- Heating without heat
- Location
- Sampletown
- Urgency
- high
- Next step
- Callback from the team
- 1Take down the request
- 2Capture urgency
- 3Trigger callback
Typical use case
First contact in the trades
A heating engineer takes requests at night too: address, type of system, urgency. In the morning there is an enquiry waiting that can be worked with.
What are the dimensions of the garden table, and is it weatherproof?
According to the product description, 180 × 90 cm, teak, suitable for outdoors. Shall I show you an alternative with different dimensions?
Yes, a bit smaller please.
Then the 140 × 80 cm model fits better. I'll link the product page.
- 1Use product data
- 2Suggest an alternative
- 3Guide to the page
Typical use case
Product questions in an online shop
A garden furniture retailer explains dimensions, materials and delivery times via chat, instead of every question turning into an email. If the product does not fit, the bot shows the alternative.
Features
What HeyLeo can do
Features (depending on the agreed HeyLeo scope)
Answers to frequent questions
HeyLeo draws on content you have approved: services, processes, opening hours, terms. When information is missing or uncertain, it is meant not to guess but to point to contact or a callback.
Guiding through your offering
The chatbot asks one or two follow-up questions and points visitors to the page or service that fits their situation. This replaces searching with a short conversation.
Capturing enquiries completely
Name, contact method and request are collected during the conversation and passed on to you in a structured form. Your team no longer has to ask what was meant.
Handover to people
If the bot gets stuck or a request seems sensitive, it refers to your team, your contact form or your phone number. Handover is a fixed part of the planning.
Multiple languages
Depending on the scope set up, HeyLeo answers in the languages your visitors need. Which ones those are, we clarify in the intro call based on your actual target audience.
Integration into your website
A script is usually enough. We adapt the look, greeting and tone to your site so that the chatbot feels like part of it rather than a foreign window.
Integration
Integration and requirements
The website is at the center. What else gets connected, we clarify with you.
Content from your website
Foundation
FAQs, price lists and documents
Foundation
Contact form or email inbox
Foundation
Cookie and privacy settings
Foundation
CRM or appointment booking (by arrangement)
By arrangement
Which systems are actually connected depends on the project. Connections shown with dashed lines are optional and project-dependent.
Limits and control
Clear rules for when the chatbot answers and when a person does
Visitor asks a question
Handover to a person: Form, callback or phone, as you define it.
Privacy & AI notice
Data protection and AI notice
Visitors should recognise that they are writing with an AI and know what happens to their input. The following points are a guideline, not legal advice. The specific assessment is a matter for your data protection adviser.
- Clear notice that an AI is answering
- Answers based on approved content, tests before launch, spot checks in operation
- A human takes over for unclear or sensitive requests
- Privacy notices matching the integration and the provider of the AI technology
- Collect only the data needed for the request
Limits
- The chatbot does not replace personal advice on contracts, health or money.
- It only knows the knowledge base; outdated content leads to outdated answers.
- It is set up so that, when information is missing or uncertain, it does not guess but points to contact or a callback. Mistakes are still possible; that is why we test before launch and spot-check in operation.
- Whether it takes load off your team only becomes clear from the conversations after launch.
- Privacy notices must match the integration and the AI provider; the legal review lies with your data protection adviser.
Setup
From content analysis to a tested live chatbot
01
Clarify goals, target audience and typical questions
02
Build the knowledge base from your content
03
Define dialogues, tone and limits
04
Integrate into your website
05
Test with real questions
06
Evaluate and refine after launch
Ready for a chatbot that fits your website?
We clarify scope, content and handover paths in the intro call. The quote follows afterwards.
HeyLeo: the chatbot we use ourselves
HeyLeo is the AI chatbot we set up on customer websites. You can also try it out here with us: ask it a question about our services and see how it answers and when it hands over to us.
We discuss scope of functions and terms in the intro call.
Send an enquiry →Result
What you get out of it
Frequent questions are answered outside office hours too
Visitors find the right service faster
Enquiries reach you complete and structured
Your team has fewer standard questions on its desk
The conversations show which information is missing on your website
Actual results depend on the starting point, scope and implementation. We do not give guarantees of success.
Concept studies
Concept studies on AI chatbot
Detailed scenarios for typical starting points and possible approaches. They are not reports on client projects.
- Expert analysis · not a client project
Privacy and transparency · 14 min
What happens to what visitors type into your chat window?
Anyone who uses a chatbot on their website should know where every input goes, how long it is kept and how visitors can tell.
Read concept study → - Concept study · not a client project
Lead qualification · 14 min
When the callback only clarifies what the enquiry could have said
A chatbot can organise enquiries before handover if it asks like an attentive conversation partner rather than a form, and if the scoring merely supports sales.
Read concept study → - Scenario · not a client project
Multilingual support · 14 min
The customer writes in Dutch, your team does not
A multilingual chatbot in shop support only works if the knowledge base, glossary, legal texts and order data are deliberately handled separately for each language.
Read concept study → - Expert analysis · not a client project
Chatbot quality · 13 min
The bot sounded confident, and the answer was still made up
An AI chatbot is only ready for operation when it knows what it must not answer, and when tests, samples and a human fallback prove it.
Read concept study → - Scenario · not a client project
Appointment booking · 14 min
The 7:55 a.m. call that one chatbot can take and another cannot
An appointment bot works when it strictly follows calendar rules, asks as little as possible in the chat and hands over to people when in doubt.
Read concept study → - Expert analysis · not a client project
Knowledge base · 13 min
A chatbot only knows what you give it to read
The quality of an AI chatbot is decided less by the model than by the knowledge base: what is in it, how current it is and what the bot does when something is missing.
Read concept study →
FAQ
Frequently asked questions
Which questions can the chatbot answer?
Whatever is in the approved knowledge base: services, process, requirements, opening hours, frequent follow-up questions. For questions outside of that, it is set up to refer to your team or your contact form rather than guess. Mistakes are still possible, which is why we test in advance and spot-check in operation.
How is the chatbot supplied with information?
Together with you we collect website content, FAQs, price lists and documents, prepare them and store them as the knowledge base. We then test with typical customer questions whether the answers are correct. If anything changes on your side, such as prices or opening hours, the knowledge base is updated so that the bot does not spread outdated information.
What happens if the bot does not know an answer?
It is meant to say that it does not know, and gives your contact options or takes the request for a callback. You can also define topics that it always passes on, for example complaints, legal questions or medical information.
Can the chatbot hand conversations over to people?
Yes, handover is part of the planning. Depending on the setup, the bot refers to a form, collects contact details together with the request, or gives the right phone number. How quickly someone responds is up to you. Together with you we define what visitors are told outside business hours.
Is an AI chatbot on a website compatible with data protection?
In principle, yes, provided it is integrated properly. That means a clear notice that it is AI, appropriate privacy information, data minimization, and an integration that respects your cookie settings. This is a general guide and not legal advice. Your data protection adviser should carry out the binding review for your case. We supply the technical details for it.
How long does it take for the chatbot to go live?
That depends less on the technology than on the content. If your FAQ and service descriptions are ready, a first version can usually be tested much faster than when information is scattered. We give you a fixed schedule after the intro call, once we know the scope, languages and integrations.
How much does an AI chatbot for the website cost?
It depends on the scope: amount of content, languages, connection to a form, appointment booking or CRM, and maintenance. There is no flat price. There is a one-time setup cost, plus ongoing licence, language and model usage based on conversation volume, and possibly maintenance. We discuss features and terms in the intro call and then send you a concrete quote. One-time and ongoing costs are shown separately.
How does HeyLeo differ from a simple FAQ section or rule-based chatbot?
An FAQ section assumes visitors can find the right question themselves. A rule-based chatbot with fixed buttons fails on any phrasing that was not anticipated. HeyLeo understands free-form questions and draws on your content. For very small offerings with only a few questions, a well-made FAQ section can still be enough, and we will tell you so.
Keep reading
Related services
- Websites & web developmentWebsites for your business: visitors quickly understand what you offer and can get in touch right away.
- AI agentsRead emails and documents, prepare tasks and carry out approved steps.
- AI phone assistantAnswers calls, handles standard questions and passes the request on to you cleanly.
Make your website the first point of contact.
Tell us which questions your visitors ask. We'll show you what a chatbot can take over.