The announcement problem: reaching every home, every tier, every time

Stand in the gabbai's shoes on a Thursday night. A levaya is called for nine tomorrow morning. In the old world, the phone chain handled it — twenty calls fanning to four hundred homes by a discipline every community once knew. In the new world, he has a chat group that reaches most of the shul instantly, an email list that reaches all of it eventually, a street of households on talk-and-text devices, and three families who moved in last month and are on nothing yet. The message is simple. The architecture is not — and pretending one channel is the architecture is how announcements miss homes.

The broadcast problem, stated properly

Community announcement systems fail on four axes, and naming them is half the fix:

• Coverage. The kehilla is tier-diverse by conviction: secured smartphones, basics, talk-and-text — the deliberate spectrum this whole library documents. Any single-platform channel excludes a principled fraction; the account question alone keeps real households off the chat rails.
• Urgency mismatch. The levaya and the dinner reminder are different species of message sharing one pipe. Systems without an urgency distinction train their audience to skim — and the skim eats the levaya notice too.
• Authority blur. When anyone can post to the channel, the official and the forwarded rumor wear the same clothes. An announcement system is only as trusted as its sender discipline.
• Memory loss. The chat scroll forgets; the family that asks "when is the dinner again?" in Kislev is not lazy — the system genuinely lost the answer, per the two-rails comparison.

The architecture kehillos converge on

The communities that solved this run the same three-layer design, whatever brands they use:

1. One authoritative source. A single institutional identity originates everything official — the shul office, not seventeen well-meaning forwarders. Every channel carries its messages; the community learns that authority has exactly one voice, which is also the anti-impostor defense every scam-aware community needs.
2. Channels by message class, not by fashion. Urgent-ephemeral rides the instant rails — the chat, and crucially plain text messaging, the one channel that reaches every phone ever made, the quiet universality KolBo Text builds on. Durable-official rides the email list as the record. The consequential rides both. The phone chain survives as the escalation tier for the truly critical — communities that retired it entirely rediscover it at the first regional power cut.
3. The membership pipeline. New family arrives → one form, at the welcome kiddush → every channel updated at once. Coverage decays at the edges (the move-ins, the seminary returnees, the split households); the pipeline is the maintenance the whole architecture stands on — the same institutional-address discipline as the household postal map, run from the institution's side.

“A community announcement is not sent when it leaves the office. It is sent when it has reached the last home on the slowest tier.”

kolbo.life

The platform question underneath

Everything above runs on any stack a kehilla already has — and everything above runs better when the community's own infrastructure carries it. A community platform where groups exist without the account-exposure trade, where the broadcast channel is architecturally separate from the schmooze, and where the same message fans to chat, text, and mail from one send — that is the shape KolBo WhatsApp's "community groups without the account — connection without the exposure" points at, generalized to the kehilla's whole nervous system: the group problem and the group-admin craft become one design instead of one volunteer's nightly moderation battle.

The honest note for today: no kehilla should wait for perfect infrastructure to fix its architecture. The three layers — one voice, classed channels, a membership pipeline — upgrade any community this month, on whatever rails exist.

Frequently asked questions