The kehilla's announcements: email or the group chat?

Watch one week of a kehilla's information flow: the levaya notice that must reach everyone within the hour, the dinner reservation form that must be findable next month, the eruv status, the gabbai's schedule change, the school's fifteen-attachment registration packet. Now notice the failure stories every community owns — the family that never heard because they are not on the chat; the form nobody can find because it scrolled away four hundred messages ago. Neither rail failed; a message rode the wrong one.

The two rails, honestly compared

The chat group's virtues are immediacy and presence: instant delivery, read-by-supper certainty, the communal murmur that makes announcements feel alive. Its structural costs: membership excludes whoever lacks the platform — a real fraction of every kehilla, per the account-question realities — the archive is a scroll (searchable in theory, lost in practice), attachments degrade, and every announcement channel drifts toward conversation until the announcements drown, the moderation battle mapped in the announcement-architecture story.

The email list's virtues are the mirror image: reach across every device tier (every household has mail, on any architecture — including inboxes on talk-and-text-adjacent setups), a permanent per-household archive (the dinner form is findable in Kislev), attachments that arrive intact per the document craft, and a tone that stays institutional because nobody replies-all a shmooze. Its costs: latency measured in hours, and the deliverability craft below.

“The chat asks "did everyone see it now?" Email asks "can every home find it later?" A kehilla needs both answers.”

kolbo.life

The routing rule kehillos converge on

The communities that run this well route by message shape:

1. Urgent + ephemeral → the fast rail. The levaya, the minyan change tonight, the weather closure: chat's home territory, where immediacy is the whole value.
2. Durable + official → email. Schedules, forms, registration packets, the newsletter, anything with an attachment or a deadline beyond today: the list is the kehilla's paper of record.
3. Both, for the genuinely important. The rule that ends the "but I never got it" era: anything both urgent and consequential rides both rails, with email as the citable original. Redundancy for the things that matter is not inefficiency; it is respect for the households at every tier.
4. The institutional address discipline on the receiving end: kehilla mail lands on each family's household address per the postal map — one door the institution can rely on, whichever parent answers.

Running the list like infrastructure

The email rail rewards a small amount of craft that most volunteer-run lists never learn: send from one consistent institutional address (the household's admission rules then greet it as a known sender, per the door-policy model); subject lines that carry the whole message's identity ("Dinner RSVP — due 3 Adar"); one announcement per email rather than the weekly omnibus nobody scrolls; and the digest tier offered for the willing. The dividend is quiet but structural: the kehilla's voice arrives as institutional mail — expected, filed, findable — rather than as one more notification in the storm the household is campaigning to silence.

The migration a kehilla can actually run

Institutions moving from chat-only to two-rail do it in one season: announce the list on the chat for a month, collect household addresses at the dinner and the door, and begin the both-rails habit with the very next consequential announcement. The chat keeps its immediacy; the list quietly accumulates the record — and within a year, nobody remembers governing without it.

Frequently asked questions