I understand the recommendation is to keep transactions on the household in v11, but there are some arguments within our organization for putting them on the individual affiliates instead. Can anyone weigh in if they are doing this, and with any pros or cons either way?
Thank you!
Before I get started - We are not on V11 yet and don't have any hands on experience to point us down one path or the other yet. :)
We also have some situations that would lead us to want to put transactions on the individual account rather than the household account. One specific scenario (that comes up way more often that you'd believe) is that many of our patrons want to be treated as an individual and separate their transactions from their spouse's transactions. This is how we ended up with many duplicates in our old ticketing system. We would have 3 (or more) accounts for each household. One for Mr John Smith, one for Mrs Jane Smith and one for Mr and Mrs John and Jane Smith. Depending on the situation, any one of those accounts could be used for a ticket purchase.
From looking at the V11 sandbox it looks like you can see the ticketing history for the individuals in the household record and can see the household ticketing history in the individual records. So I *think* (though I could be wrong) it wouldn't be the end of the world to choose at the time of the transaction whether it should be on the household or the individual account based on the customer's preference.
Perhaps once we have upgraded our test environment to V11 and have had some time to play we will have a much clearer understanding of what the appropriate choice for us will be.
Thanks everyone for your responses – I appreciate it! We’ve decided to follow the common wisdom and keep most transactions on the household in v11. We too have some patrons who want to keep their transactions separate from a spouse/partner so for those I think we’ll flag the household account and leave specific instructions in a CSI.
Another situation we frequently encounter now is when N1 and N2 have different last names, tickets automatically get filed under N1 and if N2 made the transaction it can cause confusion (and sometimes irritation on the part of the patron). I’m wondering if the Swap A1 / A2 feature would work as a solution, but maybe that would create headaches that I can’t even think of now. Does anyone know what the ramifications of using the swap feature are?
Thanks again!
We have not played with the swap feature extensively, but I do wonder if it will solve your specific problem. If I order tickets today and keep them at will call. You have made my account A1 so that they will live at will call in my name, but what happens when tomorrow my husband calls and orders tickets and you swap the names again? My will call order has not printed yet so it will now file under my husband's name.
We have created a will call header that can print specific notes left in the order notes. It seems like this would be a better solution to leave order specific name instructions.