Job · Cohort notices
One notice to a cohort. Only the exceptions reach a person.
A timetable change goes to twenty-eight families as a utility template. Replies are matched by a rule and tagged: confirmed, needs a call, no reply. The confirmations close themselves, the problems get assigned, and the silent families get a scheduled reminder.
عرض توضيحي ببيانات وهمية.
What it looks like
Cairo Learning: Year 4, September intake, 28 families.
“Monday’s class moves to 09:30. Reply OK to confirm, or CALL if that doesn’t work.” One send, then the sorting happens without anyone opening a thread.
The notice goes to a segment, not a list someone pasted
Year 4 · September intake · 28 families. The segment is a filter on contact fields, so it is right on the day it is sent.
Nour Hassan replies OK
The rule matches the keyword, tags the contact Confirmed, and closes the conversation. Nobody opened it.
Tarek Fouad replies “CALL — we have a school run”
Tagged and queued for a call, assigned to a named person with the reply visible. This is the one that needed a human, and it is the one a human sees.
Dina Saleh replies OK from Instagram
Same rule, same tag, different channel. One contact, one thread, regardless of where the family answered.
Youssef Adel says nothing
No reply · reminder due. Silence becomes a scheduled task rather than an assumption.
The morning reads: 24 confirmed · 3 need a call · 1 reminder due
One message to twenty-eight families. Four of them needed a person, and the office knows exactly which four.
The problem
The broadcast is easy. The twenty-eight replies are not.
Sending to a year group takes a minute. Reading what comes back takes the rest of the morning, and the important part is what never arrives.
- One notice produces a reply per family
- A timetable change sent to 28 families comes back as 28 messages into a single inbox, all within the same hour.
- Confirmations and problems look identical
- “OK” and “we have a school run” arrive as the same kind of row in the same queue. Someone has to open each one to find out which is which.
- The families who never reply are the ones that matter
- Silence is indistinguishable from agreement in an inbox, and it is the easiest thing in the operation to lose track of.
- Follow-up falls to whoever remembers
- Without an owner per exception, the call that needed making is remembered on Monday morning, in the classroom, by the family.
How it works
The mechanism, step by step.
A segmented template send, a matching rule, an assignment, and a scheduled reminder for the silence.
- The send is a template to a contact segment
- An approved utility template, addressed to a saved filter — year group, intake, opted-in guardians — rather than a list someone exported last term.
- Replies are matched by an automation rule
- OK, CALL, and the obvious variants and Arabic equivalents you add. The rule writes a tag onto the contact: confirmed, or needs a call.
- Confirmations close themselves
- A tagged confirmation needs no human step. The conversation closes with the tag recorded, which is what makes the remaining queue meaningful.
- Exceptions are assigned to a person
- Anything the rule cannot match, and anything that matched CALL, is routed to a named owner with the reply and the notice both in view.
- The silence is scheduled, not forgotten
- Contacts with no reply after your chosen interval get a reminder, and the list of who is still silent is a filter anybody can open.
- The result is countable
- Confirmed, needs a call, no reply — tags on contacts, so the cohort's status is a number you read rather than a thread you scroll.
What it costs to send
A cohort notice is a utility template, priced per recipient.
Meta charges per message delivered, not per send. Twenty-eight families is twenty-eight utility messages. The replies arrive inside the window the family opened by answering.
- Timetable notice, one family (Egypt)
- $0.0036
- Utility rate: a notice about a class the family is already enrolled in. Billed per recipient.
- The same notice to 28 families (Egypt)
- $0.1008
- 28 recipients × $0.0036 per utility message. The cost of a cohort notice scales with the cohort, which is why the segment should be a filter and not a list.
- Handling the replies
- Service message
- A message from the customer opens a 24-hour window. Meta began charging for service messages on 1 October 2026, with the first 1,000 per business phone number per month free.
- An open-day invitation instead (Egypt)
- $0.0644
- Promotional sends are marketing templates — about eighteen times the utility rate, which is why a notice and an invitation should never share a template.
Source: Meta WhatsApp per-message rate card, Egypt, retrieved 2 November 2026; category, window and service-message rules from Meta developer documentation.
Meta bills these fees, not us, and we never mark them up. BlendDesk charges for seats and AI resolutions.
Control
A cohort send is the easiest thing to get wrong.
Twenty-eight families is twenty-eight chances to message someone who did not ask to hear from you.
- No send to a guardian who has not opted in
- Opt-in is a property of the contact and it is checked at send time. A contact without it is excluded from the segment rather than quietly included.
- Frequency caps
- A limit per contact per period, so a week of small changes does not turn into a week of notifications and an exhausted year group.
- A stop word is honoured everywhere
- A family that opts out is opted out across every channel and every future cohort send, not just the thread they replied in.
- A person owns every exception
- Nothing tagged “needs a call” sits unassigned. The queue has an owner, and the unassigned count is visible.
- Every send is readable
- Which template, which segment, who was excluded and why, which rule tagged which reply — one record, after the fact.
Source: WhatsApp Business Messaging Policy, updated 23 September 2026.
What you need
The segment and the keywords are the work; both are a morning.
- Guardian contacts with opt-in recorded, and the fields that define a cohort — year group and intake.
- An approved utility template for the notice, in the languages your families read.
- The reply keywords you will match, including the Arabic equivalents, and the tag each one writes.
- A named owner for the exception queue.
- A reminder interval for the families who have not replied.
Questions schools actually ask.
Is a timetable change a utility or a marketing message?
Utility: it concerns a class the family is already enrolled in. An open-day invitation to the same families is marketing, and it should be a separate template so the categories never blur.
What happens to a reply the rule does not recognise?
It goes to the exception queue with a person's name on it. An unmatched reply is treated as something that needs reading, never as a confirmation.
Can parents reply in Arabic?
Yes. You add the Arabic keywords to the same rule; anything outside them becomes an exception rather than a guess.
How do we see who has not responded?
As a filter on the cohort: contacts with no confirmation tag after the send. That filter is also what the scheduled reminder runs against.
Does it connect to our timetable or school system?
Not as a built-in integration. You can register an HTTPS endpoint of yours as a tool, or send the notice from a segment you maintain in BlendDesk. We do not claim a packaged SIS connector.
Can we require approval before a cohort send goes out?
Yes. A send to a segment can be gated behind an approval, so a named person signs off the template, the segment and the exclusions before anything is delivered.
Send your next cohort notice once.
Book a demo, bring a year group and a change you need to announce, and we will have the replies sorting themselves against a test number before the call ends.