Website assistant
An embedded chat widget answering questions from your own pages, documents and product information.
Chatbot development — Nepal
Soft Himalaya builds website assistants, WhatsApp Business bots and knowledge-based support chatbots from Kathmandu for businesses in Nepal, the UK, Australia, the USA and Canada.

Support starts with people
An assistant handles agreed repeat questions and hands uncertain or sensitive cases to your team.
What we build
Most businesses need one channel done properly rather than a bot on every surface. We scope the channel, the questions it answers and where it hands over.
An embedded chat widget answering questions from your own pages, documents and product information.
A bot on your business number using the official Meta Cloud API, within Meta's template and opt-in rules.
Automated replies to common direct messages, with escalation to your team for anything unusual.
Answers retrieved from your documents so responses cite your material rather than a model's general knowledge.
Structured questions that collect contact details and requirements, then pass them to your CRM or inbox.
Appointment slots, order lookups and status updates connected to the system that holds the real data.
Conversations and contacts synced to the tools your team already works in, with ticket creation where needed.
Handling of Devanagari, Romanized Nepali and English, tested with the phrasing your customers actually use.
Volumes, unanswered questions and handover rates reviewed so the bot improves after launch.
What to expect
A chatbot is good at repetition and availability. It is not a replacement for judgement, and a badly scoped one costs more goodwill than it saves in staffing.
Opening hours, delivery times, order status, pricing basics — the questions your team answers dozens of times a week are the ones worth automating first.
A language model asked about your business without your content will guess. Answers are retrieved from approved material, and unanswerable questions are handed over rather than fabricated.
The measure of a good bot is not how few conversations reach a human, but how few people leave without an answer.
Products, prices and policies change. Without periodic review of transcripts and content, a bot slowly starts giving out-of-date answers.
How we work
Timelines depend on the channel, how ready your content is and which systems the bot needs to read from. We plan the schedule once the intents are agreed.
We review your real enquiries — inbox, chat logs, phone notes — and list the questions the bot should handle, and the ones it should not.
The material each answer will be drawn from is identified: pages, documents, product data or a system the bot needs to query.
Conversation paths, fallback wording, handover rules and response tone are drafted and approved before implementation.
The assistant is built on the chosen channel and connected to the CRM, helpdesk or business systems in scope.
Flows are tested with the way customers actually write, including mixed languages, typos and questions outside the scope.
The bot goes live with logging enabled, and transcripts are reviewed on an agreed cycle to correct gaps and wrong answers.
Example
This is a scripted walkthrough rather than a live assistant. The interesting cases are the last three: what a bot does when it should not answer matters more than what it does when it can.
Try a question
Hello. This is a scripted demonstration — pick a question below to see how the assistant is designed to respond.
Your assistant would answer from your own content and connect to your own systems. This demo does not send anything anywhere.
Tools
Model and platform choices are made per project. Where a paid API is involved, the account is set up in your name so usage and cost stay visible.
Language models for open-ended conversation
Official WhatsApp Business messaging
Answers grounded in your documents and pages
Webhooks, backends and embedded widgets
Conversation storage and content lookup
Lead sync and ticket creation
Where it fits
These are the patterns businesses usually bring us. Each still starts with the same question: which enquiries repeat often enough to be worth automating?
Stock and delivery questions, order status lookups and product guidance during browsing hours and after them.
Admission criteria, fee structures, deadlines and document requirements answered from published information.
Appointment availability and preparation instructions, with anything clinical routed to qualified staff rather than answered.
Package details, availability enquiries and pre-booking questions, with the booking itself handled by your system.
Listing details, viewing requests and qualification questions passed to the agent handling that enquiry.
Consignment tracking, common troubleshooting steps and ticket creation when the issue needs a person.
Project estimates
Cost depends on the channel, how many intents are in scope, whether the bot reads from live systems and how much content preparation is needed. Model and messaging usage is billed by the platform and is separate from our fee.
A defined set of questions and flows — hours, services, directions, simple lead capture.
Answers retrieved from your own content, with handover rules and transcript review.
A bot that reads from or writes to your live systems — orders, bookings, accounts or tickets.
Questions
Common questions about channels, AI versus scripted flows, data handling and how chatbot work is quoted.
It is the work of deciding which questions an automated assistant should handle, where its answers come from, and what happens when it cannot help. That covers scripted flows, language-model assistants grounded in your own content, the channel it runs on, and the connections to your CRM or support tools.
Working together
We do not publish anonymous client quotes, satisfaction scores or deflection percentages that cannot be checked. These are the standards we hold ourselves to instead.
The intents, channels, integrations, handover rules and review cycle are documented before development starts.
Model API keys, WhatsApp Business accounts and any platform subscriptions are created in your name.
The bot responds from content you have signed off, and unanswerable questions go to a person rather than a guess.
We report conversation volumes, handover rates and the questions the bot could not answer, not just the flattering totals.
Start a project
Send the enquiries your team repeats most, the channel you want the bot on and any system it would need to read from. We will reply with questions, a suggested scope and an estimate.