Over the past six months, ShalomCloud has delivered several key features designed to enhance user experience and streamline administrative processes. These updates focus on improving email communication flexibility, financial transaction visibility, and preventing payment errors. Some of these features may not have had an individual blog post; hence, we’ve gathered these topics here, in one article.

Community Field Now Available in Email Templates

Our most recently requested feature has arrived – the ability to include the “community” field in your email templates. (If you’re not aware of the “community” field, please review this blog post.) Previously, users could customize emails with various merge fields, but community designation wasn’t among them. Now, administrators can incorporate community information directly into their communications, allowing for more targeted and relevant messaging.

This enhancement is particularly valuable for organizations managing multiple communities (e.g. HOA associations, senior living facilities). Communications can now be automatically personalized based on community affiliation without manual intervention.

Enhanced Financial Transaction Visibility

We’ve improved the financial transaction posting page by adding a total-owed calculation underneath individual line items. This simple yet effective addition provides instant visibility into the overall financial picture while processing individual transactions.

This feature addresses a common pain point where administrators had to manually calculate totals when reviewing accounts. Now, the system automatically displays the cumulative amount owed, saving time and reducing the potential for errors during financial processing.

Smarter Recurring Payment Protection

Our third recent enhancement focuses on preventing accidental overpayments when setting up recurring payments. The system now includes intelligent validation that compares the recurring payment amount against outstanding balances.

When an administrator attempts to create a recurring payment that would result in an overpayment, the system now displays a warning notification. This proactive approach helps organizations maintain financial accuracy and saves both administrators and members from dealing with refund processes.

Deceased Indicator for Yahrzeit Observers

We’ve added a new visual indicator within the Yahrzeit management system to clearly identify which observers are deceased. This thoughtful enhancement helps administrators avoid potentially sensitive mistakes when sending Yahrzeit notifications or planning memorial events.

The indicator appears directly in the so-called Combo Bimah List (and corresponding spreadsheet export), making it immediately clear which family members should not be contacted. This feature reflects our understanding of the delicate nature of Yahrzeit observances and our commitment to helping organizations manage these important traditions with appropriate sensitivity.

Here’s a full article on this topic.

Customized Acknowledgement Email Recipients

Acknowledgement emails can now be directed to specific household members based on their family role. This granular control allows organizations to ensure that financial acknowledgements, donation receipts, and other important communications reach the appropriate family member.

Administrators can now configure email preferences based on family roles such as primary contact, Adult1, or other custom designations. This enhancement respects family dynamics while ensuring important documents reach the right individual.

Article on this topic.

Customizable Secondary Address Terminology

Understanding that different organizations use different terminology, we’ve added the ability to customize the phrase used for secondary addresses. Whether your organization prefers “Seasonal Address,” “Alternative Location,” or another term entirely, you can now configure the system to reflect your preferred terminology.

This simple but impactful change helps maintain consistency in your communications and creates a more familiar experience for both administrators and members.

Mass Attribute Assignment from Family Query

Finally, we’ve streamlined the process of managing family attributes by enabling mass attribute assignment directly from the family query screen. This powerful feature allows administrators to select multiple families based on search criteria and apply attributes to all selected records simultaneously.

This enhancement dramatically reduces the time required for bulk updates and ensures consistent attribute assignment across your database. Whether you’re tagging families for event invitations, special communications, or reporting purposes, this feature makes the process significantly more efficient.

Previous post on this topic.

These updates reflect our ongoing commitment to making ShalomCloud more intuitive and efficient. We continue to prioritize enhancements that directly address user feedback and streamline critical administrative functions.

Perhaps you’ve made use of the ShalomCloud Combo Bimah List. This change is an additional nugget of information that you may add to that list.

If there is a relationship, where the related party is also deceased, this change allows you to denote that fact with an acronym, or phrase, of your choice. Could be OBM, or z”l, or A”H — whatever is customary in your congregation.

For example, using this option, a line on the combination Bimah list would look like this:

And, how do you take advantage of this option? Start with Home => Declare synagogue options. Under Choices and Preferences, you’ll see a collection of terms that you can declare. The new one is called “Term for deceased.”

Here’s a video demonstration of what’s described in this article:

When producing donation acknowledgements by email, you may have noticed that the recipient seemed arbitrary. May have been adult 1…may have been adult 2.

With this change, you can choose, based on the field we call “role within family.”

How does that work? Under Configuration -> Roles Within Family, you likely will see something like this:

Role within family	Display order
Adult1	10	Show	Edit	Destroy
Adult2	11	Show	Edit	Destroy
StatementTester	33	Show	Edit	Destroy
Minor child	60	Show	Edit	Destroy
Adult Child	62	Show	Edit	Destroy
Deceased	99	Show	Edit	Destroy

With this change, the person attached to the role with the lowest numbered display order will receive the acknowledgement email (provided, of course, that an email exists for the individual).

Here’s a video showing how this works. The video also shows how to view and change those roles.

By the way, the video mentions a technique to acknowledge several contributions from one screen. If you’re not familiar with that capability, please review this blog article.

There is now a new selection on statements, namely a “not” attribute.

In our quest to continually provide you with more flexibility, we’ve rolled out quite a few more options for producing periodic statements, over the years. To summarize here, those options have included:

• Choose your email template when sending statements.
• Include or suppress payment details.
• Include or exclude credit balances.
• Select a subset of categories (e.g., school-only).
• Include or exclude a recent-payments section.
• Select statement recipients by family/household attributes.

This is yet another of those incremental improvements. In regard to those attributes — you can now select by households that do NOT have a certain attribute.

Couple of examples where this might prove useful.

• Your standard is to produce statements by email. However, you have some families who expressly want a paper statement only. In that case, you might set up an attribute, “Surface mail only.” Then, when your embark on your standard statement run, you can select Does not have attribute Surface mail only.
• Your standard practice is to run statements monthly. In contrast, a few families want this communication quarterly. Accordingly, you’d set up an attribute, such as “Quarterly.” Then in your monthly run, select Does not have attribute Quarterly.

Here’s a video depicting this idea in motion.