Ask any honest organizer where their campaign's donations actually came from and the answer is not the email blast, not the flyer, and not the announcement — it is the chats: the family groups, the class-parent threads, the shul chevra, the seminary friends' circle that never stopped talking. The community's real communications infrastructure is the chat graph, and campaigns that treat it as an afterthought ("someone should post the link somewhere") leave their largest channel to chance. The chat cascade can be engineered — seeded deliberately, crafted for the medium, and run with the etiquette that keeps the community's goodwill — and engineering it is the single highest-leverage launch work most campaigns skip.
The cascade, understood structurally
Chat distribution works nothing like broadcast. A post in one group reaches that group; the campaign's actual reach happens when members FORWARD — into their own family threads, their other chevros, the groups the organizer has never heard of. Reach is therefore a product of two numbers: how many well-placed people share in the first hour (the seeds), and how forwardable the message is (the craft). The second ring — the recipients of forwards, people the committee doesn't know — is where campaigns exceed their warm list, and it is the ring flat appeals never reach: a stranger ignores an institutional broadcast, but a message forwarded by their own sister arrives with her endorsement attached. Everything in this playbook serves those two numbers.
Seeding: the first hour is the campaign
The launch hour's work, done properly. Build the seed list before launch: fifteen to thirty people chosen for placement, not prominence — the class mother in three school threads, the cousin who runs the neighborhood group, the alumnus in the yeshiva chevra, per the same warm-list thinking as the launch checklist. Placement means group membership; the quiet woman in eight active threads out-seeds the famous man in none. Arm each seed personally: not "please share" broadcast to all seeds, but one direct message each — "launching at 8; would you post this in the Bais Yaakov parents' thread?" — with the share text ready to forward. People asked personally, for a specific group, at a specific time, share at rates blast-requests never approach. And stagger the first wave: seeds posting across the launch evening (not all at 8:00) keep the campaign surfacing in chats through the whole prime window, and the second-day seeds (held back deliberately) give the cascade a second push before the first sag.
Message craft for the medium
Chat messages have their own copy rules, distinct from the page's. The forwardable unit is short: two to four lines plus the link — the message IS the headline, and anything requiring a scroll dies at the forward decision. The working anatomy: the hook line ("Our kollel's wheel is live — every number is one slot"), the personal line where the sender can add their own ("we just spun — landed $56!"), and the link with its preview doing the visual work (which is why the campaign page's share image matters — the preview card is the chat medium's billboard). Voice notes are the secret weapon for the right senders: the rosh yeshiva's thirty-second voice note travels through chats with an intimacy no text achieves — one per campaign, deployed at launch or the match window, from the one voice the community most wants in its ear. And the number one craft rule: write the message people can forward WITHOUT editing — self-contained, no "as I mentioned above," no inside references — because every edit required is a forward lost.
A campaign email arrives from an institution. A forwarded chat message arrives from your sister — same link, different physics. The cascade's whole power is that endorsement travels with the message.
Group etiquette: spend goodwill like it's real
The chat graph runs on social capital, and campaigns that burn it lose more than they raise. The rules the community's own norms enforce: post where you belong (seeds share into groups where they're genuine members — the parachuted stranger-post reads as spam and marks the campaign); once per group per phase (launch, the match window, the final day — three touches across a campaign is the ceiling for any one group, and each should carry news, not repetition); respect the group's own rules (the class thread that bans fundraising gets a direct-message strategy instead, not a tested boundary); and never guilt the silent (no "only 3 families from this group have given" — public giving-shame poisons a group permanently, and the community remembers who did it). The etiquette isn't a constraint on the cascade; it IS the cascade's sustainability — the organizer known for respectful campaigns gets his seeds' yes next year too.
Reading the cascade and steering it
Mid-campaign, the chat channel gives feedback broadcast never did. Watch the referral shape: platform analytics showing share-driven arrivals tell you which rings are alive; a campaign strong in the first ring but dead in the second has a message-craft problem (not forwardable) rather than a cause problem. Feed the cascade news: each update is a fresh forwardable unit — the match announcement, the milestone, the gold-slot story — and updates written chat-first (two lines + link) get carried by the same seeds who launched. Activate the second-ring converts: donors who arrived by forward and gave are your newest seeds — the thank-you flow can invite exactly that ("share the wheel with your own chevra?"), which is how cascades compound. And close the loop where it started: the final total, posted by the same seeds in the same groups, with the thank-you — communities that watch a campaign end well in their own chats carry the NEXT campaign further, which is the long game every cascade either builds or spends.
Frequently asked questions
How many groups should a campaign realistically reach?
A well-seeded community campaign surfaces in forty to eighty groups across its run — most invisible to the organizer, which is the point. The measurable proxy is second-ring share: when a third or more of donors arrive from links the committee didn't post, the cascade is working.
What time should the launch wave post?
The community's chat prime time: evening after supper (8:00–10:00), never Friday afternoon, with motzaei Shabbos as the strongest single window of the week for the second push. The medium's rhythms are the community's rhythms; post where attention already is.
Should the campaign have its own WhatsApp group?
Almost never — a campaign group demands attention the cascade borrows for free, and it dies the week the campaign does. The exceptions are operational (a phone-team coordination thread, a team-captains' room per the team mechanics); the donor-facing campaign lives in existing groups, as a guest.
How does the cascade work for communities with lighter chat culture?
The same structure rides whatever the community's real graph is — email forwards, text threads, the shul's actual bulletin board. The playbook's principles (seeds by placement, forwardable units, etiquette as sustainability) are graph-agnostic; the app is just where this decade's graph lives.