Web/Guru

AI chatbots

AI chatbot development for your website, store and team

We build custom AI chatbots that answer from your own content and data: website support bots, Shopify store assistants, internal knowledge bots for staff, and chat on WhatsApp, Slack or Teams. Answers cite their sources, the bot says when it doesn't know, and a person can take over the conversation. We test it on real questions before launch and track what it can't answer after.

01/signals

When a custom AI chatbot makes sense

  1. Your support team answers the same questions every day, and the answers are already in your help pages or policies.

  2. Shoppers ask about sizing, stock, shipping or order status and leave when nobody replies.

  3. Staff search shared drives and wikis for policies and procedures, or ask a colleague instead.

  4. Website visitors want answers outside office hours, in their own language.

  5. You tried a generic chatbot plugin, but it made things up or couldn't use your content.

  6. Sales spends time on enquiries that a few questions could have qualified first.

02/use cases

What a custom chatbot can do

What you need01A website support chatbotWhat we buildA chat widget that answers from your help centre, docs and policies, with links to the source pages.
What you need02Shopify product and order questionsWhat we buildA store assistant that answers from your catalog, shipping and returns policies, and looks up order status for verified customers.
What you need03An internal knowledge assistantWhat we buildA bot for staff that answers from policies, handbooks and documents, and respects who may see what.
What you need04Lead qualificationWhat we buildA chat flow that asks the right questions, captures the answers in your CRM and books a call when the lead fits.
What you need05Answers on WhatsApp, Slack or TeamsWhat we buildThe same knowledge base behind a bot on the channels your customers or staff already use.
What you need06Multilingual answersWhat we buildReplies in the visitor's language from the content you have, with the source still cited.
What you need07Handover to a humanWhat we buildA clear path to a person, with the conversation passed to your helpdesk or inbox so nobody repeats themselves.
What you need08Analytics on what people askWhat we buildReports of common and unanswered questions, so you know which content to add or fix.
03/build

AI chatbot project

A scoped build that takes one chatbot from your content to a tested, monitored launch on the channels you choose.

What we do

  • Agree the bot's job, audience, channels and what it must not answer
  • Connect your content sources: website, help centre, documents, catalog or database
  • Build retrieval over that content (RAG) with TypeScript and Node.js, using Postgres with pgvector or a managed vector database
  • Choose the model per use case: OpenAI, Anthropic Claude, Google Gemini or an open model
  • Add guardrails, human handover, an AI disclosure notice and privacy controls

What you get

  • The chatbot running on your website, store or messaging channels, on your accounts
  • An evaluation set of real questions and a report of how the bot answered them
  • A dashboard of conversations, unanswered questions and usage, plus a guide to updating its content

Scoped after a call; the estimate depends on content sources, integrations, channels and volume.

04/reliability

How we keep chatbots reliable

A chatbot is only useful if people can trust its answers.

  1. 01

    Answers come from your content and cite the sources they used, so users and your team can check them

  2. 02

    Guardrails keep the bot on topic, and it says "I don't know" instead of guessing when the content doesn't cover a question

  3. 03

    A person can take over at any point, and the bot hands over on request or when it is unsure

  4. 04

    We run an evaluation set of real questions before launch and again after every change to prompts, content or model

  5. 05

    Monitoring flags unanswered questions, poor answers and unusual traffic

  6. 06

    Rate limits, caching and model choice keep running costs predictable as volume grows

05/process

How it works

  1. 01

    Scope

    The bot's job, users, channels, content sources and limits.

  2. 02

    Prototype on your content

    A working bot on a sample of your real content to test early.

  3. 03

    Evaluate

    Real questions, measured answers, and fixes before anyone outside sees it.

  4. 04

    Launch and improve

    A monitored launch, then regular updates from unanswered questions.

/faq

AI chatbot questions

We design, build and run chatbots that answer from your own content and connect to your systems. That covers choosing the model, building retrieval over your content, adding guardrails and human handover, testing before launch, and monitoring after. Webguru builds chatbots for websites, Shopify stores and internal teams.

ChatGPT answers from general knowledge. A custom chatbot answers from your website, documents and data, stays on the topics you allow, cites its sources, follows your tone and hands over to your team. It runs on your website or channels, under your accounts and your privacy settings.

Yes. We index your pages, help centre, PDFs, policies or database and use retrieval-augmented generation (RAG), so each answer is based on the passages it found and links to them. When your content changes, the index updates.

The bot answers only from retrieved content, cites its sources and is told to say it doesn't know when the content doesn't cover a question. We test it against a set of real questions, including ones it should refuse, before launch and after every change. No AI system is error-free, so we also log unanswered questions and give users a route to a person.

It depends on the use case. We work with OpenAI, Anthropic Claude, Google Gemini and open models, and choose based on answer quality on your content, speed, cost, languages and where data may be processed. The design lets you switch models later.

We design for UK GDPR and EU GDPR: we minimise the personal data the bot collects, set retention periods, put data processing terms in place with providers, and choose a processing region where the provider offers one. We use API providers that document they don't train on API data by default. The bot tells users they are chatting with AI, which the EU AI Act (Article 50) requires for EU users from 2 August 2026. Your legal team should still review the final setup.

Yes. Users can ask for a person at any time, and the bot can hand over when it is unsure or the topic is sensitive. The conversation goes to your helpdesk, inbox or live chat tool, so your team sees the full context.

Yes. The same chatbot can run as a website widget, inside your Shopify store, and on WhatsApp, Slack or Microsoft Teams. On Shopify it can answer product, shipping and returns questions and look up order status for verified customers. See our Shopify AI services for more store use cases.

You do. The code, prompts, evaluation set and content index run on your accounts, and the model provider contracts are in your name. We hand over documentation so your team or another developer can maintain it.

It depends on the content sources, integrations, channels and expected volume. A bot that answers from one help centre is a smaller build than one that reads order data and runs on several channels. We quote after a short call about what you need.

09/quote

Scope your chatbot

Tell us what the chatbot should answer, who will use it and where your content lives. We'll reply with next steps.

Prefer email? Write to webguru.com.pk@gmail.com