Table of Contents
Synagogue dues collection: what's actually permitted
Synagogue dues collection through phone reminders is well supported when it asks for a commitment, or gates a specific benefit like High Holiday seating on payment or an agreed arrangement — the Reform movement's own responsa committee calls this gentler than legal action. What's not supported anywhere is treating a member like a delinquent account and chasing a specific dollar balance already billed.
What does the CCAR responsum actually say about dues collection?
CCAR Responsa 5764.1, "Collection of Debts to the Congregation," lists remedies preferable to litigation. It states directly: "we can tell our members that acceptance of their children to religious school, admission to High Holiday services, and the scheduling of certain life-cycle events are contingent upon payment of financial obligations or the making of acceptable arrangements to do so" — and that this approach is "less difficult, divisive, and contentious than the initiation of legal action to collect debts" (CCAR Responsa).
Two things follow directly from that wording. First, gating High Holiday seating on dues — the mechanism many synagogues already use — is described by the Reform rabbinate's own responsa committee as the gentler alternative, not a harsh tactic. Second, the gate has two doors: payment, or an agreed arrangement. A stated hardship doesn't remove the gate — it opens the second door.
Why does the responsum call this the gentler path?
The ruling frames the underlying concern as one of institutional dignity, not outside reputation: certain collection practices are "wrong purely and simply because of the impression they ought to make upon us, because those who strive to be holy should not behave in such a manner." The committee adds that legal action should be used "only as the absolutely last resort, when all other available remedies have been tried and have failed."
The practical reframe: a phone reminder that asks for payment or an arrangement isn't a step toward collections — per this responsum, it's one of the "other available remedies" that must be tried first. Two caveats worth stating plainly: the page itself notes these responsa "do not necessarily reflect current CCAR policy or approach," so treat it as reasoning on the record rather than binding law, and CCAR is specifically the Reform rabbinate — a Conservative or Orthodox congregation's own rabbi may reason differently and should be consulted directly.
What are the real financial stakes behind a High Holiday dues gate?
- Individual adult dues: $1,420 at one mid-Atlantic congregation, $2,140 at another — real published figures, not estimates.
- Two-adult household dues: $3,650 at the same congregation charging $2,140 individually.
- Non-member guest High Holiday tickets: $565 for one year at another congregation — the price of not being current on membership at all.
- The deadline is hard and religious, not administrative: one congregation requires "at least 1/2 of member dues... paid by September 15" for tickets; another requires members "current in dues through August" for a seat assignment. Neither date moves, because the Hebrew calendar sets it.
Dues typically cover 45-85% of a synagogue's operating costs, which is why this is a conversation for the executive director and treasurer, not just the office administrator.
What's the difference between gating a benefit and chasing a balance?
Ability to pay is the line the sources converge on. Reform responsa permit the dues gate only for "a member who has the ability to pay," while simultaneously holding that "no Jew should be denied the opportunity to affiliate with the community... out of inability to pay." Separately, Orthodox writing on debt collection agrees in principle: "you dare not sanction him for something outside his ability." Both traditions land on the same rule from different directions — the gate applies to can't-be-bothered, never to can't-afford.
How should a synagogue actually handle a member who says they can't pay?
- Stop the automated ask immediately — the applicable principle: "if after asking the borrower once whether they have the money to repay they respond in the negative... we may not ask them again." One ask, one follow-up at most, then stop.
- Route to a named person, not a form: synagogue dues policies commonly name the executive director and rabbi directly, by name and extension, for hardship conversations — not a generic office line.
- Resolve through an arrangement, not a waiver with no resolution: per the responsum's own wording, the obligation is satisfied by "payment... or the making of acceptable arrangements" — a reduced amount or a payment plan closes the gate; silence does not.
- Never let an AI voice make this call: hardship detection should hand off warmly to the named human immediately, since getting this wrong in a community where the rabbi knows everyone isn't a conversion problem, it's a reputational one.
What does a real synagogue calling campaign's data actually look like?
In a High Holiday dues and ticket reminder campaign covering roughly 1,900 contacts, calls reached a live person on 26% of attempts and left 966 voicemails recorded in the director's own voice rather than a synthetic one. A separate Sukkot invitation campaign for the same congregation got most of its responses by text, from members who hadn't answered the call — over 115 text replies on the first day alone.
That's not two channels competing — it's one thread: call, then a voicemail in a familiar voice if nobody answers, then a text follow-up, and the member replies on whichever leg suits them while staff step into the same conversation. Plan on roughly 26% for live conversations, not a higher number borrowed from academic call-center benchmarks — those studies don't reflect a real member list's actual pickup behavior.
Does ShulCloud or other synagogue software already handle this reminder?
Yes, partly. ShulCloud's batch billing already issues dues invoices and mass payment reminders to a congregation's full list — that part of the workflow isn't missing. The gap is what happens after: the reminder already exists and it's an email. Nothing escalates when it's ignored. A call-and-text layer is the escalation step that email alone doesn't provide, not a replacement for what ShulCloud already sends.
| What the reminder does | Handled by ShulCloud today | Handled by a call-and-text layer |
|---|---|---|
| Sends the dues statement and payment reminder | Yes — batch billing and mass reminders | Nothing to add — ShulCloud already does this |
| Follows up when the email goes unread | No next step | A call, then a voicemail in your director's voice, then a text |
| Hears a member say they can't pay right now | No | Dues asks stop, event invitations continue, and a private talk with your director is offered |
| Tells the office who needs a personal call | No | One plain list each morning: paid, call back, can't pay right now |
"The reminder already exists and it is an email. Nothing escalates when it is ignored. That escalation is the product — not a collections tactic, but one of the remedies the responsum itself treats as gentler than legal action."
Why doesn't one dues script work for every synagogue?
Dues models differ fundamentally across congregations, and a script built for one model reads as confused or wrong on another.
- Fixed dues: a flat amount per household, with a formal abatement process for hardship — the model the CCAR responsum above addresses most directly.
- Fair share: dues set as a percentage of household income, commonly cited between 1% and 2% depending on the source — a call here needs to ask about a commitment level, not quote a fixed number.
- Voluntary commitment: members choose their own amount with no published minimum — the ask is entirely different in tone from a fixed-dues reminder.
- Sustaining amount: the synagogue publishes its actual per-household cost (commonly $2,900-$3,300 in the sources checked) and asks members to meet or approach it — a transparency-based ask, not a bill.
A call script referencing "your $2,140 balance" on a fair-share or voluntary-commitment congregation would be factually wrong. Confirm which model a congregation uses before building the campaign, the same way the festival calendar needs confirming before scheduling one.
Implementation checklist
- Confirm the dues model first — fixed, fair share, voluntary, or sustaining — before writing a single line of script.
- Confirm the movement's festival calendar before scheduling any campaign around a Hebrew-calendar deadline; Reform congregations keep several festival dates differently from the standard count.
- Set the ability-to-pay rule before launch: one ask, one follow-up, then route to a named person — never a third automated attempt.
- Never quote a specific balance owed in an automated call or text — reference the deadline and the benefit, not a dollar figure billed.
- Report on escalation, not collection: the honest metric is "reminders that got a response after the email didn't," not dollars recovered from a chase.
FAQ
Does Jewish law allow gating High Holiday seats on unpaid dues?
Reform responsa (CCAR 5764.1) explicitly permit it, describing it as gentler than legal action, provided the gate can be satisfied by payment or an agreed arrangement — not payment alone with no path for hardship. This is a Reform-specific ruling; a Conservative or Orthodox congregation should confirm with its own rabbi.
What if a member says they can't pay?
The automated ask stops immediately — asking a second time after a stated inability to pay is not supported. The record routes to a named staff member (commonly the executive director or rabbi) to work out an arrangement, which is what actually satisfies the obligation under the responsum's own terms.
Does this apply the same way in Orthodox or Conservative congregations?
The specific responsum cited is Reform (CCAR). Orthodox sources checked converge on the same ability-to-pay principle from a different direction, but exact practice may differ by movement — this is a conversation for your own rabbinic authority, not a universal script.
Does ShulCloud already send dues reminders?
Yes — ShulCloud's batch billing handles invoices and mass payment reminders. The gap it doesn't cover is escalation: what happens after that email goes unopened.
How often do calls actually reach a live person?
In a real High Holiday campaign covering about 1,900 contacts, calls reached a live person 26% of the time, with the rest going to voicemail recorded in the director's own voice — plan around that figure rather than a higher call-center benchmark.
See how a dues and High Holiday reminder sequence works end to end: visit the synagogues and congregations solutions page.