Not Just One, but Many — on Statement Runs

Modest change here — having to do with your periodic statements.

One of the selection criteria on statement runs had been the ability to select all families, or one family:


With this change, you can now select multiple families or all:

Probably the most advantageous circumstance where this would be useful is this: Suppose you primarily send statements by email. The system dutifully warns of any families who would have received a statement, but for whom the system has no email address.

Before, you would proceed by selecting the first family and printing the statement. Then, you would select the second family; and so forth, one at a time.

Now, you can select all the families for whom there is no email address, and obtain printed statements in one step.

Here’s a video that illustrates the above.

By the way, if you want to see a series of articles about the various developments concerning statements, please peruse this collection.

New Field — Community per Family

What do we mean by the term “Community?” Families often live in what can generically be referred to as a community. For example, a senior living community. Or, an apartment community. Or, a Home Owners Association community. It’s just a way to group families by a geographic area, more local than zip code.

Now, how might you use this new field? By first designating the communities in the Configuration menu

you can then assign these communities to the respective families who reside there.

And, then, to harvest that information, you can either

  1. Run a family query for one or more communities, or
  2. Run a member query, to list all the people in those communities.

For example, suppose you’re running a Purim program at one of the senior living communities. By using this new field, you could send a targeted email, announcing the event, to members of that community.

Here’s a video showing how to enter the communities, and then how to query both families and members, by community.

New capability — to acknowledge pledges

Adding to the existing ability to acknowledge payments in bulk, we now have the ability to bulk acknowledge pledges.

If you’re not families with what we mean by “bulk acknowledge,” please view this article.

That works handily for recognizing payments of any kind. Now, we’ve added the a button to sent several acknowledgements for pledges, or any amount owed, for that matter. For example, you may want to sent email thank-you notes after a pledge drive, or after people have made commitments to a building campaign.

The procedure is the same as before — it stars with Queries -> Financial transactions. Then, you’d likely select a date ranges; and, perhaps focus on a designated set of categories

New is the light blue button to bulk acknowledge pledges (actually, any type of amount owed).

Here is a video to view the end-to-end process

Direct Link — Member Portal to Shopping Cart

Now available — a direct link from the member portal to the shopping cart.

Some basics — if you’re unfamiliar with the member portal, it might help to view this video.

The ShalomCloud shopping cart provides a way for your community to purchase items (including zero-cost items), and sign up for events. Examples include Shabbat dinners, Rabbi classes, Lulav and Etrog, concerts … quite a variety.

In the last step, where the user goes through a check-out process, there’s a form to fill out. As described in the shopping cart tutorial, ShalomCloud uses the demographic information in that form to identify the buyer, and to attribute the purchase to a family known to your synagogue — or to create a new family unit, if none of the info matches anything in the system.

What is new about this announcement is that, if the congregant first logs into the member portal, a new button will appear. That button will launch the shopping cart. Furthermore, when that person enters the check-out, all the demographic information will be pre-filled. Name, email, phone, physical address. Thus, no need to repetitively fill out known data–as long as your congregant first logs into the member portal.

Video demonstration