One of our subscription-heavy resident groups has recently had us set up a flex package. They're used to seeing the subscription summary screen. With a flex package order, they are unable to set the season or status.
Is this normal? Is something set up incorrectly?
A flex pkg is not recognized as a subscription in Tessitura because they don’t have the same day/time/seats. For reporting you’ll want to use the Package Sales Summary not the subscription reports.
Shelley Salinas
Box Office Manager
COCA
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of David Crowell Sent: Wednesday, June 26, 2013 10:22 AM To: Shelley Salinas Subject: [Tessitura Ticketing Forum] Flex Package and Subscription Summary
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Ticketing Forum. You may reply to this message to post to the Ticketing forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Thank you, that clarifies things.
Any idea if this is still the case 5 years later? Or if sub summary can be utilized for Flex packages?
Hi Michelle. It is still the case that flex packages do not use the subscription summary screen.
Thanks for confirming Michael. I was planning to use sub summary to track renewals, new subs, upgrades, downgrades etc., but am rethinking since it wont work for flex. Do you have any other recommendations? Order category?
Hi Michelle,
We use lists and constituencys to track our flex patrons.
A few options come to mind:
Order Category is a useful high-level field because it's included in the Order Search screen and a few reports. You could use this to label orders that need action, and reset the field to (none) or another value when complete. The values come from TR_ORDER_CATEGORY.
The Special Request screen is available for all package and performance line items and includes a notes field, a category dropdown, and other seating request fields. This can be useful if you want to use the notes field for a specific purpose separately from the order notes field, and when there is a lot of products in the order.
Customer Service Issues can be configured to require the selection of a package (specifically, in TR_CUST_ACTIVITY_TYPE). This can be part of a workflow where you record some notes that require action, review open actions with the View All Customer Service Issues screen, and then mark them closed when completed.
And as Amber mentioned, constituencies are a great way to mark subscribers in general, and you might want a special constituency for these folks. The Manage Constituency utility can be scheduled to automate the application and removal of constituency codes based dynamic lists of constituents with the flex package in their Package History.