Prove every message reached its parent. reached its parent
Every message a school sends — by channel, by template, by recipient, by event — with sent, delivered and opened marks on one screen. Filter by class, search by parent, export for any complaint inquiry. The principal stops being asked "did this go out?" in board meetings, the office stops digging through WhatsApp group screenshots, and year-end audit becomes a single export. Built for the way Indian school complaints actually need to be answered.
How most Indian schools answer "did this message reach the parent?"
Mrs. Pandey calls the school office on a Friday afternoon. "You never sent the fee receipt for Saturday's payment. Now my husband thinks I lied to him about paying." The principal is in a board meeting. The accountant is on lunch break. The office assistant who actually sent the WhatsApp message a week ago is now busy with the admissions queue. The school's answer is a 20-minute hunt through WhatsApp group screenshots, an SMS panel login that has been forgotten, and finally a phone call back at 6 p.m. saying "madam, we definitely sent it, we don't know why you didn't receive it." The parent does not believe the school. The parent never quite trusts the office again.
The cost compounds across the school. The principal is asked at every management committee meeting "did the fee reminder go out?" and the answer is always "yes I think so". The accountant cannot reconcile last term's SMS bill because three different vendors each show different counts and there is no single source of truth. The board asks for proof of parent communication during the CBSE renewal audit and the school produces a printed Excel that says "sent 12,847 SMS in 2025" with no breakdown by template, no delivery confirmation, no read marks, no failed-reason analysis. A parent litigates over an attendance dispute and asks the court for evidence that the absence notification was actually sent on the date claimed. The school cannot produce it. The case is decided against the school.
The deepest cost is invisible. Every week, a small number of parents do not receive a message that the school did send — because the number was wrong, the parent had blocked the school, the SMS credits ran out at 4 p.m., or the message was held in quiet hours and quietly dropped. The school never knows. The parent never knows. Slowly, message after silent failure, the parents' confidence in the school erodes. By the third or fourth missed message, the parent has stopped expecting the school to communicate at all. By the time the school discovers the failure, it has already lost the parent's trust. Inkwelly's Message Delivery Audit Trail is the screen that ends this entire pattern — the principal opens one log, filters by recipient, and sees every message ever sent, with sent, delivered, opened and failed marks. Trust replaces guesswork.
How the message log actually works
Every message Inkwelly sends — from any of the four channels the school has connected — lands in one append-only log the moment it is queued. The row carries the recipient's name, the student's name and class section, the template that was used, the language the message was rendered in, the channel it went out on, the exact second it was sent, the exact second it was delivered (from the channel's own delivery proof), the exact second it was opened (for WhatsApp — the green-tick read mark), and the reason for failure if it did not get through. Nothing is computed later; every timestamp is captured from the channel itself, the moment it happens.
When Mrs. Pandey calls about the fee receipt, the office opens the log, types her phone number or her child's name into the search box, and the screen filters down to every message the school has ever sent her. The fee receipt for Saturday's UPI payment is right there — Saturday 11:47 a.m., WhatsApp, sent, delivered, opened at 11:52 a.m. The office shares the screenshot. The conversation ends. Mrs. Pandey realises she had archived the school's WhatsApp number on her phone. The school's reputation is intact. The whole interaction took 90 seconds.
The log is not a black-box report; it is a working screen. Filter by channel (show me only WhatsApp), by template (show me every absence alert), by recipient (show me every message ever sent to this parent), by event (show me everything triggered by a fee payment last weekend), by date range (this month, this term, last academic year). Search by parent phone number, parent name, student name, or any keyword. Export the filtered result as a CSV for the accountant's monthly reconciliation or the principal's board pack. Open any row to see the full message body, the variables that were filled in, and the timestamped status pipeline as it actually happened.
What's covered in the message log
- Every WhatsApp, SMS and email the school has ever sent — from every channel, on every event, by every staff member
- Sent, delivered, opened and failed marks per message — captured from the channel itself, not estimated
- WhatsApp opened timestamp (the green-tick read mark) — proof the parent actually saw the message
- Failed messages with the reason in plain language — wrong number, parent unsubscribed, outside promotional hours, SMS credits low
- Filter by channel — only WhatsApp, only SMS, only email, or any combination
- Filter by template — every fee-paid receipt, every absence alert, every marksheet notification, side by side
- Filter by recipient — every message ever sent to a specific parent, by phone number or by student name
- Filter by event — every message triggered by a fee payment, an absence, a marksheet publication
- Filter by date range — this week, this month, this term, last academic year
- Search by parent phone number, parent name, student name, or keyword in the message body
- Export any filtered view as CSV — ready for board packs, audit submissions or accountant reconciliation
- Open any row to see the full message body, the rendered variables, and the timestamped delivery path
- Per-school retention — message log preserved for the period the school configures, well past TRAI and Meta minimums
- Year-end audit export — every message of the academic year, by channel and category, in one file
See the log in action
Sent, delivered, opened — every mark, captured from the channel
The sent mark is the moment Inkwelly handed the message to the channel — WhatsApp's API, the DLT-approved SMS vendor's gateway, the school's email server. The delivered mark is the moment the channel confirmed the recipient's phone or inbox accepted the message. The opened mark is the moment the parent's phone showed it as read — for WhatsApp, this is the famous double-tick-turned-blue moment, and Inkwelly captures the exact second it happened. The failed mark, if it appears, carries the channel's own reason for the failure.
Every timestamp is real — the channel itself reports it back to Inkwelly the moment it happens. Nothing is computed, estimated or smoothed. When the principal looks at "Mrs. Pandey · fee receipt · 11:47:04 sent · 11:47:09 delivered · 11:52:31 opened", every one of those four numbers came from the channel itself. The log is forensic-grade proof, not a marketing summary.
Failed messages — the reason in plain English
The most important rows in the message log are the ones that did not get through. Inkwelly does not show them as a red error code. Every failed row carries the reason in a sentence a school office can act on — "Phone number not on WhatsApp", "Parent unsubscribed from promotional messages on 14 March 2026", "Outside promotional window (sent at 9:14 p.m., parent's window closes at 9 p.m.)", "SMS sender ID daily cap exceeded; queued for tomorrow", "Email bounced — mailbox not found".
Every reason has an action attached. "Phone number not on WhatsApp" surfaces the parent's Student Information profile with the phone-number field highlighted, so the office assistant can update it in 30 seconds. "Email bounced" asks if the office wants to retry with an alternate email on the same profile. "SMS daily cap exceeded" opens the usage screen with the cap and the next reset time visible. Failed is not a dead-end; it is the start of a workflow that ends in the parent actually receiving the message.
Filter by recipient — every message this parent ever received
The single most-used filter in the entire workspace is "every message ever sent to this parent". When Mrs. Pandey calls, the office searches her phone number or her child's name and the log filters down to every message Inkwelly has sent to her household across every channel — fee receipts going back six terms, every daily absence alert, every marksheet notification, every parent-teacher-meeting reminder, every promotional alumni-event invitation. The office sees the full conversation history with the parent, by channel, in seconds.
For a parent complaint, this filter resolves 90% of "you never sent it" disputes in under 90 seconds. For a class-teacher review, the same filter shows whether the parent has been receiving and reading the school's communication — a parent with a long string of delivered-but-never-opened WhatsApp messages is a parent who has muted the school's number and needs a phone call, not another broadcast.
Year-end audit, in one export
CBSE renewal, board affiliation reviews, the school's annual statutory audit, the management committee's annual report, the parent association's quarterly transparency request — all of these ask the school to prove its parent communication is real, dated and channel-attributed. Without a message log, the school produces an estimate. With Inkwelly, the school clicks Export on the audit screen, picks the date range (1 April 2025 to 31 March 2026), picks the columns (date, channel, template, recipient, sent, delivered, opened), and downloads a single CSV.
The export carries every message, every delivery proof, every failed reason — not summarised, not sampled, every row. The board sees actual data. The auditor sees actual proof. The school stops being asked "how do we know?" because the answer is "open this file." The same export is regenerated whenever the board asks for it; nothing is locked away in a vendor's reporting tool the school cannot access.
“Pehle parent jab complaint karta tha ki message nahi mila, hum 20 minute screenshots dhundhte the WhatsApp groups mein. Ab Inkwelly mein parent ka phone number type karte hain, har message aa jata hai — sent, delivered, opened, sab dikhta hai. Complaint 30 second mein resolve.”
Real-world use cases — when the log saves the day
1. Parent calls about a fee receipt that never arrived. Office searches phone number, message is right there — sent, delivered, opened. Conversation ends in 90 seconds. The office now has the conversation history to investigate why the parent claims it did not arrive (often the parent had muted the school's number).
2. Attendance dispute escalates to a legal notice. The parent's lawyer asks for evidence that the daily absence alert was actually sent on 14 February 2026. The school exports the audit log filtered to that parent, that template, that date — the sent and delivered timestamps from WhatsApp's own delivery proof are admissible evidence. The matter is resolved without going to court.
3. CBSE renewal asks for parent-communication evidence. The renewal committee asks the school to demonstrate that fee receipts, attendance alerts and result notifications are sent reliably. The school exports the full academic year, by channel and category. The committee sees actual data and the renewal goes through without follow-up queries.
4. Accountant reconciles last quarter's SMS bill. The DLT-approved SMS vendor's invoice shows 12,400 SMS sent. The school's message log shows 12,378 SMS sent and delivered. The accountant finds the 22-message discrepancy in three minutes (vendor counted retries that Inkwelly recorded as one logical send) and disputes it with the vendor. The bill is corrected before payment.
5. Principal investigates why parent feedback dropped. The principal notices the parent satisfaction survey scores dropped in Class 6. She opens the log, filters by Class 6 parents, sees that delivered-but-not-opened rates are at 40% for that section's WhatsApp broadcasts — too many parents have muted the school's number. The principal switches Class 6 attendance alerts to SMS, the open-rate problem is solved within a week.
Common operations the office runs from the log
- Search by parent phone number to resolve a complaint in 90 seconds
- Filter by template to count how many fee receipts were sent last term
- Filter by event to see every message triggered by a single fee payment
- Filter by channel to compare WhatsApp opened-rates against SMS delivered-rates
- Filter by language to check whether Hindi messages are landing as well as English
- Filter by failed-only to see which parents are systematically not receiving messages
- Filter by date range to produce a monthly board report in one click
- Filter by class section to investigate a class-specific complaint pattern
- Open any row to see the full message body and the variables that were filled in
- Retry a failed message from the same row — fix the phone number first, then retry
- Export the filtered view as CSV for the accountant or the board pack
- Schedule a recurring export — monthly summary delivered to the principal's email
See the audit trail on a real school dataset
Twenty minutes. A real school's six months of message log. Bring your hardest complaint scenario — we will show how Inkwelly resolves it from one screen. No sales pitch.
Limits, safety and small print
The message log covers every message Inkwelly itself sent on behalf of the school. Messages a staff member sent from their personal WhatsApp account (the old drawer-phone pattern) cannot be captured by Inkwelly because they never touched the school's WhatsApp Business number — the audit log captures only the school's official communication, which is exactly what board reviews and legal proceedings care about. The path forward is to move every school message through the school's WhatsApp Business number, the school's DLT-registered SMS sender, and the school's verified email domain.
The opened timestamp is captured only when the channel itself reports it back. For WhatsApp this is the green-tick read mark, which is reliable and admissible. For SMS, mobile operators do not return a read receipt, so the log shows only sent and delivered — SMS open-rate is not measurable on any platform in India. For email, the log captures bounces and opt-outs but does not insert tracking pixels (which Indian parents increasingly block); explicit open-rate is therefore not available for email. Sent and delivered cover the legal-proof requirement; opened is a nice-to-have where the channel supports it.
Message retention follows TRAI's DLT framework for SMS, Meta's WhatsApp policy for WhatsApp, and the school's own configured period for email and push. The default active-log retention is two academic years, with an optional five-year archive for schools with board-affiliation or legal-evidence needs. The log is read-only — staff members cannot delete rows, and even super-admin deletion (when the school chooses to purge after the retention window) leaves an audit row showing what was purged, when, and by whom. All log content is stored on servers in Mumbai. The export feature respects the school's role-based access — a class teacher can export only her sections' communication, the accountant can export only fee-related templates, the principal can export everything.
Belongs to
1 moduleFrequently asked
8 questionsCan we use the audit log as evidence in a parent dispute or legal case?
Yes. Each row carries the channel's own delivery proof — for WhatsApp, the sent, delivered and opened timestamps come from Meta's own WhatsApp Business API and are admissible as electronic records under Indian evidence law. For SMS, the sent and delivered timestamps come from the DLT-approved vendor. The export carries the original timestamps, the recipient phone number, the message body and the variables that were filled in. Schools have used Inkwelly exports successfully in fee disputes and attendance-related cases.
Why does the log not show an opened timestamp for SMS messages?
Mobile operators in India do not return a read receipt for SMS — the protocol does not support it. No school ERP can show SMS open-rate honestly, on any platform. Inkwelly shows sent and delivered for SMS, which is what TRAI's DLT framework actually measures, and notes the absence of opened explicitly so the school is never misled by a fake number.
Inkwelly me pichla saal ka message log kaise dekhein?
पिछले academic year का log देखने के लिए Date Range filter खोलें, *Custom* चुनें, 1 April से 31 March की dates डालें। पूरे academic year का log एक screen पर दिख जाएगा — channel के hisaab से, template के hisaab से, parent के hisaab से। CSV export भी एक click में ho jata hai। Default retention 2 academic years की है, अगर 5-year archive चाहिए तो enable किया जा सकता है।
What happens when a parent says they never got a message but our log shows it was delivered?
Open the message detail. If the WhatsApp message shows opened at a specific timestamp, the parent saw it — they may have archived the chat or deleted it, but the green-tick read mark is conclusive. If WhatsApp shows delivered but never opened, the message reached the parent's phone but they did not open it (often because they muted the school's number); the office can call the parent and suggest unmuting. If the message is in the failed list, the row explains why — wrong number, parent unsubscribed, outside the promotional window — and the office can fix the underlying issue.
Kya school office assistant message log se kuch delete kar sakti hai?
नहीं। Message log read-only है — कोई staff member individual rows delete नहीं kar sakta। Yeh isliye hai taki koi embarrassing failed message ya complaint-worthy message chhupa na sake। Super-admin retention period (default 2 years, optional 5 years archive) khatam hone par bulk purge kar sakta hai, lekin uska bhi audit trail bachta hai — kis ne, kab, kitne records purge kiye, sab log mein dikhta hai.
Can the accountant export only fee-related messages, not the whole log?
Yes. The Template filter has a category facet — select Fee Receipt, Fee Reminder, Payment Link Sent, Fine Added, Payment-Link Reminder — and the log filters down to only fee-related messages. The CSV export carries only the filtered rows. The same approach works for the principal (filter by every event), for the class teacher (filter by her section), and for the accountant's monthly reconciliation.
Does the log cover messages sent by the old broadcast-list WhatsApp drawer phone?
No, by definition. The audit log captures only messages that flowed through Inkwelly — the school's WhatsApp Business number, the school's DLT-registered SMS sender, the school's verified email domain. Messages a staff member sent from their personal WhatsApp account (the drawer-phone pattern) were never seen by Inkwelly and cannot be reconstructed. Once a school is fully migrated to Inkwelly, every official school message lives in the log.
Is the message body retained, or only the metadata?
Both — the full message body and the metadata (timestamps, recipient, channel, template, variables filled in). For email, attachments are referenced by secure download link rather than re-stored, but the link is preserved for the retention period. The body retention follows the school's configured period (default two academic years for the active log, optional five years for the archive). This is essential for legal evidence — a timestamp alone is insufficient; the actual words the school sent are what disputes hinge on.
You might also like
2 readsSee Inkwelly on your school
30-minute demo. We open your current ERP with you and load your data into Inkwelly on the call. Dated go-live plan by the end of it.