Who this is for
Businesses whose website or WhatsApp receives the same questions all day and whose enquiries arrive at hours when nobody is working: clinics, education consultancies, travel companies, stores, software companies and any service business where the first answer decides whether the person keeps talking. Chatbot development is one of the builds under marketing and business automation services, and the modelling and guardrail approach behind it is set out on AI automation services.
It is a poor fit for a business without documented answers. A bot cannot be more accurate than the material it reads. If your prices, policies, eligibility rules and hours live in people’s heads, the first half of this project is writing them down, and that work is worth doing whether or not a bot ends up on the site.
Two kinds of bot, and which one you need
| Menu and rules bot | AI bot on your content | |
|---|---|---|
| How it answers | Buttons and fixed paths you wrote | Reads the question, retrieves from your documents, writes an answer |
| Best for | Booking, order status, a short fixed catalogue | Varied questions, long policy documents, multiple services |
| Risk | Dead ends when the user wants something unlisted | A wrong answer if retrieval and limits are set up badly |
| Running cost | Platform subscription only | Subscription plus model usage per conversation |
| Maintenance | Edit the flow when something changes | Update the source document; the bot follows |
Most builds end up as a hybrid: buttons for the three things everyone wants, an AI layer for everything else, and a person one tap away throughout. I recommend the cheaper option whenever it will do the job.
What the bot does
- Answers from your own material. Service pages, price lists, policies, FAQs and product data are indexed, and answers are generated only from what is retrieved. Questions outside that material get an honest hand-off, not an invented answer.
- Qualifies. Collects the two or three facts your sales or front desk always asks for, such as service needed, location, timeline and budget range, and writes them to the CRM through CRM setup and integration.
- Books. Offers real available slots and confirms, with reminders handled by appointment booking and reminder automation.
- Looks things up. Order status, application status or account details, fetched live from your system rather than guessed.
- Hands off. Transfers to a named person with the full conversation, the qualification answers and the page the visitor was on, inside a response commitment you set.
- Reports. Every conversation logged with the question, the answer, whether the source material covered it and whether the visitor asked for a human. The list of questions it could not answer is the most useful output in month one.
What it will not do
- Give medical, legal or financial advice. Those categories are routed to a qualified person by rule.
- Quote a discount, negotiate or commit to a delivery date the system cannot verify.
- Pretend to be a human. Every bot identifies itself in its first message.
- Handle a complaint. Frustration and refund language trigger an immediate hand-off, as covered under customer support automation.
- Take payment card details or ID numbers in chat.
How a build runs
- Collect the real questions. A month of website chat, WhatsApp threads and phone notes. The mix tells us whether a menu bot is enough and which twenty answers matter.
- Write and approve the knowledge base. Answers in your words, in Nepali and English where both are used, with a named owner for each. This is the largest and most valuable part of the work.
- Set the boundaries. The do-not-answer list, the hand-off triggers, the response commitment in and out of office hours, and the fallback wording when the bot does not know.
- Build and test against a scored question set. Fifty real questions with correct answers; the bot is measured against them before anyone sees it, and the score decides whether it launches.
- Launch on one channel with conversation logging and a visible route to a person, then review the unanswered-question list weekly and feed it back into the knowledge base.
- Extend to the second channel once the first is answering reliably.
What you receive
- The bot running in your own accounts, on your own model API keys, with the widget or WhatsApp number in your name.
- The approved knowledge base as an editable document, plus the process for adding an answer without me.
- The scored test set, so future changes can be re-checked rather than trusted.
- Conversation logs, a weekly unanswered-questions report and hand-off timing alerts.
- Documentation, a pause switch and a 30-minute training for whoever takes the hand-offs.
Pricing pointer
Setup is quoted on request; a menu-based bot on one channel sits at the lower end of the range. An AI bot answering from your documents on website and WhatsApp, with CRM and booking integration, sits toward the top, with knowledge-base work and testing making up most of the effort. Maintenance is quoted on request; model usage and any messaging platform subscription are billed to your own accounts. International clients are quoted 40 to 60 percent below comparable Western agency rates, month to month.
Next step
Send your website URL, the channels enquiries arrive on and any existing FAQ document. I will come back within four business hours with an honest answer about whether you need a menu bot or an AI bot, what the knowledge-base work involves and a fixed price.
