Your child is on the bus. WhatsApp says so. In seconds.

How parents find out today whether their child made it onto the bus

The mother of a Class 2 girl is at her office in Indore by 9 a.m. Her daughter's school day starts at 8:15. The bus picks the girl up at 7:25. Between 7:25 and 9 — every working day — there is no signal whether the girl got on the bus, missed it, was at the wrong stop, or is waiting for the late driver. The daughter does not own a phone. The school's receptionist, called at 8:40, says she will check and call back. She rarely calls back. The mother spends the first hour of her workday with a low-grade worry that does not lift until the school's morning circular goes out at 9:30.

In the school, the office is no better off. The transport in-charge has a paper register — the driver scribbles a tick mark next to each name as the child boards, and hands the sheet to the office at 11. By then it is useful only as historical record. If a parent calls at 7:50 asking whether her daughter got on, the receptionist literally cannot answer. If a child has been absent without notice, no one realises until the class teacher takes attendance at 8:25 — by which time the parent has driven to office assuming everything is fine.

Inkwelly closes this gap. The driver marks each child boarded, absent or no-show with a tap on the Driver app. The mother's parent app pings within seconds: "Your daughter Ananya boarded the school bus at Stop 3 at 7:26." The school office sees the same row appear on the bus attendance screen. The receptionist already knows the answer when the parent rings. The class teacher already knows which children to expect.

How bus attendance actually works in the morning

At 7:25 a.m. the driver pulls up at Stop 3. He has the Inkwelly Driver app open on the phone clipped to his dashboard. The screen shows the five children assigned to Stop 3 — names, photographs, parent contact, blood group, any medical note. He taps each child as they board: green tick for boarded, red cross for absent, amber circle for no-show. He hits Confirm and the bus moves on to Stop 4.

The instant Confirm is tapped, three things happen. The parents of the boarded children get a WhatsApp alert within seconds: "Ananya boarded the school bus at Bazar Atariya at 7:26 a.m. Driver: Ramesh. Bus: UP-32-AB-1234." The parents of any no-show or absent children get a different alert — "Ananya did not board today; please call the school office if this is a mistake." The school office's bus attendance screen updates the row for each child, live, on whichever computer the office staff has it open.

When the bus arrives at school, the in-charge has the day's bus attendance complete — on a single screen, by bus, by route, by stop. The class teacher has the same data flowing into her register. The receptionist knows for any parent call whether the child boarded, where, when, and which bus is bringing them in. Reports for the term — attendance percentage by route, by class, by child — generate themselves at month-end.

What it looks like — from the driver's phone to the parent's WhatsApp

“Pehle kabhi humein pata hi nahi chalta tha kaun bus pe chadha kaun nahi. Class teacher 8:25 par bolti thi ‘Aarav nahi aaya hai’, tab phone karte the. Ab driver tap karta hai aur 30 second mein parent ke WhatsApp pe message chala jaata hai. ‘Aapka bachcha bus mein hai, Stop 3 se 7:26 par chadha.’ Bus ki shikayatein 80 percent kam ho gayi.”

Five real moments this is built for

1. The 7:30 a.m. mother in Indore. Old way: she calls the school at 8:40 to ask whether her daughter got on the bus. The receptionist says she will check and call back. The mother spends the first hour at work distracted. Inkwelly way: at 7:26, she gets a WhatsApp alert — "Ananya boarded at Bazar Atariya. Driver: Ramesh. Bus: UP-32-AB-1234." She closes the phone and starts her day.

2. The forgetful parent. A child slept in. The parent did not inform the office. The driver reaches the stop, taps no-show with reason "missed pickup." The parent's WhatsApp pings within seconds — "Aarav was not at Stop 3 at 7:26. If this is unexpected, please call the school office." The parent looks up, sees the alert, calls the school. The class teacher is told before the morning bell rings. No one is reported missing.

3. The first parent-teacher meeting question. Parent asks: "Is my child taking the bus regularly?" Old way: nobody knows. Inkwelly way: the class teacher pulls up the term's transport attendance for that child — 92 percent in the morning, 87 percent in the drop, no major absences — and the answer is on the screen. Decisions about whether to renew transport for the next year are based on data, not feelings.

4. The substitute driver. Bus 4's regular driver is on leave. A substitute takes over for two days. The Driver app on the substitute's phone shows the same children, the same stop list, the same expected count. He marks attendance the same way. Parents do not notice a change in alerts. The substitute does not miss anyone. The school's transport reliability looks the same on a Tuesday and a Wednesday.

5. The 11:30 a.m. wrongful complaint. A parent calls the office at 11:30 claiming the bus did not stop for his child. The receptionist opens the day's bus attendance, sees the child marked no-show at 7:26, sees the GPS confirms the bus was at the stop for 90 seconds, sees the alert went out at 7:27. The receptionist replies politely with the data. The complaint is closed in two minutes. The parent updates his pickup arrangement.

See the parent app pinging on a real school's morning

Bring your toughest parent question — "how do you tell parents if a child missed the bus?" — and we will show how Inkwelly answers it. 25 minutes, real fleet, real alerts. No sales pitch.

Limits, safety and the small print

Where the alerts come from. Inkwelly uses a verified WhatsApp business channel registered to your school. Parents see your school's name, not a generic number. There are no per-message charges to worry about — messaging is included in your plan up to the limits in your agreement (most schools do not come close).

No-signal stretches. If the bus enters a no-signal patch when the driver taps Confirm, the marks queue locally on the driver's phone. As soon as connectivity returns, the queue flushes — the parents' WhatsApp alerts go out together, the school office screen updates together. Tested in Tier-3 outskirts, hostel-route mountain passes and underpasses.

Parental consent. Bus attendance and the WhatsApp alerts are opt-in at admission. Parents can opt out per channel — some prefer SMS, some prefer in-app push, some prefer both. The alert content stays the same; only the channel changes. Opt-outs are logged for audit.

Privacy. Each parent only ever sees their own child's bus attendance. The class teacher sees only her own class. The transport in-charge and the principal see the whole school. Bus attendance records are kept for the full session and exportable to CSV for board affiliation reviews. After session-end, records become read-only.

Data residency. Bus attendance, parent contacts, child names and the WhatsApp message log live on servers in Mumbai, encrypted at rest, handled the way the DPDP Act 2023 expects. The Inkwelly support team in India can answer compliance questions in writing.

Multi-language. Alerts go out in English or Hindi today, in Latin digits the way the rest of the product works. Tamil, Marathi, Bengali and Kannada are on the road map. Tagalog is not on the road map.

Backup channels. Schools that have a small number of parents without smartphones can opt those into SMS instead of WhatsApp — same data, same content. Aadhaar-linked phone numbers are not required. The DigiLocker integration for parent identity is optional and does not affect alerts.