Running a WhatsApp Chatbot in Nepali: What Works and What Does Not



A WhatsApp chatbot in Nepali works well for structured tasks — checking an order, booking an appointment, answering common questions — and poorly for open conversation. The biggest practical decision is not the technology. It is whether to write in Devanagari or Romanised Nepali, and the honest answer is usually both.

Devanagari or Romanised Nepali?

Your customers write both, often in the same message, and a bot that only understands one will fail half the time.

People type Romanised Nepali — "kati ho", "order kahile aauncha" — far more than businesses expect, because it is faster on a phone keyboard and requires no keyboard switching. Older customers and formal contexts lean to Devanagari. Many messages mix Nepali and English words freely.

What works in practice:

• Reply in Devanagari. It reads as correct and professional, and everyone can read it.
• Understand both, plus English. Your matching has to accept "1", "एक", "ek", and "one" as the same answer.
• Do not correct people. A bot that says it did not understand because someone typed Romanised is a bot people stop using.

Use buttons rather than free typing

This is the single highest-value design decision, and it sidesteps most language difficulty.

WhatsApp supports reply buttons and list menus. A customer tapping "मेरो अर्डर" has given you unambiguous input with no spelling, no transliteration and no ambiguity. A customer typing the same thing gives you a dozen possible spellings.

Use buttons for anything you can enumerate: main menu, order status, business hours, talking to a person. Reserve free text for the genuinely open — a delivery address, a complaint — and hand those to a human.

What a Nepali chatbot handles well

• Order status. Customer taps a button, gives an order number, gets an answer. No language difficulty at all.
• Business hours, location, price lists. High volume, zero variation, ideal for automation.
• Appointment booking. A menu of dates and slots works cleanly in either script.
• Routing. Ask what the customer needs and send them to the right person with context already gathered.
• After-hours holding. Acknowledge, collect the essentials, promise a morning reply — and keep the promise.

What it handles badly

• Complaints. An upset customer wants a person. A bot insisting on a menu makes it worse.
• Negotiation. Common in Nepali retail and not something to automate.
• Anything with money moving. Confirm with a human.
• Open questions about complex products. The bot will guess, and a confident wrong answer costs more than no answer.

Always give a way out

Every bot needs an obvious, permanent escape to a human, available at every step — a visible "कुरा गर्नुहोस्" or "Talk to us" button, not a hidden keyword.

Two details that matter. Make the handover real: if nobody is available, say so and give a time, rather than leaving the customer waiting on silence. And carry the context across, so the person does not open with "how can I help?" after the customer has already explained twice.

The free window, and why bots pay for themselves

When a customer messages you, a 24-hour window opens in which your replies are free. A bot answering inside that window costs nothing per message.

This is the real economics of WhatsApp automation in Nepal. The bot is not primarily saving you message costs — replies were already free. It is saving staff time on repetitive questions, and keeping conversations alive inside the free window instead of letting them lapse into paid template re-engagement.

Testing before launch

Test with people who actually write the way your customers write, not with staff who know the intended wording. Give five customers the bot and watch where they get stuck — it will be somewhere you did not anticipate, usually a spelling variant or a question your menu does not cover.

Then keep reading the transcripts. The messages where the bot failed are your roadmap, and they are more useful than any amount of planning.

Questions we get asked

Can a WhatsApp chatbot understand Nepali?

Yes, in both Devanagari and Romanised Nepali. Reliability is far higher for structured tasks with buttons than for open conversation.

Should the bot reply in Nepali or English?

Devanagari Nepali for consumer audiences generally, while accepting input in Devanagari, Romanised Nepali and English. Some business audiences prefer English — test rather than assume.

Does a chatbot cost extra per message?

Replies inside the 24-hour customer service window are free, and that is where most bot conversation happens. See WhatsApp Business API pricing in Nepal.

Will a chatbot annoy my customers?

It will if it traps them. A bot that answers a simple question in two taps, and hands over to a person the moment it is asked, is generally welcomed.

Do I need the API for a chatbot?

Yes. The free WhatsApp Business app offers only a fixed away message, not automated flows.

---

Dibi Tech Private Limited is an official Meta Tech Provider based in Janakpur, Dhanusha, Nepal. We build WhatsApp automation in Nepali and English for Nepali businesses.