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?
The Academy at Colorado Ballet is currently making the switch to household accounts and is struggling with credit card relationships.
Most of our credit card info is housed under the student (individual) level. Now that they're affiliated into households, their credit card info doesn't seem to be accessible. It would be easier to not have enter in a credit card in three-four places (household level, A1 level, A2 level, and student level). But we also don't want to make credit card numbers insecure (i.e. having an A1 access a card number not avail to A2), but we'd like an option to select individual credit card numbers when in a household order. If there's a trick around this now, please let me know!
Thank you!