The WhatsApp Business Language Ceiling: 11 Languages, 22 Scheduled, and the MSMEs Left Off Both

The channel MSMEs actually use

Most conversations about MSME digital readiness in India start with a website, a Google Business Profile, or a marketplace listing. For the median small business, none of those is the primary channel. WhatsApp is. A 2024 report jointly produced by Bain and Company and Meta, based on a commissioned survey of 7,800 consumers and 150 enterprises conducted in October 2023, found more than 650 million Indians already active on social media and messaging platforms, and 15 million small and medium businesses already using WhatsApp for Business to build a digital presence and drive traffic through click-to-chat ads.

The same report puts a number on how far that presence typically goes: of the roughly 30 million formalized small businesses registered on the Udyam portal at the time, only about 15 percent, some 5 million, were selling online at all. WhatsApp is not a nice-to-have add-on for these businesses. For a majority of them, it is the only structured, always-on channel a customer can reach them on outside a phone call.

That makes WhatsApp Business a de facto national utility for MSME commerce, and it puts real weight on a question that gets asked far less often than it should: which of India's languages does that utility actually run in?

Eleven languages, and only ten of them scheduled

India's Constitution names 22 languages in its Eighth Schedule, the list maintained by the Ministry of Home Affairs and the Department of Official Language. The current 22 are Assamese, Bengali, Gujarati, Hindi, Kannada, Kashmiri, Konkani, Malayalam, Manipuri, Marathi, Nepali, Odia, Punjabi, Sanskrit, Sindhi, Tamil, Telugu, Urdu, Bodo, Santali, Maithili, and Dogri. Fourteen were in the original 1950 Constitution; Sindhi was added in 1967; Konkani, Manipuri, and Nepali followed in 1992; Bodo, Dogri, Maithili, and Santali were added in 2004. English is not on this list. It appears instead on the Ministry's separate roster of 38 languages currently seeking inclusion, alongside Bhojpuri, Rajasthani, and Tulu.

Meta publishes its own list separately: the set of languages and language codes the WhatsApp Business Platform supports for message templates, the pre-approved, reusable messages a business sends through the Cloud API for order confirmations, appointment reminders, and shipping updates. As of the version published on Meta's developer site, that list runs to 128 language and locale codes, from Afrikaans to Zulu, covering everything from Kinyarwanda to six regional variants of Spanish.

Laying the two lists side by side is the actual mapping this piece set out to do, and no publicly available source appears to have done it directly. Of India's 22 scheduled languages, exactly ten appear on Meta's supported list: Bengali, Gujarati, Hindi, Kannada, Malayalam, Marathi, Punjabi, Tamil, Telugu, and Urdu. English, not itself a scheduled language, is also on Meta's list and is the language most WhatsApp Business tools default to outside those ten. Put together, that is eleven languages actively usable for structured business messaging in the Indian market, ten of them constitutionally scheduled and one, English, filling the eleventh slot the title of this piece refers to. Independent technology press covering the separate, free WhatsApp consumer and small-business apps describes the same ten-language set for the in-app interface, which suggests the ceiling is not an artifact of one product tier; it shows up wherever WhatsApp draws a line around "supported" Indian languages.

The twelve left standing outside

Subtract the ten covered languages from the Eighth Schedule's 22, and twelve remain with no native WhatsApp Business template support: Assamese, Bodo, Dogri, Kashmiri, Konkani, Maithili, Manipuri, Nepali, Odia, Sanskrit, Santali, and Sindhi. These are not fringe languages by population. Odia alone has tens of millions of speakers concentrated in Odisha; Assamese anchors most of Assam's commerce; Maithili is spoken across a wide swath of Bihar and parts of Nepal. None of them can be used to send a WhatsApp Business template message natively, which means a business operating in one of these twelve is pushed toward one of three imperfect options: default to English, default to Hindi even where it is not the customer's first language, or hand-type messages one at a time in a script the platform has no formal template support for.

That third option is where the gap compounds. A message typed manually in Odia or Santali script works fine as a one-to-one chat, but it falls outside the templated, catalog-linked, automation-eligible tier of WhatsApp Business that Meta is actively building AI and automation features on top of, including Meta Verified business pages, quick replies, and click-to-WhatsApp ad campaigns. The business is present on the channel; it is just present in a lower, more manual tier of it than a competitor messaging in Hindi or Tamil.

