Salesforce for Synagogues means one platform, Agentforce for Nonprofits, that connects every stage of a congregant’s life, from religious school enrollment through bar and bat mitzvah preparation to yahrzeit tracking, in a single family record instead of scattered legacy systems.
Synagogue relationships do not run on a calendar year. They run on a lifetime. The nine-year-old learning aleph-bet in Hebrew school today is the parent enrolling their own child a generation from now, and every milestone in between, from religious school to bar or bat mitzvah to a parent’s yahrzeit, belongs to the same family story. That was the premise behind Fíonta’s second session in the Modern Synagogue Series, The Full Member Lifecycle, presented on August 13, 2026, by Jordan Berger, VP of Delivery at Fíonta, with Mike Brown, Lead Strategic Solution Engineer for Nonprofits at Salesforce.
This was the second webinar in this series. Click here to view the first webinar presented for those synagogues that currently have Salesforce, and here for synagogues that do not currently work on Salesforce.
The session combined two threads that are usually treated separately: the emotional arc of a member’s life in the community, and the operational console that synagogue staff use to run it. Here is what attendees saw.
A quick primer on the platform underneath it all
Mike Brown opened with context on Salesforce for nonprofits, which recently evolved into Agentforce for Nonprofits (formerly Nonprofit Cloud). He described the platform in layers, starting with trust, security, and scalability at the foundation, then a data layer that unifies information from spreadsheets, legacy databases, or other systems, then an application layer that Fíonta and other partners build on, and finally the nonprofit industry solutions that track households, relationships, and lifecycle touchpoints over time.
He also addressed a question that comes up often as synagogues consider AI: how does Salesforce handle data privacy with agentic tools? Brown noted that Salesforce maintains a zero retention policy with its LLM partners, so conversations with an AI agent are not used to train models and are not retained once the interaction ends. The data stays the synagogue’s own, always.
One family, one record
Jordan then walked through a demonstration centered on a single family, the Goldstein-Levy household, to show what it looks like when religious school enrollment, bar and bat mitzvah preparation, and yahrzeit tracking all live on a single connected record rather than three disconnected ones.
On the religious school side, the portal showed that a parent’s two children were enrolled in their respective classes, complete with teacher assignments, class times, and self-service tuition payments. Staff sees the exact same enrollment record from the internal console that a parent sees from the portal, so there is no exporting, no syncing, and no risk of two systems disagreeing about who is enrolled in what.
The bar and bat mitzvah tracking followed the same logic. A console view showed upcoming service dates, assigned Torah portions, tutor assignments, and progress toward preparation milestones, all tied back to the same child record used for religious school. Nothing had to be retyped. It is one child moving through one congregation, viewed two different ways depending on who is looking.
Watch the full webinar below.
Timestamps:
0:00 Welcome and overview
4:17 What is Agentforce for Nonprofits
12:13 The full member lifecycle
16:50 Religious school and tuition demo
20:08 Bar and bat mitzvah tracking
24:08 Yahrzeit tracking and deduplication
34:02 Bulk year-end statement generation
42:19 Live Q&A
57:46 Closing and next steps
Yahrzeit tracking without the manual cleanup
The most striking part of the demo may have been yahrzeit and memorial tracking. Jordan showed how a family member can record an observance directly through a conversational interface, in Hebrew or Gregorian calendar terms, and the system automatically recognizes when that observance belongs to an existing memorial record, even if it was created by a different relative years earlier.
In practical terms, that means when three siblings each observe the same parent’s yahrzeit from three separate households, the name is read once at Kaddish, exactly as Halacha requires, without a staff member manually deduplicating a list by hand. Jordan estimated that this kind of manual reconciliation can cost a synagogue office more than twelve hours a year, time that gets returned to staff once the matching happens automatically.
Generating year-end statements in minutes, not days
Bulk letter and statement generation directly inside the platform was also demonstrated, without the need for a third-party add-on. Using a step-by-step wizard, he selected a giving statement template, set the fiscal year, previewed the full list of households included in the run, and generated tax-deductible, itemized annual statements for the entire congregation. What can take a synagogue administrator days to produce every January happened live in a matter of minutes, and the finished letter appeared instantly in the family’s own portal for them to view or print.
Where AI agents fit in
During Q&A, Mike drew a clear line between a traditional chatbot and an AI agent. A chatbot follows a fixed, predetermined script, similar to an old-fashioned phone menu. An AI agent, by contrast, understands natural language, works within guardrails that the organization defines, and can take real action, such as creating a record or logging a follow-up, rather than only answering questions.
Jordan connected that back to the demo, explaining that the Shamash agent he’s created and shown throughout the session is grounded entirely in the synagogue’s own Salesforce data and configured with defined topics and boundaries, so it reasons within a scope the synagogue controls rather than operating as an open-ended tool.
Answers to the questions synagogues actually ask
The Q&A covered several practical concerns that often arise when synagogue leadership considers a platform change.
Are bar and bat mitzvah preparation milestones customizable? Yes. Because the system is data-driven rather than hard-coded, synagogues can define their own milestones by program, whether that is a bar or bat mitzvah track, a religious school class, or another initiative entirely.
Does this require a brand new Salesforce org? Not necessarily. What was demonstrated is a customized experience layered on top of Agentforce for Nonprofits, and Fíonta can also work within an existing Salesforce instance, depending on a synagogue’s current setup.
How does Experience Cloud fit in? Experience Cloud is the portal layer that gives congregants their own lower-cost login to securely access their household’s information, whether that is enrollment, giving history, or yahrzeit reminders, while staff continue to work from the full Salesforce console.
Can a synagogue already on NPSP stay there, or does it need to move to Nonprofit Cloud? Mike Brown described this as a case-by-case decision. Organizations that have built extensive workflows on NPSP may have real reasons to stay, while Nonprofit Cloud now offers broader out-of-the-box functionality for fundraising, volunteer management, and program tracking without the need for separate installed packages. Fíonta has also built accelerators specifically to shorten migration timelines for synagogues moving from a legacy system or from NPSP.
Keep the series going
This was the second session in the Modern Synagogue Series, and it built directly on the first, which introduced the case for moving off disconnected, aging systems. Attendees who want to go deeper have a few paths forward, including a discovery call to discuss a synagogue’s specific needs, a live demo tailored to their congregation, a scope-of-work walkthrough with the Salesforce account team, or a broader technology review with Fíonta.
For more information, reach out to us through our contact form, and we’ll get back to you shortly.
