Hello friends,
I have just started my R+D into this aspect of configuration, and as this is our first season using Tessitura I would love any suggestions or feedback to point me in the right direction.
One of our concerts this summer has an associated "Opening Night Dinner" gala event run by our development office. This gala is not on sale yet, but the performance tickets are. As such, invitations will be sent that offer a full "package" of admittance to the gala dinner plus premium seating to the performance for price t, and an alternate offering of admittance to the gala only (in the case that concert tickets have already been purchased) for price g (t minus concert ticket value).
We would like to be able to take full or add-on reservations through the box office, and offer the full offering with premium seating online (we are on TNEW). Our development office is not yet using Tessitura, but they will need reporting for all of the above described transactions.
My starting point for configuring this is going to be TNEW, since I have a good understanding of what I can and can't do with it. I don't yet have much experience with the development/contribution modules. As such, my plan at present is:
The box office would use the contributions module if they were processing gala only (g), and if they are doing so alongside some unrelated performance tickets, they would use an on-account pay method to bring money into the contributions module with only a single credit card charge. For "full package" tickets (t), they would use the special price type in ticket orders. This seems like it would be sufficient to take the required payments, but I don't know if it's practical to report on both of those things at once. Should I be thinking about using the t price type in ticket orders only for taking income, and after the fact using on-account to move the gala portion of income for ALL attendees into the elevated event?
Your thoughts are appreciated. Thanks,
-Nick
Hi Nick,
There are probably 20 different ways to do this and none of them would be incorrect, but here is my two cents. I would do the additional price type/price zone, but I would probably get the price by stacking two price maps, that way I could send the money that was for the concert to one ledger line, and send the money for the gala into another. This would make reporting a little more specific. I would also create a zone for gala only so that everything was being processed in the same place. I don't know if I would really use the elevated event structure other than to send invitations and keep track of attendance. Trying to track the same money in two places would be very difficult. In my experience, the more variables in place, the more likely someone in the box office will mess something up.