Write once. Send in both languages. English for one parent. Hindi for the next. From the same template.

How Indian schools fake bilingual today

It is the third week of admission season in a Bahraich state-board school. The office assistant has just finished sending the fee-payment reminder to 314 parents. She did it in two passes. First, the English version was pasted into the WhatsApp broadcast list of class 6 to 12 — Hindi-medium parents and English-medium parents jumbled together, because the office never separated them. Then, because half the angry callbacks last month came from parents who could not read English, she went back, opened the same broadcast list, and sent a hand-typed Hindi version of the same reminder. Two hours of work. Two pre-Diwali coffee breaks lost. And still, twenty-two parents missed the message because the Hindi version landed seven hours after the English one.

This is what 'bilingual' looks like in most Indian schools today. The principal of an ICSE school in Pune calls it "the translation tax". She pays it on fee receipts, attendance alerts, admit cards and result-day messages. She pays it on every single template her office maintains. She pays it twice over on result day, when the English-medium parents want clean professional English and the Hindi-medium parents want a sentence they can read aloud to their husbands. She has a salaried translator on the office bench whose only real job in March is to retype Hindi versions of receipt templates the office should never have had to retype.

Inkwelly removes the translation tax entirely. Every ready-to-use template ships in both English and Hindi from the day the school goes live. Each parent's preferred language — set in the parent app on the very first sign-in — is honoured automatically on every channel. The WhatsApp fee receipt goes to the Hindi-medium parent in Hindi, to the English-medium parent in English, fired from the same template the office edited once. The translation tax is paid by Inkwelly, not by the school office.

How language picking actually works

Every parent who logs into the Inkwelly parent app picks a preferred language on the very first sign-in. That choice is stored against her user record. From that moment, every alert the school fires — fee receipt, absence alert, homework, marksheet, admit card, exam result — looks up her preference and renders the template in that language before the message leaves the building. The school office never has to remember which parent reads what. The system does the remembering.

The template author writes the English version once and the Hindi version once, side by side, in the same editor. The variables (student's name, amount, date, receipt link) are the same in both. The school is editing one document with two language tabs, not two documents that drift apart. When the principal wants to tweak a holiday-greeting message, she updates both tabs in the same session, sees the preview in both languages, and saves once. Inkwelly compiles the right version per parent at send time — the office never picks 'send English' or 'send Hindi' from a dropdown.

If a parent has not set a language preference yet (early-onboarding parents, or grandparents using a temporary login), Inkwelly picks the parent's preferred language first, then the school's default, then English. The school decides its own default in the Communications settings the day it goes live — a Bahraich state-board school picks Hindi as default; a Pune international school picks English; a Bangalore CBSE school often picks English with Hindi available per parent. The school does not see a fallback enum or a priority list — it sees one dropdown that says "School default".

What bilingual looks like in the editor and on the parent's phone

“Pehle Hindi receipt ke liye office assistant ko alag se type karna padta tha. Ab same template hai — office English likhta hai, Hindi version Inkwelly khud render karke parent ke phone pe deta hai. Translation ka kharcha bachta hai aur Hindi-medium parents khush rehte hain.”

Real situations bilingual templates solve

1. Result day at a Lucknow CBSE school with 1,800 students. Half the parents are English-medium IT professionals; half are Hindi-medium grandparents who speak the language at home. The office fires the marksheet-published template once. Every parent gets the result on her preferred channel in her preferred language. The English-medium father reads it on his commute to work; the grandmother reads it aloud to her daughter-in-law over chai. Same school, same minute, same template — two languages, zero double authoring.

2. A Bahraich state-board school where almost every parent reads Hindi. The principal flips the school default to Hindi during onboarding. Every alert from that day onwards goes in Hindi to parents who have not set a preference — which is most of them. The handful of English-preferring parents (the doctor's family, the bank-officer's family) tick English in the parent app once, and from that moment their receipts arrive in English while the rest of the school continues in Hindi. The principal never picks a language per send.

3. A Pune ICSE school with a Maharashtra State Board sister branch. The ICSE branch defaults to English; the State Board branch defaults to Marathi (when Marathi ships) or Hindi today. Both branches use the same Inkwelly account, the same fee-payment-received template, the same authoring screen — the language each parent gets depends on her sign-in preference, not the branch. A parent with kids in both branches gets the same language across both, picked once.

4. A Tier-3 town school where the office assistant edits the holiday-greeting message for Diwali. She opens the template, types the English version in the English tab, types a Devanagari-grammar Hindi version ("Diwali की हार्दिक शुभकामनाएँ — school 21 October से 26 October तक बंद रहेगा।") in the Hindi tab, hits Save, fires the broadcast. Both versions go out at the same moment in the same broadcast. No second pass, no Hindi-only worklist, no afternoon coffee break sacrificed.

5. A school auditor doing the year-end review of communications spend. She filters the usage dashboard by language to see how much of the school's WhatsApp spend went out in Hindi versus English. The number is real, attributable, exportable — evidence for the next inspection that the school is communicating with parents in the language they actually speak.

See bilingual templates working in your school's voice in 20 minutes

Bring three real parents (with their permission) — one English-preferring, one Hindi-preferring, one without a preference yet — and we will fire the same fee-receipt template to all three from one screen. You will see exactly what each parent's phone shows, in the language she expects.

Limits, safety and the small print

Bilingual ships with two languages on day one — English and Hindi — across every ready-to-use template on WhatsApp, SMS, Email and Push. Tamil, Marathi, Bengali, Gujarati, Punjabi, Kannada, Telugu and Malayalam are on the roadmap, in that broad order based on Inkwelly's current school distribution; each will ship after a native-language editor has reviewed every ready-to-use template in that language. The schema is ready today; the gating constraint is editorial quality, not engineering.

WhatsApp and SMS have an additional regulatory layer that affects how new templates light up per language. WhatsApp templates have to be approved by Meta per language — the English version and the Hindi version are two separate approval rows on Meta's side. SMS templates have to carry a TRAI DLT template ID per language — the English version and the Hindi version are two separate DLT submissions. Inkwelly ships every standard template already approved on both languages for the connected provider account; for any school-customised template (see Template Customisation), the school re-submits the modified body for approval, per language. Email and Push do not require external approval and light up the instant the school edits and saves.

Parent-side preference is stored against the parent's user record — the parent app, the website, or the school office can change it at any time; the change applies from the very next send. There is no waiting period and no SMS / WhatsApp re-approval needed when a parent changes her language preference — the template was already approved on both sides in advance. School defaults are configurable per school in the Communications settings. A school can also lock a specific template to one language across all parents (rare, but used by some boards for mandated notices) — in which case the parent's preference is bypassed for that one template and the audit log records the override reason. All language behaviour is auditable; the system never picks silently.