Kolkata breaks the pattern the rest of this series has been making. In most Indian cities, the argument is straightforward: businesses default to English or Hindi, and a real share of callers are quietly underserved because their actual language is something else. Kolkata is genuinely bilingual in a deeper, older way than that framing accounts for — a city with a long intellectual and literary tradition in both Bengali and English, where plenty of people move between the two within a single conversation, comfortably, by choice rather than necessity.
That makes the lazy version of this argument — "your customers are hanging up because you don't speak their language" — actually wrong for Kolkata, or at least incomplete. The real issue isn't that English fails here. It's that assuming either language covers everyone is where businesses get it wrong.
Bilingual doesn't mean interchangeable
A caller in Kolkata might open a call in English and switch to Bengali the moment the conversation gets specific — an actual health concern, a price they want to negotiate, a complaint they want to make forcefully. That's not a random flip. People often reach for the language that carries more emotional precision for the thing they're actually trying to say, and for a lot of Bengali speakers, especially on anything that matters, that's Bengali — even when the small talk around it happened in English.
A support line that only speaks English catches the small talk and misses the part of the call that actually mattered. A support line that only speaks Bengali misses the callers, especially younger and more transient ones, who default to English out of habit and would find a Bengali-only system oddly formal for a quick question.
The mistake in Kolkata isn't picking the wrong language. It's picking one at all, in a city built on using both.
Why the switch happens where it happens
Picture a call to a clinic in Salt Lake: the caller opens in English — "hi, is the doctor available Wednesday morning" — because that's the register a first appointment question gets asked in. Two minutes later, describing an actual symptom that's been bothering them for a week, they slide into Bengali without noticing they've done it, because that's the language the discomfort is easiest to put into words in. AIVA follows that shift the way a bilingual receptionist would — not resetting the conversation or asking "would you like to continue in Bengali," just continuing in whichever language the caller is actually using at that moment. Missing that switch isn't a small failure. It's exactly the part of the call — the actual concern — that a business can least afford to get wrong.
What this means for how the phone should work
AIVA doesn't ask a caller in Kolkata to pick a language. It detects Bengali or English from the first sentence and replies in kind — and if the caller switches mid-call, from a pleasantry in English into a real question in Bengali, the model follows that switch instead of forcing the conversation back into whichever language it started in. That's the code-switching handling built into every language AIVA supports, and Kolkata is one of the clearest places to see why it matters: the switch isn't a fringe case here, it's Tuesday.
Where it shows up
A clinic in Salt Lake fielding calls that start "hi, is the doctor available" and finish with a detailed Bengali description of symptoms. A sweet shop or tailoring business in North Kolkata where older customers call in Bengali and their children, ordering on their behalf, call in English. A coaching centre where the parent asks about fees in English and the specifics of the syllabus in Bengali. A restaurant near Park Street taking dinner reservations sees the same pattern on a smaller scale: a first-time caller who found the place online books a table in English, while a regular calling for a family gathering slips into Bengali mid-call to specify exactly which corner table or which fish preparation they want — the kind of detail people reach for their first language to get exactly right. None of these are two different customer segments. They're the same city, doing what Kolkata has always done with language.
The generational split, not just the topic split
Age plays into this as much as topic does. A tailoring business or a sweets shop in North Kolkata often has older customers who call in Bengali as a matter of course, and their children or grandchildren, ordering on their behalf or making a payment, who default to English out of habit picked up at work or college. A newer business in Salt Lake or New Town, built around a younger, more corporate customer base, sees more English by default, with Bengali surfacing the moment a caller's parent gets on the phone instead. Neither pattern is fixed, and a lot of Kolkata businesses genuinely serve both audiences on the same phone line, sometimes in the same afternoon. It's a different shape of the same language question the rest of West Bengal faces — there, the issue is Bengali being skipped in favor of Hindi or English entirely; in Kolkata, it's picking one language when the real answer is both.
The same choice, in text
The same bilingual reality shows up on AIVA's web chat widget, not just on calls. Someone typing in English gets answered in English; someone typing in Bengali script gets answered in Bengali; a conversation that starts in one and drifts into the other partway through gets followed the same way a phone call would be. A chat widget that forces a language choice before the first message — a common pattern on generic chat tools — asks a Kolkata visitor to solve a problem that shouldn't exist: deciding which of two entirely normal languages they're "supposed" to use with this particular business.
Checking how your own calls actually split
You don't have to guess whether your customers lean English, lean Bengali, or are genuinely mixed. Once AIVA is running, the analytics dashboard shows which language each conversation happened in — data most Kolkata businesses have never had a clean way to see before. A business that assumes it's "mostly an English crowd" based on what shows up in a WhatsApp inbox is often looking at typing habits, not real language preference — someone who'd rather speak Bengali will often still type in English out of keyboard convenience. Voice calls don't have that distortion, which makes the phone the more honest measure of the two, and a couple of weeks of real call data usually says something different from what the business assumed going in.
What it costs, and what happens when a call needs a person
None of this changes what AIVA costs to run — pricing is pay-as-you-go at ₹4 a minute for voice, ₹2 per web chat conversation, and ₹1 per SMS, with ₹500 in free credit and no card required to start. And when a call genuinely needs a person, whichever language it happened in, AIVA hands off with that full conversation already captured — so a complaint that started in English and turned serious in Bengali doesn't have to be re-explained from scratch to whoever picks it up next. Here's how that handoff is actually built.
The number underneath it
Across AIVA's calls generally, about 96% resolve without a human joining in, at around 198ms average response time — and for a genuinely bilingual city, that number depends on the system not forcing a choice the caller never wanted to make. The same bilingual handling is part of AIVA's full language coverage, alongside eleven other Indian languages built the same way — natively, not as a translation layer bolted onto English.
If you run a business in Kolkata, start free and see how it handles a call that moves between English and Bengali — the way your actual customers do. Or call +91 96623 20707 and switch languages mid-call yourself.