2026-08-13 · ActiKidz Team

You posted it in the WeChat group. Parents still say they never saw it.

A Tuesday night you've probably lived through

Wednesday afternoon's room got taken, so you move the class to Thursday, same time.

At eight in the evening you post in the class group and tag everyone. Five parents reply "got it." You relax.

Wednesday afternoon, two kids show up at the door anyway. A parent calls you from outside, already a little annoyed: "I'm in that group all the time. I never saw anything about a time change."

You dig up the message, screenshot it, send it over. The message is right there, timestamp and all.

And the screenshot is worth nothing. It proves you sent something. It doesn't prove anyone received it. Meanwhile the wasted trip actually happened, and no screenshot undoes that.

"Sent" and "seen" are separated by several layers

This isn't parents being careless. Stand on their side for a minute and count how many layers your message has to get through:

So the problem isn't that parents ignore WeChat — they open it dozens of times a day. The problem is that WeChat has no way to mark "this one is an announcement, you must read it" versus "this one is chatter, skip it" — and that distinction is the entire thing you need.

The real cost is bigger than one wasted trip

Four things you can do without changing tools

None of these require buying software. You can change all four today:

  1. Physically separate "announcements" from "chat." Set a rule and tell parents what it is: every formal notice about schedule changes, cancellations, or billing goes through one fixed channel — your service account, a DM in a fixed format, a text message, pick one. The class group is for chat and photos only. Once the rule holds, parents know which messages they're obligated to read.
  2. Ask for confirmation on formal notices, and accept that it's annoying. "Reply 1 to confirm" genuinely irritates people, but inside WeChat it's the only action that produces any kind of proof. The compromise: only require it for notices that would cause a wasted trip or involve money. Require it for everything and the confirmations stop meaning anything.
  3. Assume every family has two adults. Ask at intake: how many people need to receive notices for this child? Separated parents, grandparents doing pickup, parents splitting duties — none of these are edge cases, they're the norm. Notifying one person pushes the last-few-feet problem inside the family, where you can't see it.
  4. Give recurring things a recurring rhythm. Schedules, invoices, remaining lesson balances — send them on a fixed cadence, say the last Sunday evening of each month. Once parents expect it, they go looking for it instead of waiting to be pushed. That beats any reminder you can send.

The first three fix "will this particular notice land." The fourth fixes "do parents have to depend on your push at all." The fourth is the cheapest and the one most likely to get skipped.

When you actually do need a different tool

Those four will stop most wasted trips. Two situations they won't survive:

When we built ActiKidz, we treated parent notifications as their own thing rather than a byproduct of chat: each notice is stored per recipient, so who received it and when they read it lives in a record that doesn't depend on anyone's chat history. Email and in-app messages are the default channels; WeChat template messages are wired up too, but with one precondition — the parent has to have linked the official account first, and anyone who hasn't falls back to the other channels automatically. That precondition isn't something we can solve for you.

It's probably more useful to be clear about what it doesn't fix: it will not make parents more inclined to read messages. No tool does that. The fourth suggestion above — giving recurring things a rhythm — works because parents build a habit, not because something pushed harder. Software only handles the other half: whether, when a parent says "I never saw it," there's an answer both of you accept.

If you're still answering that question by scrolling back through a chat log, the thing that needs replacing isn't the parents. It's the channel.