A chatbot integration connects three things: a source of answers (your pages and documents), a place for the chat to appear (your website), and a route to a person when the bot cannot help (an email, a phone alert or your CRM, the system that holds your customer records). The chat window is the easy part. The connections around it decide whether the chatbot helps or annoys visitors.
This guide covers what each connection involves, how to cost it with your own numbers, and how to decide whether to do it at all. For one product in use on a real site, see how an AI chat assistant works on a business website.
Do you need a chatbot at all?
Not always. A chatbot draws its answers from what your pages already say and gives them faster than a visitor can find them, though it can still get one wrong. If the answers are not written down, or nobody will read the chats and reply to handovers, a contact form that states a reply time does the job with less to maintain.

What does a chatbot integration service actually do?
It wires the assistant to the places answers come from and the places enquiries go to. In practice that is five jobs:
- Source of answers. The assistant reads your pages and any documents you give it, and answers from them. Its answers are only as good as that material. Limits differ by tool: SiteBrain, our own assistant, reads up to 25 pages of your site, refreshed weekly, plus up to 20 extra documents such as PDFs (sitebrain.app, 4 November 2026). Other products set different limits, so ask for theirs.
- Placement. For a self-install widget this is usually a line of code pasted into the site. On a platform it may be a plugin. Anything custom needs a developer and a written scope.
- Handover. What happens when the bot does not know, covered below.
- Records. Where a captured enquiry goes: an email alert, a calendar entry, a CRM record.
- Upkeep. Someone reads the conversation logs and corrects wrong answers. The logs also show the questions your website does not answer yet.

What should happen when it does not know?
It should say so and offer a person. An assistant that guesses about your prices, delivery times or policies creates a problem you then have to apologise for. When the pages do not cover a question, SiteBrain says so and offers to pass it to the owner, and the owner can reply to the visitor from Telegram (sitebrain.app, 4 November 2026). Whichever tool you use, decide these four things before launch:
- What skips the bot. Complaints, refunds and anything where money has gone wrong go straight to a person.
- What the visitor is asked for. An email address or a phone number, and it is their choice to give it.
- Who gets the alert, and how. Email, a phone message, or inside the tool you already use.
- Who replies, and by when. Do not promise a reply time you cannot keep.

Email, CRM and booking: three levels of connection
Ask a vendor which of your tools it connects to by name, and which level each connection sits at.
| Level | What it means | Where it falls over |
|---|---|---|
| Built in | The vendor lists your tool and you switch it on | Only the fields the vendor chose to pass across |
| Automation or webhook | A message is sent to a connecting service that passes it on | One more service to pay for and keep working |
| Custom | A developer writes the connection to your system | Quoted per project, so the scope needs to be in writing |
Built-in connections may avoid development work; compare subscription and usage charges as well. Custom work is where quotes differ most, so compare quotes on what is connected and how, not on the headline price.
What about GDPR and privacy?
This is a factual outline, not legal advice, and no setup is compliant just because of the vendor's logo. A chat can contain personal data: a name, an email, a phone number, or details someone volunteers. The usual points to settle:
- Tell visitors what they are talking to and what happens to the chat. Article 13 of the GDPR requires you to tell people how you use their data when you collect it, so your privacy notice should cover the chat.
- A contract with the vendor. If the vendor handles chats on your behalf, Article 28 requires a written data processing agreement. Ask for it.
- Where chats are stored, and for how long. Ask the vendor, and put the answer in your privacy notice.
- A way to delete a chat on request.
- Ask for as little as you need. A chatbot that asks for details it has no use for creates a duty with no benefit.
The Irish Data Protection Commission publishes guidance. If chats will carry anything sensitive, take advice before launch.
What does it cost? Work it out with your own numbers
We do not quote an average saving. Any figure you read online was measured on a business that is not yours. The worksheet below is a formula you fill in.

The monthly subscription is the only figure you can look up today. Real examples at the self-install end, from sitebrain.app/pricing (4 November 2026): the Starter plan is €9 a month or €90 a year for one chatbot and 150 conversations a month, Pro is €39 a month or €390 a year for five chatbots and 2,000 conversations, and Agency is €99 a month or €990 a year for ten chatbots and 7,500 conversations. There is a 14-day trial, and a card is required to start it (sitebrain.app/pricing, 4 November 2026).
Conversation limits belong on your checklist for any vendor. SiteBrain emails you at 80% and 100% of the monthly allowance, keeps answering up to 120%, and after that asks visitors to leave a question and contact details instead (sitebrain.app/pricing, 4 November 2026). Ask every vendor what happens at the limit.
For a done-for-you install, our €600 AI Opportunity Audit comes first. Fixes start at €499 each, and the full €600 is credited against any recommended fix you book within 30 days (webs.ie/ai-consulting, 4 November 2026). Custom builds with booking, stock or CRM connections are quoted per project. Your own time reading chats and fixing answers, is yours to measure: read the logs weekly for the first month, time it, and use that.
Widget, platform or custom build?
| Option | Good for | Where it falls over |
|---|---|---|
| Self-install widget | A small site whose answers are already on its pages | Few connections to your other systems |
| Chat built into a platform you already use | Teams already running a helpdesk, CRM or shop platform | Tied to that platform's pricing and limits |
| Custom build | Specific connections such as booking, stock or a CRM | Needs a written scope; you own the upkeep |
We illustrate costs with our own product, not a market comparison, so we name no other vendor. Check each vendor's own pricing page on the day you decide.
Test it before you commit
Whatever you pick, try these on the real thing, on a phone:
- Ask something your pages do not answer. It should say so, not guess.
- Ask for a price your site does not state.
- Write a complaint. It should reach a person.
- Ask in a second language you serve, and have someone who reads it check the answer.
- Try to reach a human, and time how long the alert takes to arrive.
Frequently asked questions
What does a chatbot integration service include?
Connecting the assistant to its answer sources (your pages and documents), placing it on your site, setting the handover rules, linking enquiries to email, a calendar or a CRM, and setting up how conversations are reviewed. Ask for each as a separate line in the quote.
How long does it take?
It depends on what is being connected. A self-install widget can be live quickly, because it is mostly pasting a line of code. Every connection to another system depends on that system. Preparing and correcting the answers is the slow part, and it continues after launch. Ask for a written scope with the connections listed.
Can a chatbot replace staff?
It answers repeat questions. It does not handle complaints, refunds outside policy or anything that needs judgement, and it should hand those to a person. Plan for it as a first reply, not a replacement.
Is a chatbot GDPR compliant?
That depends on your setup, not on the product. See the privacy section above for the points to settle, and take advice where chats may hold sensitive details.
What if it gives a wrong answer?
It can give wrong answers even when your pages are accurate. Read the logs, fix the page the answer came from if it was unclear or out of date, and add the missing answer. The logs also list the questions your website should already have answered.
Where to start
Write down the ten questions your customers ask most, run the worksheet with your own figures, and try one assistant on a real site before you buy. You can try SiteBrain with its 14-day trial at sitebrain.app. If most of your enquiries arrive by phone, read our guide to AI receptionists.
About webs.ie: a Dublin web studio that builds AI-assisted websites and makes SiteBrain. We describe how we build sites in AI-assisted web design in Ireland. Contact: Dublin, Ireland | hello@webs.ie About the numbers: every price here comes from the vendor's own page, with the date we read it, or is a formula you fill in. An earlier version of this page carried savings and conversion claims that we could not source. We removed them.