An AI Chatbot for Your Website: How to Capture Leads at Night and on Weekends Without New Hires

Short answer: an AI bot isn’t “a toy with artificial intelligence” — it’s a way to close three specific funnel leaks: answering out of hours, answering in the first seconds, and the repetitive questions that eat employee hours. Payback is a five-minute math: missed enquiries × conversion × average order value. It ships in 2–3 weeks if you have a knowledge base and a CRM.

Count the losses before you build

The formula is simple: enquiries per day × share without a fast reply × conversion to order × average order value × 30.

Parameter	Store (example)	Agency/service (example)
Enquiries per day	60	12
No reply in first 5 min	25%	40% (evenings, weekends)
Conversion of a “cold” lead	3% instead of 12%	5% instead of 25%
Average order value	$40	$1,100
Monthly loss	≈ $650 of revenue	≈ $11,000 of revenue

This isn’t scaremongering — it’s why the first bot is deployed where there’s a stream of repetitive questions, not where it’s “trendy”.

Checklist: is your business ready for a bot

Answer “yes” to at least 5 of 7 — and the rollout will pay off:

1. Repetitive questions: prices, availability, timelines, delivery, order status, warranty terms.
2. A knowledge base exists, even if messy: price lists, policies, FAQ, manager email history.
3. Leads come from several channels: site, Telegram, WhatsApp, Instagram, email, phone.
4. Managers physically can’t reply in the first minutes.
5. There’s a CRM or sheet where the bot can write leads (otherwise they vanish “in the chat”).
6. Enquiries come at night, on weekends, in peak season.
7. You’re ready to delegate part of the decisions: qualify, reschedule a visit, send a quote template.

What different “bots” can do — and what you don’t need

Type	What it does	When it’s enough	When it’s not
Buttons & scripts	branching “price → package → lead”	5–10 routine questions, a narrow service	free-form questions
Form widget	captures a contact, alerts a manager	low volume, replies are on time	you need an answer right now
RAG bot on a knowledge base	answers from your documents, semantic search	high volume of routine enquiries	deep expertise, bespoke quotes
AI agent with actions	creates a deal, checks stock, places an order, drafts a reply	processes documented, API/CRM exists	processes live “in people’s heads”

If your processes aren’t documented, start with an audit and a map, as in the AI automation guide — otherwise the bot is “pretty but useless”.

Architecture: how it works without magic

1. Knowledge base. Price lists, service descriptions, FAQ, policies, chat history → cleaned, chunked, indexed in a vector store (Qdrant or pgvector).
2. Model. OpenAI or Claude: understand the question, assemble an answer from retrieved chunks, ask clarifying follow-ups. The model swaps in one config line — no vendor lock-in by design.
3. Escalation rules. The bot hands to a human: payments, complaints, non-standard quotes, “let me talk to a person”, three low-confidence answers in a row — with full context.
4. Integrations. CRM (create deal and contact), warehouse/ERP (stock), site and messengers (Telegram, WhatsApp), telephony and email.
5. Logs and dashboard. Which questions come in, which the bot fumbles, how many dialogues it closed, how many leads reached a deal, token spend.
6. Security. Access roles, no personal data in prompts, data stays on your own store.

Launch in 5 steps and 3 weeks

Economics: rollout and monthly costs

Line item	Typical range	Note
Rollout with RAG and integrations	from $2,900	includes dialogue audit, knowledge base, dashboard
API tokens	$50–$400/mo	depends on volume: 1 dialogue ≈ $0.10–$0.25 in model calls
Hosting and vector store	$25–$100/mo	for your own data and logs
Support and retraining	$200–$500/mo	weekly dialogue review, new documents

Token spend is visible in the dashboard from day one: you always know the cost of a closed dialogue and can compare it to the cost of a manager’s minute.

FAQ

Bottom line

An AI bot pays back when you count not “the technology” but three numbers: how many enquiries go unanswered, their conversion, and the average order value. Everything else is technical — a matter of 2–3 weeks and transparent token economics.

Order an AI bot rollout → — we’ll start by analyzing your real dialogues and calculating lost revenue, then propose a solution. Service details are on the AI integration page.