1 · Who this goes to
Communications segments
People saved lists
Counts reflect the visible directory sample; the congregation headline is 487.
All opted-in members · 164 people · 164 reachable on WhatsApp · 0 excluded — no consent or no line
2 · Which message
A WhatsApp template may only be sent once Meta has approved it. A pending template is shown so its state is never hidden, but it cannot be selected or drafted.
3 · Live preview
The {{name}} placeholder renders per person at draft time. Only opted-in people enter this preview or a send; anyone pending or opted out is excluded and never quietly messaged.
4 · How much is already being asked of these people
4 people are already in 2 or more broadcasts across the church — counted over everything not yet sent, plus everything sent in the last 7 days.
5 broadcasts could be matched to the people they reach, after consent and after each member’s own mutes.
3 more broadcasts in this window could not be matched to people — a saved segment is a count of the congregation, not a list of names. Every figure here is therefore a minimum, not a total.
All opted-in members is a saved segment — a count of the congregation rather than a list of people — so who it reaches cannot be checked against the broadcasts above. That is not the same as nobody being over-messaged here.
5 · Hand it to a person
This church requires one named person to approve a broadcast before it goes out. This one goes to Ruth Chikwanda (Communications lead) or Faith Mensah (Executive pastor).
This draft would address the 164 reachable people in All opted-in members. 0 excluded — no consent or no line, never messaged quietly.
ChurchOS never sends on its own — it drafts; a person reviews and sends every broadcast. WhatsApp goes via approved Business templates, never automation.