How to send parent notifications in Hindi in Inkwelly

1. Confirm Hindi variants exist on the templates you care about

In Inkwelly open Communications → Templates. Each row shows the language badges shipped with that template — most carry both EN and HI. Fee Payment Received, Invoice Payment Link Shared, Payment Link Reminder, Receipt Shared, Fine Added, Attendance Marked Absent, Admit Card Issued, Marksheet Published and Homework Assigned all ship with an HI variant on Day 0. If a template you need has only EN, click Customise on that template and add a Hindi body (see [[how-to-customise-a-parent-notification-in-inkwelly]]).

2. (Option A) Make Hindi the school-wide default

For schools where almost every parent reads Hindi, open Communications → Settings → Language and pick हिन्दी (hi) as the school default. Save. Every Inkwelly notification fires the HI body unless an individual parent has explicitly set their preferredLanguage to English on their contact record. Templates without an HI variant fall back to English automatically — so this setting is safe to flip even before customisation is complete.

3. (Option B) Let each parent's language preference decide

For mixed schools where some parents read Hindi and some read English, leave the school default on Auto. Open Students → a student → Parents and edit the parent's preferredLanguage to hi or en. Inkwelly stores the preference on the parent contact, and every event that fires for that student honours the preference. The school-default route is the fallback for any parent who has no preference recorded — so you can change preferences one cohort at a time.

4. Bulk-import preferredLanguage for thousands of parents

For large schools, set the preference in bulk via the existing Student Bulk Import flow. Add a parentPreferredLanguage column to your CSV (values: en, hi, mr, ta, te, kn, bn, gu — ISO-639-1 codes for the languages Inkwelly's templates support). Upload through Students → Import. Inkwelly merges the language preference into each parent contact alongside name and phone. Existing parents get updated; new parents are created with the preference set on the first row.

5. Submit the Hindi WhatsApp variants to Meta

Meta treats every template-language pair as a separate asset — EN approval does not cover HI. On each template you want to dispatch over WhatsApp in Hindi, click Submit to Meta on the HI row. Most schools submit EN first to learn the Meta acceptance pattern, then submit HI as a second pass. The Communications dashboard's Templates & triggers card surfaces every HI variant that is still Not submitted so you can see the queue at a glance.

6. Register the Hindi SMS variants on DLT

DLT also treats every language as a separate template entry. Open each template's SMS tab, copy the HI body word-for-word into your DLT operator portal, register and wait for the 19-digit Hindi template ID, then paste it back into Inkwelly. The SMS variant flips to APPROVED only when that HI-specific DLT ID is in place. Email variants need no provider step — Hindi email dispatches immediately once the HI body is saved.

7. Verify the routing with a test send

Go to Communications → Messages → Send test. Pick a parent contact whose preferredLanguage is HI and trigger a real template send to that parent. Inkwelly resolves the language at dispatch time: if the parent has a preferredLanguage and a matching HI variant exists, the HI body goes out; otherwise it falls through to the school default; otherwise to English. The Messages log records the exact language used on the row so you can spot misrouted parents.