Sanskar Kharya

We already are getting a overwhelming response in ourr website and product and people are loving it, try it out first hand
https://platform.vaani.dev/
Grab your free credits, and this thread and our socials are open for feedback and comments, Thank you so much!

Our callers mix Hindi and English in the same breath: "haan toh mein bol raha tha, why are you calling me?" We assumed language handling was a detection problem. It turned out to be about six separate problems, and we found them one at a time, in production.

1. Detecting a language switch without flip-flopping
A caller says one English word and the bot jumps languages. We settled on a heuristic switch with guardrails you can configure per agent:

• a minimum number of words per turn (default 3)

• the same language for consecutive turns (default 2)

• a dominant-language threshold (0.6) from a fastText classifier

• a reset of the counter on mismatch, so one stray turn doesn't count

• "meta" references ignored, for example someone saying "English" while speaking Hindi

2. Callers who just tell you what they want
"Let's speak in English" shouldn't need two confirming turns. We added explicit request detection, in English and Hindi (e.g. " "). It bypasses the heuristics and switches immediately.

Here's how webhooks work in Vaani (no code needed)

A webhook is just Vaani sending your app a message when something happens on a call.

You pick the events you care about: call_started, call_ringing, user_picked_up_at, call_rejected, call_no_answer, call_failed, call_ended.

You give us a URL. When a call ends, we send it a message, and you can drop the result in a Google Sheet, ping Slack or update your CRM.