How to Test a Hinglish Chatbot Before Launch: A Practical Checklist

Most chatbots in India are tested by the people who built them. They type clean, complete sentences in English, wait patiently for each reply and know exactly what the bot can do. Real customers do none of those things.

A customer in Kanpur types "mera refund abhi tak nahi aaya, kya scene hai" on a ₹9,000 phone with a cracked screen and two bars of signal. If your bot has never seen messages like that, it will fail quietly — and the customer will leave without telling you why.

This checklist is how we approach chatbot testing in our Bharat Bot Test. You can use it yourself, or let us run it for you.

Step 1: Write down the five jobs your bot must do

Before writing a single test, list the five most important things customers come to the bot for. For an e-commerce brand this is usually:

1. Track an order
2. Cancel or return an order
3. Ask about a refund
4. Change an address or phone number
5. Talk to a human

Every test you write should map to one of these jobs. If a test does not, it is probably less important than you think.

Step 2: Test the way people really type

For each job, write messages in at least four styles:

• Clean English: "Where is my order?"
• Hinglish: "Order kab tak aayega?"
• Romanised Hindi with spelling variety: "mera ordr kha hai", "order kahan h"
• Devanagari: "मेरा ऑर्डर कहाँ है?"

Add the small things real users do: no punctuation, voice-to-text mistakes, one-word messages ("refund"), and emojis. A bot that only handles the first style is not ready for Bharat.

Step 3: Test memory across turns

Ask the bot something, give it a detail, then ask a follow-up that depends on that detail. For example:

"Mera order 48213 hai" → "Uska status kya hai?" → "Aur delivery kab tak?"

A good bot remembers the order number from the first message. Many do not, and ask for it again — which is exactly where customers give up.

Step 4: Try to break it on purpose

Real users go off-script. Test what happens when someone:

• Asks something the bot cannot do ("loan milega kya?")
• Gets angry or uses rude words
• Shares personal details like a full card number
• Asks the bot to ignore its instructions

The right answer is often "I can't help with that, but here is who can". The wrong answer is an invented policy, a promise you cannot keep, or a leaked internal instruction.

Step 5: Check the handover to a human

Ask for a human in three ways: "talk to agent", "insaan se baat karao" and "koi real person hai?". Does the bot hand over? Does it pass along what the customer already said, or does the customer have to start again?

Step 6: Put it in front of real people

Internal tests catch obvious bugs. Real users catch the rest: confusing words, replies that are too long for a small screen, and moments of distrust. In our tests, real people from Tier-2 and Tier-3 towns use the bot naturally, in their own words, while we record the session with their consent.

What you should get at the end

A useful chatbot test does not end with "it seems fine". It should give you:

• A score for each area — understanding, accuracy, safety, handover — with evidence behind every number
• The exact conversations that failed, so your team can reproduce them
• A short list of fixes, most important first

That is what our sample report looks like.

Ready to test yours?

The AI Tool Check is our fastest way in: a focused review of your chatbot with real users and a scored report. See Bharat Bot Test pricing or tell us about your bot and we will suggest the right package.