See every rupee spent on a parent message. every rupee

How most Indian schools find out what they spent on parent messages last month

The school's accountant opens his email on the 3rd of the month. Three invoices have arrived overnight — one from the SMS vendor for ₹91,400 (24,200 messages), one from the WhatsApp solution provider for ₹83,000 (no message count, just an opaque line item), one from the email-marketing tool for ₹4,200 (no breakdown at all). The accountant has no idea which event drove the spike. Was it the result-day batch? The Diwali greeting? The fee-deadline-week reminders? The reception's misconfigured absence alert that fired five times per student per day for a week before anyone noticed? Three vendors, three invoices, three different formats, and the accountant has to reconcile all of it manually before Friday's board meeting.

The cost compounds quietly. Without a per-event spend breakdown, the school cannot tell which alerts are paying for themselves and which are pure noise. Without a per-recipient breakdown, the school cannot tell which 20 parents are receiving 80% of the SMS (almost always fee defaulters, sometimes a signal of a misconfigured alert hitting the same family eleven times an hour). Without a per-language breakdown, the school cannot capacity-plan for Hindi-medium expansion. Without a monthly cap, the school finds out it has overshot the budget only when the invoice arrives — four weeks after the spend was incurred and three weeks too late to do anything about it.

Inkwelly's usage and cost dashboard is the screen the accountant opens on the first of every month and never closes till the 5th. Live spend, by channel, by category, by language, by template, by recipient. A daily trend chart that shows the result-day spike and the fee-deadline spike. A monthly cap with a traffic-light gauge. And a no-margin rule that the founder repeats out loud to every school during demo: the cost the school sees on the dashboard is the cost Meta and the SMS vendor actually charge. Inkwelly does not add a per-message markup on top.

How the dashboard actually works

Every message Inkwelly sends — to a parent, a student or a staff member — carries the rate the vendor charged for it. WhatsApp conversations are billed by Meta in transactional, promotional, authentication and service categories at different per-conversation rates (typically around ₹0.30 for transactional, ₹0.80 for promotional in India). SMS is billed by your DLT vendor at typical rates of ₹0.15–0.20 per transactional SMS and ₹0.20–0.25 per promotional SMS. Email is billed by your email provider, usually around ₹0.01 per message at school volumes. Push notifications via the Inkwelly parent app cost zero.

The dashboard aggregates these per-message costs across three dimensions you can pivot freely. By channel — see exactly how much you spent on WhatsApp, SMS, Email and Push this month, with both the rupee total and the message count. By category — see transactional vs promotional vs OTP login codes separately, useful for board reviews and for spotting if promotional spend is creeping above your guideline. By language — see English vs Hindi vs Tamil vs others, useful when a new region opens up and you need to plan for additional Hindi-medium message volume.

The screen updates within minutes of a message being sent — not at the end of the day, not in next month's invoice. If a misconfigured alert starts firing at 10:30 a.m., the spike shows on the dashboard at 10:31 a.m., the daily cap kicks in by 10:35 a.m., and the principal sees the alert before lunch. The dashboard's data window is the calendar month by default, with last-month, last-week and today comparisons one click away. Year-end exports for the board are a single CSV download — itemised by month, by channel, by category.

What it looks like in the office

“Pehle mahine ke 3rd ko teen invoices aate the SMS, WhatsApp aur email vendors se. Accountant ko week bhar reconcile karna padta tha. Ab Inkwelly ka dashboard 1st ko hi dikha deta hai — channel wise, category wise, language wise. Principal aur board ko 5 minute me number mil jaate hain. No vendor lock-in, no per-message markup, no surprise.”

When schools actually use the dashboard

1. The 1st-of-the-month board review. The Principal opens the dashboard on the 1st, screenshots the channel and category breakdowns, and brings them to the management committee meeting at 11 a.m. on the 2nd. Three years ago this review took a week and ended in arguments about which vendor's invoice was right. Today it takes five minutes and the board members can drill into any number themselves.

2. The fee-deadline-week spike. The dashboard's daily trend chart shows a 2.4x spike on the three days around the school's fee deadline. The accountant flags it for the next board review — not as a problem (the school recovered ₹18 lakh of fees that week from 240 defaulters) but as evidence that the fee-reminder template is doing its job. The cost: ₹12,400 in extra SMS sends. The recovered fees: ₹18,00,000. The ROI is obvious.

3. The Hindi-medium expansion planning. A school adding a new branch in a Hindi-medium town pulls last quarter's language-breakdown chart from the dashboard. It shows 38% of messages went out in Hindi, with strong Hindi template performance on fee receipts and weak Hindi performance on examination-related templates (Hindi parents call the office more often after results). The school commissions Hindi-language Examination templates before the new branch opens, instead of after the parents start complaining.

4. The misconfigured alert at 10:30 a.m. A junior office assistant turns on an SMS alert on every attendance event for every student. By 10:30 a.m. the daily-trend graph spikes to 3.2x normal. By 10:35 a.m. the per-channel daily cap kicks in and pauses SMS. By 10:40 a.m. the Principal sees the dashboard alert. By 11:00 a.m. the configuration is fixed. Cost of the mistake: ₹4,800. Cost without the dashboard: maybe a full month of credit before anyone noticed.

5. The board's year-end compliance review. The school's annual board audit needs evidence of inclusive parent communication, transparent vendor billing and DPDP-Act-compliant data handling. The Principal exports a single CSV from the dashboard — every message itemised by month, channel, category, language, with vendor rates included — and submits it as the communication audit. The auditor's questions are answered before they are asked.

See the dashboard on a real school's data

Twenty-minute walkthrough on a school's actual last month spend. Bring your worst billing-surprise story. We will show exactly how the dashboard would have caught it. No sales pitch.

Limits, safety and the small print

The dashboard's numbers are as accurate as the rates your vendors publish. Inkwelly captures WhatsApp conversation costs at the conversation rates Meta charges your business account; SMS at the rates your DLT-approved vendor (MSG91, Fast2SMS or another) bills you; Email at your email provider's rate. If your vendor rates change mid-month — Meta updated India conversation pricing in 2024, and is expected to revise again in late 2026 — the dashboard reflects the new rate from the moment it takes effect, and the year-on-year comparison is annotated so the change is visible.

The dashboard does not bill the school. It is a reporting and audit surface; the actual money flows to Meta, MSG91, Fast2SMS or your email provider on the rate they invoice you for. Inkwelly's subscription is a flat annual fee that covers the platform; per-message costs sit on top and are passed through unchanged. This is the no-margin rule the founder repeats during every demo and means the school is never locked into Inkwelly for the per-message economics — if you change WhatsApp solution providers or SMS vendors, the dashboard plugs into the new rates and the cost picture continues seamlessly.

For a school group operating multiple branches, the dashboard supports a group-level rollup with per-branch filters — the head office sees consolidated spend across all branches; each branch principal sees only their own. The role-based-access permissions (Identity & Access Management) decide who can see what — a typical setup gives the head accountant full cross-branch view, the branch accountant a single-branch view, and the principal a read-only summary of their branch.

Finally, the dashboard's job is to show the truth, not to celebrate it. A month when promotional spend creeps to 22% of total is still a month when promotional spend was 22% of total — the dashboard flags it, but it does not stop the school from running that strategy if the school believes it is right. The discipline of 'should we send this' is still the principal's call. The dashboard's discipline is 'we will show you exactly what you sent, exactly what it cost, and exactly who got it'. Two different jobs, both important, neither replaceable by the other.