No fee reminders at 11 p.m. Ever. 11 p.m.

Why a parent should never be woken up by your school's ERP

Every Indian principal who has run a parent group on a personal phone knows the feeling. It is 10:47 p.m. on a Tuesday in March. The accountant, working late on the fee-defaulter list, presses Send on a 200-parent reminder broadcast that he forgot to schedule for the morning. Within fifteen minutes, two parents have replied with annoyance, one parent has called the school's emergency number, and one mother has marked the WhatsApp number as spam. By Wednesday morning, the school's WhatsApp Business number is rate-limited for 24 hours and the office cannot send the fee receipts that did need to go out today.

The cost compounds quietly. A late-night promotional message is not just a parent irritation — it is a Meta spam-metric hit that lowers the quality tier of the school's WhatsApp Business account. The school's transactional messages then get throttled the next day. Parents who never received yesterday's legitimate fee receipt assume the school is disorganised. The fee desk gets twelve phone calls before lunch. One unscheduled 11 p.m. broadcast costs the school a week of reputation and three days of staff time.

Inkwelly is engineered to protect the school from itself. Three controls — quiet hours, a promotional window and per-channel daily caps — are first-class settings on every Inkwelly school. They apply by default the day the school goes live. The accountant can press Send at 10:47 p.m. and Inkwelly will quietly hold the message until 7 a.m. the next morning. The parent sleeps. The school's WhatsApp account stays clean. The morning fee receipts go out on time.

How quiet hours and the promotional window actually work

When a message is created — either by an automatic alert from the rest of Inkwelly or by an office assistant pressing Send on a broadcast — the system runs a check before the message ever reaches the WhatsApp, SMS or Email vendor. First, is this a transactional notice, a promotional send, or an OTP login code? OTP login codes always go through, immediately, because regulators define a failure to deliver an OTP as a different kind of problem from a parent-irritation problem. The other two run through the windows.

Quiet hours are checked next. The school configures a window — typically 9 p.m. to 7 a.m. India Standard Time — and picks one of two behaviours. Hold keeps the message in a queue and sends it the moment the window opens at 7 a.m. Drop discards the message silently with a record in the log so the principal can investigate at audit time. Both behaviours are equally good — the school picks based on whether holding a 9:14 p.m. absence alert until 7 a.m. is useful or stale.

The promotional window is the third check, and it applies only to promotional messages — parent-teacher-meeting reminders, alumni-event invitations, scholarship announcements. The school sets a daytime window (typically 10 a.m. to 6 p.m. IST) and Inkwelly will not send promotional content outside it, no matter what the office assistant tries. Transactional notices and OTPs bypass this window — the school can send a fee receipt at 11:43 p.m. and Inkwelly recognises it as transactional and sends it. Same for an OTP login code at 5:30 a.m.

What it looks like in the office

“Pehle accountant sahab 10 baje raat ko fee reminder bhej dete the aur subah mujhe 6 parents ke complaint phone aate the. Ab Inkwelly khud subah 7 baje send karta hai — accountant ne press kar diya raat ko, parents ko subah mila, complaint zero. Boss ne kaha 'finally apna ERP responsible hai'.”

When schools actually use these controls

1. The 10 p.m. accountant. The school's accountant works late on the fee-defaulter list during March's fee-deadline week. He drafts the reminder at 10:30 p.m., presses Send at 10:47 p.m. Inkwelly's quiet-hours hold catches it, queues it, and sends to 312 parents at 7 a.m. the next morning. Parents wake to a clean reminder. The accountant gets to sleep on time. Nobody complains.

2. The Diwali greeting from the marketing committee. The PTA marketing committee writes a Diwali greeting on the Friday evening before the festival. They send it at 9:45 p.m., expecting it to go out immediately. Inkwelly classifies it as promotional, sees it is outside the 10 a.m. – 6 p.m. window, and holds it. At 10 a.m. on Saturday, the greeting fires to all parents. Meta's quality tier stays green. Saturday afternoon's fee receipts go out at full speed.

3. The misconfigured absence alert. A junior office assistant accidentally enables an SMS alert on every attendance event — present, absent, late — for every student. By 10:30 a.m., 18,400 SMS have queued up. Inkwelly's 5,000-SMS daily cap kicks in at 10:35 a.m., pauses the channel and notifies the principal. The principal investigates, fixes the configuration, and the next day's morning alerts (now correctly limited to absences) fit comfortably under the cap.

4. The medical emergency at 11 p.m. A child falls ill on a residential school trip. The teacher needs to message all 42 parents urgently. The teacher marks the broadcast as 'emergency / transactional' inside the composer. Inkwelly recognises the override, bypasses the promotional window, sends the WhatsApps within seconds. The override is logged with the teacher's name and time so the principal sees it on the next morning's audit.

5. The OTP login at 5:30 a.m. A maths teacher logging in from a new phone at 5:30 a.m. to mark the day's attendance receives the OTP login code in 4 seconds. Quiet hours did not apply. The daily SMS cap did not apply. The teacher logged in, marked attendance and the daily-absence alerts to parents went out as scheduled. No outage, no surprise, no human in the loop.

See the controls on a real school's data

Twenty-minute walkthrough. Bring your worst late-night-broadcast story. We will show how each one is caught, held or dropped, end to end. No sales pitch.

Limits, safety and the small print

Quiet hours, promotional windows and per-channel caps are protections, not absolutes. There are edge cases every school principal should understand. The windows are always evaluated in Asia/Kolkata time, regardless of where the cloud server is — Inkwelly does not surprise a school by treating the windows as UTC. Daylight-savings does not apply in India, so the windows are stable year-round. If the school operates across multiple branches with different state time-zones (rare but real for cross-border school groups), each branch's window is evaluated in its configured time-zone.

The controls do not extend to messages the school sends from outside Inkwelly. If a teacher sends a WhatsApp from her personal phone at 11 p.m., Inkwelly cannot stop it — but Inkwelly does not record it either, and the principal cannot audit it. This is the point of moving school communication into the workspace: every message that flows through Inkwelly is windowed, logged and budgeted. Messages outside the workspace are outside the school's protection.

In an emergency — medical, safety, school-closure — the school can override the promotional window at the broadcast level. The override is recorded with the user, the time, the recipient count and the reason. Quiet hours can also be overridden in genuine emergencies, but the override requires a Principal-level role and is highlighted on the next morning's audit so the school's senior team sees it. OTP login codes are the only category that bypasses everything by default, and this is hard-coded — a school cannot accidentally lock its parents out by enabling quiet hours on OTPs.

Finally, the controls do not replace good judgement. A school that sends 18 broadcasts a day and complains about the daily cap is not being protected by Inkwelly — it is being warned by Inkwelly. The settings exist to prevent disaster, not to tune a high-volume marketing machine. If your school is genuinely a high-volume communication operation, the caps and windows are a foundation; the discipline of when to send what is still the principal's call.