Pick an audience. Pick a channel. Send. Pick a channel

The Wednesday afternoon broadcast that ruined the budget

It is a Wednesday in late October at a CBSE school in Pune. The Principal walks into the office at 3:15 p.m. with a one-line decision: parent-teacher meetings are this Saturday, classes 6 to 10, send a WhatsApp tonight. The office assistant opens the SMS portal her vendor gave her three years ago, types a 220-character message, and hits Send to 'all parents'. Two hours later the message lands with 1,847 parents — including 412 parents of Class 1 to 5 students who are not invited, 38 parents whose children left the school last year and whose contacts the cleanup batch never reached, and 19 parents in default whose contracts technically prohibit non-essential broadcasts. The bill at the end of the month is 11,000 rupees more than the principal expected, the wrong-audience parents are politely confused, and the school does not find out about the 38 ex-parents until someone screenshots one of the messages back to the admissions head.

This is what happens when a school's broadcast tool is just a text box and a Send button. Schools that have lived through one bad blast like this stop running broadcasts altogether — a worse outcome, because the school then loses the only legitimate way to send a non-routine message to parents en masse. Diwali greetings stop going out. Exam schedules are pinned on a notice board nobody reads. The next PTM has 30% attendance because half the parents never knew.

Inkwelly's Broadcast Composer fixes the underlying tool, not the workflow around it. The audience filter already knows the school's roster, its current fee status, its class structure, its enrollment state. The composer reports back, before anything is sent, that 247 parents will get this message, 8 will not, and 3 have no phone number on file. The Principal sees the breakdown. The office assistant hits Send. The wrong-class parents do not get the message. The school does not get a screenshot from an ex-parent two days later. The October bill is correct.

How the composer actually flows

The Broadcast Composer is opened from the Messages section in the Communications module. It is a four-step dialog — audience, message, channels, send — each step visible on the same screen, so the office never has to navigate forward and back.

First, audience. The filter knows the school. The office picks combinations of class, section, parent vs student, class teacher group, current fee status (paid, overdue, in default), attendance trend (low attendance flag) and saved audiences. Each click of a chip narrows the recipient list live; the count in the corner updates in real time. There is no SQL, no rule builder, no 'segment definition' page — just clickable filters that read like the school org chart they came from.

Second, message. The office picks a template from a dropdown (Diwali greeting, PTM reminder, school closure, fee reminder, custom) or writes a free-form message in the text area. Templates have variables — student name, parent name, class, date — that auto-fill per recipient. Free-form messages are previewed side-by-side in English and Hindi so the office sees exactly what a Hindi-medium parent will read. The preview updates as you type.

Third, channels. WhatsApp, SMS, Email, Push — tick whichever combination this broadcast needs. Inkwelly enforces what the channel allows — SMS over the DLT-registered template, WhatsApp under a Meta-approved utility or marketing template, email free-form. A promotional broadcast outside the school's allowed marketing window gets a yellow notice with the next available time slot.

Fourth, send. Right before Send is enabled, Inkwelly resolves the audience server-side and shows you the breakdown: '247 parents will receive this on WhatsApp + Push, 8 parents have no WhatsApp number on file (they'll get email only), 3 parents have withdrawn consent for non-essential messages.' The office sees the numbers, hits Send, and the broadcast goes out via the same dispatch engine that runs every automatic alert — same quiet hours, same channel limits, same audit log.

What the office actually sees

“PTM ke pehle har baar tension hota tha ki kahin Class 5 ke parents ko Class 10 ka message na chala jaye. Ab composer me filter laga ke pehle 247 parents dikhata hai — phir Send. Wrong-class broadcast bilkul khatam ho gaya, aur cost bhi tight ho gayi.”

Five real broadcasts schools run with this

1. Diwali greeting on a Sunday morning. The principal of a CBSE school in Indore picks 'all enrolled parents' as the audience, drops in a one-line Diwali template, picks WhatsApp only, previews in Hindi, sees the breakdown (1,247 reached, 28 unreachable), clicks Send at 11 a.m. on the festival day. The composer holds delivery to within the marketing window because Diwali messages are categorised as promotional; everything goes out cleanly between 11 and 11:20 a.m.

2. PTM reminder on Thursday evening. Saturday is the parent-teacher meeting for Class 6 to 10. The office filters to those classes (parent audience, exclude transferred students), picks WhatsApp + SMS + Email, previews in both languages, sees 'WhatsApp will reach 612, SMS will reach 627, Email will reach 419, total unique parents 631.' Click Send. The next morning, the principal stops getting WhatsApp queries from confused parents — they already have the date.

3. Exam schedule update at 8 p.m. The chemistry pre-board paper has been shifted by a day. The exam coordinator picks 'Class 12 only', writes a tight 80-character SMS-friendly message, hits Send. The composer holds nothing because exam-schedule updates are utility messages — they bypass quiet hours and the marketing window. 87 parents and 87 students each get the message. The morning of the exam, nobody shows up on the wrong day.

4. Transport route change for bus 4. The bus 4 route has been re-drawn because of monsoon waterlogging. The transport coordinator picks the saved audience 'transport bus 4 parents', writes the new stop sequence, attaches a route-map image, sends WhatsApp + Push. 38 parents get the new route within 2 minutes. The next morning's pickup runs cleanly.

5. Class teacher reaches out to her six. A Class 8 teacher noticed six students struggling in maths. She opens the composer, switches to individual selection, types the six names, picks 'parent + student', WhatsApp only, writes a warm note about an extra session next Saturday, hits Send. 6 + 6 messages go out. The audit log records every send for the principal's monthly review. No mass blast, no class-wide embarrassment.

See the Broadcast Composer with your school's data

A 20-minute walkthrough on your real student roster. We build a PTM audience, preview in Hindi, show the recipient breakdown, and run a test send to your phone — end to end.

Limits, safety and the small print

The composer is a manual-send tool, not a marketing automation platform. There are no drip campaigns, no behavioural triggers, no A/B tests. We have kept it deliberately simple because the schools we sell to want a one-shot broadcast that just works — not a marketing playbook to learn. If you need an automated trigger (fee paid, attendance absent, marksheet published), that's the automatic alerts screen, not the composer. We will not bundle marketing-automation features here even when prospects ask; the moment the composer becomes 'powerful', it stops being usable by the office assistant who actually runs the school.

The maximum audience size for a single broadcast is currently the entire school roster — there is no artificial cap, but very large schools (5,000+ parents) will see the message dispatch over several minutes to respect provider rate limits. The composer shows the estimated dispatch duration in the pre-send breakdown so the office knows what to expect. If the school needs to send the same message to a multi-school group (a chain or a state-board federation), that is run from the org-admin console, not the school composer; the school composer scope is strictly the single school it lives in.

Finally, the composer is for messages, not phone calls. If a parent absolutely needs to be reached — a missing child, a medical emergency — the right tool is a phone call from the class teacher, not a WhatsApp broadcast. The composer makes mass communication clean and auditable; it does not solve urgency. The two best office workflows we have seen are 'broadcast the routine, call the urgent' and 'broadcast the audience, call the outliers'. Both treat the composer as a starting point, not the entire parent-communication strategy.