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