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,
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.