BlogGuide

How to Use AI Agents to Call Your Synagogue Member List With Event Reminders

Published

Sep 27, 2026

Read time

10 min

How do you use AI agents to call your members with event reminders?

You give the AI agent four things: a clean member list, a script you've approved, one voicemail recorded in your director's voice, and your own sign-up link. The agent then calls every member about the event, leaves the voicemail for anyone who doesn't answer, texts the link, and sends your office one plain list each morning of who's coming and who needs a person. Setup takes days, not weeks.

Here are the steps in order, with timings from a real synagogue campaign of about 1,930 members:

  • Step 1: Pick one paid event and its real deadline.
  • Step 2: Set the dates from the Hebrew calendar and your movement.
  • Step 3: Plan three rounds: two weeks out, a few days out, and after.
  • Step 4: Clean the member list.
  • Step 5: Write and approve the script.
  • Step 6: Record one voicemail in your director's voice.
  • Step 7: Set up the text with your own link, early.
  • Step 8: Check consent and handle opt-outs.
  • Step 9: Set calling hours around Shabbat and festivals.
  • Step 10: Work the daily list.

Step 1: Pick one paid event and its real deadline

Start with an event that has a price and a date that can't move. That's where a missed member costs the most, and where the call has a clear job.

  • High Holiday seats and dinners. Seats are often tied to dues: "Members must be current in their dues through August 2026 to be eligible for a seat assignment" (Congregation Etz Ahaim).
  • A community seder. Pesach 5787 runs 21–29 April 2027, so seder reservation calls belong in late March to mid-April.
  • Chanukah and Purim events. Chanukah runs 4–12 December 2026, and Purim falls on 22–23 March 2027 (Hebcal).
  • Membership renewal. For 5788, the dues window runs from mid-August to Rosh Hashanah on 1 October 2027.

One call can cover two related things, such as the paid dinner and the free service. Don't plan two separate calls in the same week. Members find that irritating.

Step 2: Set the dates from the Hebrew calendar and your movement

Don't copy last year's dates. 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 built from civil dates would call about three weeks late.

  • Put your movement on the campaign. Reform practice, as a CCAR responsum states it, is "Pesach for seven days, Shabuot one day, Sukkot (including Shemini Atseret) eight days, and Rosh Hashanah one day" (CCAR). Those end dates differ from the standard Diaspora calendar.
  • Use Diaspora dates in the US. Pesach, Shavuot and Shemini Atzeret fall differently in Israel, and some calendar tools use Israeli dates without saying so.
  • Watch the year boundary. Chanukah 5788 runs from 24 December 2027 to 1 January 2028, straight across the civil new year.

Give us the dates your congregation actually keeps, and the calls are scheduled around them.

Step 3: Plan three rounds: two weeks out, a few days out, and after

An event reminder campaign works best as three short rounds, not one call in the week of the event.

  • The invitation, about two weeks out. This reaches the members your email didn't. On one congregation's campaign, members called only two days before an event had already made other plans. Two weeks gives members time to decide and gives your office time to work the replies.
  • The RSVP confirmation, a few days out. This confirms the members who said yes and their guest counts, so you're not setting tables for people who quietly changed their minds. Places can be changed or released on the call.
  • The follow-up, within days after. This reaches members while the event is fresh, including the ones who meant to come and didn't, and flags anyone who wants to speak to staff.

For High Holiday seats, count back from the dues or seat-form deadline, not from Rosh Hashanah itself. If seats need dues paid by 15 September, the invitation round has to go out by the start of September at the latest.

Step 4: Clean the member list before anyone is called

Member lists collect people who shouldn't get the call: staff, businesses, duplicates, and people who asked not to be contacted. They come out first. On one congregation's list, about 2,020 contacts became about 1,930 real members.

  • Get the list from your system. AutoCallFlow integrates with ShulCloud, ShulSuite and Rakefet, and also works from a spreadsheet. We connect the member list for you.
  • Pull it fresh. A member who registered yesterday shouldn't get a call today asking them to register.
  • Check what was removed. You're told what came out and why before any call is placed.
  • Expect the list to improve. Every campaign finds members who moved away or joined another shul, so next year's list is cleaner.

Step 5: Write the script and approve every word

The script is short. It says who's calling, what the event is, and what the member can do next. You read exactly what will be said before a single call goes out, and if a call ever drifts from it, the whole campaign stops by itself.

  • Say who's calling. "I'm calling from the synagogue office." The agent never claims to be a member or a volunteer. Follow-up calls in a congregation traditionally come from a fellow member or clergy, and an AI can't truthfully be either.
  • Name the event, the date and the price. Members decide faster when they don't have to look anything up.
  • Offer one next step. "Would you like me to write you down and text you the link?"
  • Let "not this year" be final. A member who says no is written down, not asked again.
  • Build in the ability-to-pay rule. If a member says they can't manage the dues, the dues question stops for good. They keep getting invited to everything, and they're offered a quiet word with your director by name.

That last rule isn't only good manners. Halakhah is explicit: "If after asking the borrower once whether they have the money to repay they respond in the negative, and we know that they do not have the funds, we may not ask them again" (Ask the Rav).

Step 6: Record one voicemail in your director's voice

Most members won't pick up, so the voicemail is the part of the campaign most of them hear. Make it a voice they know. Your director records one message, about thirty seconds, and it plays for everyone who misses the call.

  • Keep it short: who's calling, the event, and "we've just sent you a text with the link."
  • Record it once. The same message is used for the whole campaign.
  • Expect it to carry most of the reach. On one High Holiday campaign, 966 members heard the director's voicemail, against 458 who spoke with the agent live.

