One of the big tasks ahead in the Next Generation project is redefining all the ways in which a constituent relates to other constituents. Today we call this Associations and we know that it doesn’t begin to cover all the bases. So just as we have in the past, we need you to help us out with your thoughts on any or all of the following questions:
1. What are the ways that constituents relate to one another, particularly ways that aren't so easy to track in Tessitura today? 2. What are some scenarios that describe ways that your business needs to communicate with different segments of related constituents? (A simple example: “Sometimes I need to send a mailing out with only one piece per household. But if I’m doing the same promotion in an email I need to send it to all the members of the household.”)3. One of the things we struggled with in designing Tessitura the first time was the whole name1/name2 construct. Is there a reason to treat spousal relationships differently than any other type of family/household relationship? 4. What other questions need to be asked about this topic?
I like what Ryan had to say on this. One record per person and records are linked in different ways. I envision a relationship circle of some kind where there are different levels of "closeness". For example a spousal relationship could be a level 1 relationship (very closely linked) and that would result in a specific rule set for those two records (e.g. they only get one appeal letter instead of two etc.).
Level 2 relationships could be family or friends, level 3 work or professional etc. Imagine the sun surrounded by planets with the individual at the center and other individuals around them at different distances. Each organization could decide which specific associations are at which level. For example specific family, employment, board relationships could be level 2 or level 3. Level 1 would be reserved for only the closest of relationships like partner/spouse or even brother/sister living together etc.
Ok, I'm getting too nebulous.
Specifically answering one of Chuck's questions. One thing that is currently difficult to manage in Tessitura is email preferences when you have multiple email addresses for both N1 and N2 and both N1 and N2 have different preferences. For example N1 wants enews sent to his home address and all other emails to his business address while N2 wants enews sent to his work address and special events emails sent to his home address.
Dale