At Norfolk, we allow subscribers to have a Pick 5 or a Pick 3 concert subscription. We offer flexibility in the fact that for instance, 2 tickets to one concert plus 4 tickets to another concert acts as 2 Pick 3 subscriptions as well. However, this does not translate into tessitura so we have been putting in the individual concerts and labeling the price type as a subscription. This causes issues in Tessitura because these people do not show up as subscribers although we consider them to be. How can I set up this in Tessitura so that it is more flexible in this, and the reports that are run show up more accurately?
Hi Carol,
Unfortunately there really is no way to circumvent the requirement that all performances in a package have the same number of seats. I think the way you are currently handling your offerings is the only way to handle them. Solving your reporting issues comes down to custom reporting that counts those single tickets as subscriptions. Hopefully some other users will have some suggestions for you on how to handle the reporting, as I’m pretty sure you aren’t the first organization to use single tickets for a non-traditional package situation.
Keeping track of those tickets as package revenue is pretty simple to do with standard reports based on GLs and price type categories. Grouping them into distinct packages is more tricky and would require some custom work. Identifying the constituents who buy those packages as subscribers shouldn’t be very hard using price type, though I suppose that depends on if you want to count them on a report or find them for a list or extraction. If it’s the later, you just need list and extraction criteria that looks at price type, which if you don’t have already should be pretty simple to add. If you wont to identify them for reports, that goes back to the custom reporting need.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
1 888 643 5778 ext 329 Office
ksheehan@tessituranetwork.com
If the pricetype you use for these subscriptions has the pricetype category "subscription" then for the purposes of if not most, then at least a lot of reports the tickets would show as subscription, regardless of whether they were ever in a package. I'm not sure what you mean by people not showing up as subscribers? If you have a subscriber constituency that gets applied by a scheduled job you may want to revisit that script and make sure it's referencing people with tickets that have that price type category, rather than packages. Or if the subscriptions are not showing up in your local subscription history table, again revisit the script that populates that and make sure it's grabbing people with tickets with the subscription category instead of referencing the existence of a package.
For our "compose your own" packages (minimum of 6 but can choose across all our performances during the year, venues, price reserves etc) We set up a flexi package and buy the number of concerts within the package, we also add a "dummy" performance that we use to do our rollovers each year so that we can generate renewal forms for our "compose your own" subscribers.
We use specific pricetypes, CYO Adult, CYO conc etc... and they are in the category of "subscription" so the package information pulls out on our reports., our Finance Department are happy with this.
Maybe what would help is having just the "dummy" package element in your order and adding the extra performances as line items.
Then you could have the SQL job that runs overnight to update constituencies looks for this dummy package as well.