We have always made renewals nice and easy by rolling over all of our patrons from the current season to the new season so patrons can just hit confirm and keep their seats. For our upcoming season, we are introducing a new subscription package which is essentially the same current package PLUS a new selection of programming that does not require seating.
I want to keep the ease of rollover for our patrons, but I also want them to get a push for the upgrade option while keeping their current mainstage seats. What is the best way to build this new package on the Tessitura side and what options do I have in TNEW to push for the upgrade while they're in the renewal path? I don't want the fear of losing their seats get in the way of patrons deciding to enhance their package. I want it to be perceived by patrons as an add-on rather than an entirely new package, but in reality, have it be one package on our end to facilitate rollover in future seasons.
I don't know if our model works exactly the same way as yours but we do offer a fixed seat rollover subscription with optional add-ons. To make it work, we have a unique subscription MOS designated in the LTR_TN_EXPRESS_WEB_DEFAULTS system table. This tells TNEW that this MOS is specifically used for selling packages, and will disable order checkout if there is not some sort of package in their cart. So we setup all our renewal orders to be listed in this MOS at the time of rollover. The subscribers are sent renewal links and are automatically asked to login and are shifted to this MOS. Then we have other single performances setup that are accessible in this MOS as well. We setup pricing rule messages to display for when a package is added to the cart. This can inform them of additional performance offers they can take advantage of right now. Then they can order single tickets to these performances along side their packages. Designating this MOS as the Sub MOS in system tables will prevent them from removing the package from their cart and checking out with just the add on performance.So technically, we are not altering anything in the packages, but offering the optional performances as single ticket add-ons. Not sure if that is the intent of your system or not, but hopefully it might give you some ideas.
I just remembered a possible issue we might have had. We only started using packages in 2018-2019, so with the pandemic, I could count the number of rollover seasons we've completed on 1 hand, so apologies for the foggy memory. I want to say there may have been a slight issue with rollover orders not triggering pricing rule messages in the same way that just adding a new order would. So it might be more complicated to inform renewing subscribers of their add on options. We are just now starting the rollover process, so we still need to build the performance/packages and then process rollovers before I can double check this issue to see if I am remembering it correctly.
Hi Jesse,I just wanted to chime and say that Pricing Rules don't work on rollovers, because it's technically a different path. I tested this a couple of season ago, and Tessitura confirmed it for me. Rosalie - we have a similar scenario coming up this season where once a customer renews their package, they're offered access to a couple of other special packages that are new this season. I'm facilitating this by providing a direct link to the package purchase page on the renewal order confirmation. Not super smooth, but it's the cleanest option I've been able to come up with so far.