
A community contact record often needs more than a name and an email address. Family links, a Hebrew birth date and a Yahrzeit can help the team offer a thoughtful service. The quality of that service depends on the original information and on knowing which details still need confirmation.
Keep the original date and its context
When a family provides a civil date, record whether the time was before or after sunset if known. That detail can affect the Hebrew date. Preserve the original information rather than replacing it with an unexplained conversion. If the time or place is uncertain, flag the record for review with the family and the appropriate religious authority.
Yahrzeit observance can also require decisions for leap years or dates that do not occur in the same way every year. A calendar calculation supports the work; it should not silently choose a family’s religious practice. Have the relevant date and observance rule confirmed before scheduling a message.
Distinguish households from individual people
Two people can share an address or email while needing separate records, donation histories and communication preferences. Store the relationship between them without assuming that one person’s consent applies to everyone. Record who should receive a memorial reminder and how they prefer to be contacted.
For example, two siblings may want a reminder for the same parent, one by email and the other through a personal call. One shared memorial date can support two follow-up tasks without combining their donor identities. This is an organizational example, not a description of an individual customer.
Review a small set before enabling reminders
- Select a confirmed ordinary date and a date needing a leap-year check.
- Compare the displayed Hebrew date with the family’s information and a trusted calendar.
- Verify the person commemorated and each recipient’s relationship to them.
- Check reminder timing, language, channel and permission for that recipient.
- Preview the message and verify that a correction updates future follow-up as intended.
Make uncertainty actionable
A useful exception list says what is missing, who will check it and when it should be revisited. Avoid turning an estimated date into an apparently verified fact. After a family corrects a record, review already prepared reminders as well as the contact card.
Unisoft’s community management workflow brings contacts and relevant dates together. Ask the team to show your household structure, calendar needs and follow-up process in a demonstration. Keep access limited to people who need these details and collect only the information that serves the community relationship.