The text is where many members answer. On one congregation's Sukkot invitation, 115+ members replied by text on the first day, and most of them hadn't picked up the call.

  • Use your own link. Members register and pay through your own ticket or sign-up page. The agent never takes payment.
  • Keep it one thread. The call and the text are the same conversation, so a member who replies doesn't have to explain themselves twice, and your staff can answer from the synagogue's own number.
  • Register for texting weeks ahead. "As of December 1, 2024, carriers began blocking unregistered A2P traffic outright" (JustCall). Registration takes time, so a congregation that starts in late August may not be texting by Rosh Hashanah.

Calling your own members isn't cold-calling strangers, but the rules still apply. In February 2024 the FCC ruled that AI-generated voices are "artificial" under the TCPA, the federal calling law (FCC 24-17).

  • Tax-exempt status isn't a blanket pass. As one calling company puts it, "There is no blanket TCPA exemption for nonprofits - cell phone consent rules still apply to your organization" (RoboTalker). Most member lists are mostly mobile numbers.
  • Know what's at stake. The law allows "base statutory damages of $500 per violation, or $1,500 per violation if knowing and willful" (Best Best & Krieger).
  • Remove opt-outs the same day. Anyone who asks not to be called comes off the list that day.
  • Ask your lawyer one question first: whether membership itself counts as consent for your congregation's calls.

This is a summary of public material, not legal advice.

Step 9: Set calling hours around Shabbat and festivals

Calls go out only in the hours you choose. For a synagogue, those hours follow the calendar, not just the clock.

  • No calls from Friday sundown to Saturday nightfall, and none after candle-lighting on a festival eve. Observance begins the evening before the date most people quote: Hebcal lists Yom Kippur 5787 as "Sun, 20 September sunset - Mon, 21 September nightfall" (Hebcal).
  • Candle-lighting times vary by city. The cut-off in one city isn't the cut-off in another, so set it for where your members live.

For the 2026 High Holidays, the practical last moment for dues calls was the afternoon of Friday 11 September, not the 12th or 13th.

Step 10: Work the daily list

Every morning the office gets one plain list, sorted by what needs doing: coming, maybe, can't make it, needs the office, moved away, wrong number, and asked to be removed.

  • Confirm the seats. Members who asked for places are noted with the number, so the office can confirm them.
  • Call the few who need a person. Each one comes with what the member actually said, so nobody starts from scratch.
  • Answer texts in the same thread. Your staff reply from the synagogue's own number, and to the member it's one conversation with their shul.
  • Update your records. Moves, wrong numbers and removals go back into your member list.

On one High Holiday campaign the list came to 81 items for the office, each checked against the real call recording before it reached the director. That's the point: the office works a short list instead of the whole congregation.

TaskBy hand (office and volunteers)With an AI agent
"Two weeks out, not two days. Members we called two days before an event had already made other plans."
- AutoCallFlow Team

What mistakes should you avoid with AI event reminder calls?

  • Calling too late. Two days before is too late. Two weeks is the working window.
  • Using last year's dates. The Hebrew calendar moves, and the 2027 High Holidays are three weeks later than 2026's.
  • Calling twice in one week about related things. Put the dinner and the service in one call.
  • Chasing a member who said they can't pay. Ask once. Then stop the dues question for good and keep inviting them.
  • Skipping the text. Many members who never answer the phone reply by text the same day.

What do you need to get started?

Your member list, one event with a date, thirty seconds of your director's voice, and your sign-up link. AutoCallFlow cleans the list, writes the script with you, listens to every call and sends the daily list. Member calling runs on the $60/month plan with 220 minutes of calling included, and most congregations add credits for a big month like the High Holidays.

For what the agent itself does on a call, read AI voice agents for synagogues, or visit the synagogue page.

FAQ

Won't our members find automated calls intrusive?

On one High Holiday campaign they didn't. Members chatted with the agent, several said thank you, and 155 called back to carry on the conversation. It helps that it's their own shul calling about something they care about, not a stranger selling something. Anyone who asks not to be called is removed that day.

Would a congregation really accept automated voice calls?

Many already get them. MyShulApp, a synagogue app, lets an office send a message that members "configured for calls receive" as "an automated phone call that reads the message aloud" (myshulapp.com). A two-way agent goes further, because the member can answer back.

Why can't we start texting immediately?

Because carriers now require business texting to be registered first, and they block traffic that isn't. Registration takes time, so start weeks before the event, and well before the High Holidays.

Volunteers are free, though. Why pay for this?

The volunteers are free. Organizing them isn't. A phone bank means "coordinating dozens of people, training them on scripts, managing shifts, and hoping enough show up" (RoboTalker). The agent handles the first call, the voicemail and the text, so your volunteers and staff spend their time on the members who need a person.

Won't calls make our reminders feel transactional?

They can, if the call is only about an amount. As one campaign consultancy puts it, when stewardship is neglected, reminders "feel transactional." So the script opens with the event and the community, asks once, and passes anyone who is struggling to your director by name instead of pressing.

What happens if we get this wrong?

Legally, the stakes are real: federal calling law allows damages of "$500 per violation, or $1,500 per violation if knowing and willful" (Best Best & Krieger). That's why opt-outs are removed the same day and every call is recorded, and why you should check your consent position with a lawyer before the first campaign.

Run your next event reminder campaign

Your member list, one voicemail in your director's voice and your own link. We call, text and send the office one plain list each morning.