Listen to almost any B2B sales call in India and you will hear two languages in the same sentence. "Budget toh approved hai, but procurement ko next quarter tak time chahiye." The buyer opens formally in English, relaxes into Hindi when the real objection comes out, and switches back to English for the numbers.
That switching is normal. It is also exactly where most meeting notetakers break.
Where the notes go wrong
Most transcription tools pick one language for the whole call. When the speaker switches, one of three things happens:
- The Hindi parts come out as nonsense. The engine forces Hindi sounds into English words, and you get a transcript full of lines that read like typos.
- The Hindi parts disappear. Some engines treat speech they cannot place as noise and drop it. The transcript looks clean, but it is missing the sentence that mattered.
- The summary is built on the gaps. An AI summary can only use what the transcript contains. If the objection was said in Hindi and the transcript lost it, the summary says the call went well.
The third one is the expensive one. A rep reads "positive call, next steps agreed", the manager reads the same thing in the CRM, and nobody hears that the buyer said "hum abhi commit nahi kar sakte" until the deal goes quiet.
What a good set of notes from a Hinglish call needs
Whatever tool you use, notes from a code-mixed call should pass four checks.
1. Every part of the call is in the notes, in one language
The notes should be in one language your whole team reads, usually English, whatever language each sentence was spoken in. A translated line is fine. A missing line is not.
2. Every claim points to the moment it was said
"Budget approved" is a claim. If the notes cannot show you the second of the call where the buyer said it, you cannot check it, and neither can your manager. Notes you cannot check are notes nobody trusts after the first wrong one.
3. The outcome comes first
The most useful sentence in any call summary is what happened. Did they agree to a pilot, ask for a proposal, push it to next quarter, or not show up? Polite refusals are especially easy to miss in Hinglish calls, because "dekhte hain" ("we'll see") sounds friendly and means no.
4. The small talk stays out
The first five minutes of many calls are about traffic, cricket or whoever is still joining. That should not end up in the summary or the CRM.
How EchoBrief handles it
We built EchoBrief for exactly this kind of call. The notetaker joins your Google Meet, Zoom or Microsoft Teams call, and afterwards you get:
- English notes from the whole call, including the parts spoken in Hindi. Speech-to-text runs on a model built for Indian languages and code-mixed speech, and translates to English as it transcribes.
- A quote and a timestamp behind each point. Click any line and the recording plays from that second. Claims that cannot be matched to the transcript are removed before the summary is sent.
- The outcome first, written from what was actually said, including no-shows, conditional yeses and polite refusals.
- A deal card for sales calls: outcome, budget, decision maker, timeline, pain points, objections and next step. Anything that was not discussed says "Not discussed" instead of being guessed.
- The small talk left out. Summaries and insights cover the part of the call when your guests were in it.
You can see more on the Hinglish meeting transcription page.
Try it on a real call
The simplest test is your own next sales call. Request access to the invite-only beta, connect your calendar, and compare the notes with what you remember from the call. Look especially at the parts that were said in Hindi.