Why this is not a rounding error

It would be easy to read "ten of 22 languages" as a technical footnote, until the scale of who depends on the channel is put next to it. As of 28 February 2026, more than 7.83 crore, 78.3 million, enterprises were registered across the government's Udyam Registration Portal and Udyam Assist Platform combined, according to a Ministry of Micro, Small and Medium Enterprises reply tabled in the Rajya Sabha. That is the formal record of India's MSME base, and it has grown roughly tenfold since the revised registration criteria took effect in mid-2020.

Layer India's underlying internet base on top of that. DataReportal's Digital 2026: India report, drawing on Kepios analysis, put India's internet user base at 1.03 billion as of October 2025, a 70.0 percent penetration rate, with 500 million social media user identities recorded the same month. A meaningful share of both figures are MSME owners, employees, and their customers, and the Bain and Meta research suggests the large majority of them already treat messaging platforms as their default digital surface rather than an app or a website. A ten-of-22 language ceiling on the dominant channel for that surface is not a rounding error against numbers this size; it is a structural cutoff that tracks the state boundaries of Odisha, Assam, the Kashmir valley, and the Maithili-speaking belt of Bihar more closely than it tracks any measure of those regions' commercial activity.

The pattern repeats one layer up, in the AI answer engines

The same ceiling shows up again where a business owner might least expect it: in the generative answer engines now mediating how customers discover businesses at all. Google announced on 8 October 2025 that it was expanding AI Mode, its conversational search product, to seven additional Indian languages: Bengali, Kannada, Malayalam, Marathi, Tamil, Telugu, and Urdu, building on an English and Hindi rollout announced earlier the same year. That is nine languages total for AI Mode in India, eight of them scheduled, an almost exact echo of WhatsApp's ten-plus-English ceiling, and it leaves the same twelve scheduled languages, Odia, Assamese, Nepali, Sindhi, and the rest, without native AI Mode coverage either.

This is not a coincidence worth treating as a conspiracy; it is what happens when consumer platforms build out language support in roughly the order of speaker count and existing NLP tooling maturity, and both WhatsApp and Google are drawing from the same underlying pool of commercially viable language models and localization budgets. But the effect compounds across the stack. A business in an excluded language is simultaneously harder to message natively on the channel it most depends on and less likely to be represented, cited, or accurately described when a customer asks an AI engine to find or explain it, because the peer-reviewed literature on generative engine optimization already shows that the levers which earn citation inside a generated answer, cited statistics, authoritative sourcing, structured corroboration, are hardest to build in a language the surrounding tooling barely supports.

What an MSME in an uncovered language is actually asked to do

For a business owner whose customers write in Hindi, Tamil, or Bengali, the practical instruction is simple: use the native template tools, because they exist. For a business owner whose customers write in Odia, Assamese, Maithili, or one of the other nine excluded scheduled languages, the advice is different and less comfortable. There is no native WhatsApp Business template path available yet, so the workable options are to operate bilingually with a covered language as the templated layer and the local language as the manual, chat-level layer, or to accept that automation, catalogs, and click-to-WhatsApp ad campaigns will run in a second language until Meta's supported list changes.

Neither option is a failure of the business. It is a property of the infrastructure the business is required to build on, and it is exactly the kind of gap a business cannot see from the inside, because WhatsApp does not surface "your language is not on our supported list" as a warning; it simply does not offer the option in the template builder. The gap is visible only from a comparison like this one, done against the actual, published lists.

Two things are true at once

Two things are true at once, and neither one erases the other. WhatsApp Business remains, by every available measure, the most consequential digital channel for Indian MSMEs, and Meta has invested real, documented effort in the ten scheduled languages it does support, including a dedicated tier-2 and tier-3 outreach program and low-cost message pricing announced through 2024. That investment is genuine, and it reaches most of India's population by speaker count.

It is equally true that twelve of the Constitution's 22 scheduled languages, representing tens of millions of speakers and a meaningful share of India's formal MSME base, have no native path into the channel's automated, templated tools, and that the same twelve are largely absent from the newest generative-answer surfaces as well. Neither Meta nor Google has published a stated roadmap or timeline for closing this specific gap, so the framing here is descriptive rather than predictive: this is where the coverage lines sit today, mapped against the Eighth Schedule as it stands, and a business operating in one of the twelve excluded languages should plan around that reality rather than assume it will be resolved on any particular schedule.