Hindi, English, or Hinglish — why the language of your call audits matters more than you think
First published in The Compliance Floor on LinkedIn, 16 June 2026. Regulatory positions are as they stood on that date.
Most collections floors audit their calls in English. The calls did not happen in English.
They happened in Hindi, or in the Hindi-English mix every Indian floor actually runs on — Hinglish. Somewhere between the recording and the QA scorecard, the call was translated, and the audit was run on the translation. That step feels harmless. It is where the audit quietly loses the one thing it exists to catch.
Translation preserves the facts of a call — the amount, the date, the promise to pay. It does not preserve menace. A sentence that is administrative in English can be a threat in Hindi, and a sentence that reads as a threat in English can be ordinary on the floor. Sentiment scoring trained on English misses both directions. The agent stays polite on paper. The borrower hangs up frightened. Only one of those two facts reaches your report.
What the translation drops
Across our audit network, the same patterns recur — and almost none of them survive the trip into English.
Start with the pronoun. Hindi carries respect in the choice between aap and tu. An agent who opens with aap and, three minutes in, drops to tu has done something an Indian borrower hears instantly: the conversation has turned. There is no English equivalent. “You” is “you”. The single clearest escalation marker on the call disappears in translation.
Then the references that sound like logistics. “Ghar aa jayenge” — “we’ll come to your house” — reads in English as a visit being scheduled. On the call it is a warning. “Aas-paas sabko pata chal jayega” — “the whole neighbourhood will know” — reads as a statement about information. It is a shaming threat, and a DRA breach. “Bacchon ka socho” — “think of your children” — translates as gentle advice and lands as pressure.
And the register that flatters the transcript. An agent can stay on courteous words while the tone, the speed, and the tu do the intimidation. The English transcript records a polite call. The recording is of something else.
Nothing requires you to audit in the source language. The evidence does.
No RBI circular tells you which language to run your QA in. That is exactly why the gap stays invisible — nothing flags it, so nobody closes it.
But when a borrower complains — to the lender, or onward to the RBI ombudsman — the evidence is the original recording, in the original language. The complaint will quote the actual words: the tu, the line about the house, the reference to the children. If your floor only ever reviewed an English rendering, you cannot even find the moment being described, let alone defend it. You audited one call. The lender and the regulator are listening to another. The distance between the two is where the case is lost — and where the lender quietly marks you as the agency that did not catch it.
What to ask your QA team this week
Three questions. None needs a policy review — only an honest answer.
- What language is the audit actually performed in? Not the call — the audit. If your analysts or your tool score an English transcript, you are auditing a translation.
- What language is the transcript stored in? If the only artefact you keep is English, you have already discarded the evidence a complaint will be fought on.
- What happens when a complaint quotes a specific Hindi phrase? Walk one through. If the honest answer is “we’d go back to the recording” — good. If it is “we’d check the English transcript” — that is the gap, named.
A floor that audits in the language the call happened in catches the tu, the house, the neighbourhood, the children. A floor that audits the translation catches the words and misses the call.