Table of Contents
- What is an AI voice agent for a synagogue?
- Why call members when the synagogue already sends emails?
- What does an AI voice agent say when it calls a member?
- Whose voice do members hear?
- Do members reply by phone or by text?
- What should an AI voice agent never do on a synagogue call?
- Does the agent follow the Jewish calendar?
- Which synagogue events can an AI voice agent call about?
- What does the synagogue office get back?
- How is the member list prepared before anyone is called?
- How much does an AI voice agent cost a synagogue?
- How does a synagogue get started?
What is an AI voice agent for a synagogue?
An AI voice agent for a synagogue is a phone system that calls your members for you and holds a real two-way conversation about something with a date and a price on it: High Holiday seats, a paid Sukkot or Chanukah dinner, a community seder, or the dues that have to be current before seats are assigned. A member can ask what time it starts, say they already bought tickets, add a family member, or mention they've moved, and get an answer on the same call.
That's different from most of what comes up when you search for this. Most AI phone products offered to synagogues are receptionists: they answer the office phone when someone calls in. An AI voice agent for member calls works in the other direction. It goes through your member list, and everything it hears comes back to the office.
- It calls every member on the list, only in the hours you choose.
- It leaves a voicemail in your director's own voice, recorded once, for everyone who doesn't pick up.
- It texts your own ticket or sign-up link to everyone it didn't reach live.
- It reports back with one plain list: who's coming, who's a maybe, who needs the office, who has moved and who asked not to be called.
Why call members when the synagogue already sends emails?
Every congregation already sends a reminder. It's an email, a statement or a letter, and nothing happens when it's ignored. ShulCloud already supports "batch billing, mass payment reminders, and billing statement generation" (Shulware). The reminder isn't what's missing. What's missing is the next step after a member doesn't open it.
That gap costs real money, because synagogue events are paid and their deadlines can't move:
- Seats depend on dues. "At least 1/2 of member dues must be paid by September 15, to receive High Holiday tickets" (Pleasantville Community Synagogue). "Members must be current in their dues through August 2026 to be eligible for a seat assignment" (Congregation Etz Ahaim).
- The amounts are large. "$1,420 dues each" per adult at Har Zion Temple. "Individual Adult - $2,140 / 2 Adults - $3,650" at Anshe Emet. Non-member guest tickets at "$565 for one year" at Beth Tfiloh.
- Dues carry the budget. Depending on the congregation, dues cover anywhere from "45 percent all the way to 85 percent" of costs (Etz Hayim).
A member you never reached is a seat you never filled. An email can't find out why someone went quiet. A phone call can.
What does an AI voice agent say when it calls a member?
Here's a typical call to a member who never opened the High Holiday email, picking up on a Tuesday evening:
- Agent: "Hello, I'm calling from the synagogue office about High Holiday seating. Is now a good time?"
- Member: "Yes, fine. I think I saw an email about it."
- Agent: "We just wanted to make sure you have your seats. Would you like me to write you down and send you the link by text?"
- Member: "Yes please. And my daughter is coming this year as well."
- Agent: "I'll put down two and let the office know so they can confirm with you. Sending the link now. If you reply to that text, someone from the office will see it."
What the office gets from that one call: two seats noted, the link sent by text, and a member ready for the office to confirm. The agent doesn't take payment and doesn't issue tickets. Members still register and pay through your own link. The call's job is to get them there, and to find out what's in the way if they don't go.
Whose voice do members hear?
For most of a campaign, a person's. Most members don't pick up, and a voicemail doesn't need a computer voice at all. Your director records one short message, about thirty seconds, and everyone who misses the call hears her.
On one congregation's High Holiday campaign of about 1,930 members:
- 458 members had a real conversation with the agent, about a quarter of the list.
- 966 members heard the director's own recorded voicemail.
- 155 members called back to carry on the conversation, and the agent answered them.
So the AI voice only speaks on the live calls. That changes the usual worry about sounding robotic: the part of the campaign most members actually hear is a voice they already know.
Do members reply by phone or by text?
Both, and you can't predict which. On the same congregation's Sukkot invitation, 115+ members replied by text on the first day, and most of them hadn't answered the call. Older members, meanwhile, did well on live calls.
So it isn't a phone campaign versus a text campaign. It's one thread per member:
- A call, which some members answer.
- A voicemail in a familiar voice for those who don't.
- A text with your link, which many members answer instead of calling back.
- Your staff, stepping into the same conversation from the synagogue's own number when a member needs a person.
Plan on roughly a quarter of calls becoming live conversations. The rest of the reach comes from the voicemail and the text. A plan that assumes most members will pick up will be wrong by a wide margin.
| What you need | Email or statement | Recorded broadcast call | AI voice agent |
|---|---|---|---|
What should an AI voice agent never do on a synagogue call?
This is where a synagogue differs from a business, and where a generic calling tool gets it wrong.
- Never pretend to be a member or a volunteer. Follow-up calls in congregations traditionally come from a fellow member or from clergy. An AI can't truthfully claim to be either, so it calls on behalf of the synagogue office and never says otherwise.
- Never press someone who says they can't pay. The Reform responsum on congregational debts confines the dues gate to "a member who has the ability to pay" (CCAR 5764.1). Orthodox writing agrees: "If someone cannot afford to pay the annual dues, you dare not sanction him for something outside his ability" (Torah Musings). So when a member says they can't manage it, the dues question stops for good, not just on that call.
- Never stop inviting them. That member keeps getting invited to every service and event. Only the dues question stops, and they're offered a quiet word with your director by name.
- Never sound like a collection agency. CCAR describes making High Holiday admission "contingent upon payment of financial obligations or the making of acceptable arrangements to do so" as "less difficult, divisive, and contentious than the initiation of legal action." The call is the gentle step that comes first.
- Never call after candle-lighting. Festivals begin at sundown the evening before the date most people quote. Hebcal lists Yom Kippur 5787 as "Sun, 20 September sunset - Mon, 21 September nightfall" (Hebcal).
Does the agent follow the Jewish calendar?
It has to, because the dates move every year. The High Holidays began on 11 September in 2026 and begin on 1 October in 2027, because 5787 is a Hebrew leap year (Hebcal). A reminder schedule copied from last year's civil dates would call three weeks late, after the dues deadline has passed.
- Dates come from the Hebrew calendar, not a list of last year's dates.
- Your movement changes the dates. A CCAR responsum describes Reform practice as "Pesach for seven days, Shabuot one day, Sukkot (including Shemini Atseret) eight days, and Rosh Hashanah one day" (CCAR). That moves the end dates a Reform congregation's reminders need.
- Diaspora, not Israel. Pesach, Shavuot and Shemini Atzeret fall differently in Israel, so a US congregation's schedule should use Diaspora dates.
The next paid events on the calendar are Chanukah (4–12 December 2026), Purim (22–23 March 2027) and Pesach (21–29 April 2027), when seder reservations need calls from late March.
Which synagogue events can an AI voice agent call about?
- High Holiday tickets and seats. The biggest one: seats, the dinner, and the dues that have to be current first. One call can cover the paid dinner and the free service, because two calls in one week irritates people.
- Seders, Chanukah and community dinners. Real headcounts against a real deadline. Start about two weeks out. On one congregation's campaign, members called only two days before had already made other plans.
- Membership renewal and dues. A call from the office, not a collection notice. The most useful thing it finds often isn't who pays. It's who is quietly struggling and hasn't said so.
- A cleaner member list. Lists collect people who left years ago, moved away, joined a shul closer to home or passed away. Every campaign sorts them, so next year's calls go to the right people.
What does the synagogue office get back?
One plain list every morning, in plain English, sorted by what needs doing:
- Coming, with how many seats or places.
- Maybe, for the office to follow up closer to the date.
- Needs the office, with what the member actually said.
- Moved away, or belongs to another shul now.
- Asked to be removed, and already taken off the list that day.
On the High Holiday campaign above, that came to 81 items for the office, each one checked against the real call recording before it reached the director. The office works through a short list instead of listening to hundreds of voicemails.
How is the member list prepared before anyone is called?
The list is cleaned before the first call. Staff, businesses, duplicates and anyone who has asked not to be contacted come out first. On one congregation's list, about 2,020 contacts became about 1,930 real members. You're told what was removed and why before anything happens.
- Your system stays as it is. AutoCallFlow integrates with ShulCloud, ShulSuite and Rakefet, and works from a spreadsheet too. We connect your member list for you.
- Members still sign up through your own link, so seats and payments stay in your own system.
- You approve the script before a single call goes out. If a call ever drifts from it, the whole campaign stops by itself.
"The reminder already exists, and it's an email. Nothing happens when it's ignored. The call is what happens next."
How much does an AI voice agent cost a synagogue?
Member calling runs on the $60/month plan, which includes 220 minutes of calling. There's a $150/month plan with 360 minutes for congregations that call a lot. For a big month like the High Holidays, most congregations add credits, then go back to the normal plan.
- Compare what you get back, not the price per call. Broadcast services charge per contact or per credit, where a credit is 30 to 60 seconds of audio. A real conversation runs minutes, so it always looks pricier per call.
- The fair measure is per result: a confirmed seat, an RSVP, a renewed membership, or a member you finally heard from.
- The stakes run to hundreds or thousands per household. One renewed membership at Har Zion's published rate is $1,420 per adult.
How does a synagogue get started?
- Connect your member list from ShulCloud, ShulSuite, Rakefet or a spreadsheet. We clean it and tell you what came out.
- Your director records one voicemail, about thirty seconds, in her own voice.
- You read and approve the script. Nothing is called until you say so.
- We call, and you read the list. Calls go out only in the hours you choose, and your office answers members in the same thread from your own number.
Start the texting setup early. "As of December 1, 2024, carriers began blocking unregistered A2P traffic outright" (JustCall), and registration takes time. A congregation that signs up in late August may not be texting by Rosh Hashanah. For how one campaign runs across tickets, dues and events, see how a synagogue calling service works, or visit the synagogue page.
FAQ
Isn't this just a robocall?
No. A robocall plays a recording at you and hangs up. Here a member can ask a question, say they already have seats, or tell us they've moved, and get a real answer. The calling rules still apply: the FCC ruled in 2024 that AI-generated voices count as "artificial" under federal calling law (FCC 24-17), so consent and an easy way to opt out matter. Anyone who asks not to be called is removed the same day.
Won't it sound robotic and embarrass us?
Most members never hear the AI voice at all. On one High Holiday campaign, 966 members heard the director's own recorded voicemail, while about a quarter of the list spoke with the agent live, in an ordinary conversation. You approve every word of the script first, and if a call ever drifts from it the campaign stops by itself.
Do we have to tell members it's an AI?
Where state laws address it, disclosure is mostly required when someone asks. One analysis of Utah's AI law describes the duty as "triggered on request, not proactively in every interaction" (casrai.org). Rules vary by state and are changing, and in a congregation we'd recommend being open about it anyway. You decide the wording with us. What the agent will never do is claim to be a member or a volunteer.
We already get dues reminders from our existing system. Why add calls?
You do, and that's exactly where the calls start. ShulCloud already handles "batch billing, mass payment reminders, and billing statement generation" (Shulware). Those reminders are emails. The call goes to the members who didn't open them, so it picks up where your system stops.
Is it even appropriate for us to chase members for money this way?
It's a fair question, and it has a published answer. A CCAR responsum describes making High Holiday admission contingent on payment "or the making of acceptable arrangements to do so" as "less difficult, divisive, and contentious" than legal action. The call follows that path: it asks once, offers an arrangement, and stops the dues question for good if a member says they can't manage it. CCAR is the Reform rabbinate, so a Conservative or Orthodox congregation should check with its own rabbi.
Our congregation's data is sensitive, not just personal. Who sees it?
Only the people running your campaign. Your list is used to call your members and for nothing else. It's never shared and never used to approach another congregation. Anything a member says about hardship goes only to the staff member you name, and we delete the list whenever you ask.