We are launching our subscription campaign with one title TBA, and have built it in Tessitura as "Holiday Production" to mask the title from both patrons and staff who have not been informed of the title. We will announce the title in mid-August, but by then we will be through the major subscription push, as well as the start of single ticket sales. So there will be paid, seated orders in this production.
When we announce the title, we will change the Production and Production Season names, as well as the Description, Short Name, and line 1 of ticket text within each performance build. We will also make any necessary changes in our TNEW build.
We have never had to do this before, but I imagine someone else has. Could this possibly cause any issues with a patron's ticket history? We are on v12.5 and using the standard ticket history and subscription history. Ideally, once we make the change to the individual performances, I'm hoping that change is reflected in a constituent's ticket history, but am unsure if that will happen. Is there anything else we need to be wary of, from those who have been through a similar process before?
Thank you!
Hi Kim,
We also use the standard ticket history and have to update production and performance titles after sales have occured. Last season I used a shared report from TASK called "Performance Description Update" which worked really well and kept me from having to update each performance individually. We also didn't have any problems with our ticket history either.