What is the best way to track seat change requests for a subscription campaign?
We started using CSIs this year and it seems to have worked well. We are trying to move away from relying on paper forms for the change process, so this year we did both the CSI and the form as backup. There were times when the paper form had more information than the CSI, but my guess is that if there is no paper form to rely on, then the CSI will end up with all the info needed. We used activity types and origins to sort out what kind of change a patron was requesting, and the CSI date was set to the order date for processing changes in order.
We use a combination of the upgrade mode, special requests and the subscription summary. In the upgrade mode, we attach a package for the new request and/or new price section. If the price is likely to change we will make the upgrade line primary so the price on the subscription order reflects what we believe the new price will be (especially if it is likely to be higher in price.) We add as many upgrade lines as necessary depending on the request. We then use special request to track the actual details of the request – aisles, no steps and any detailed notes as necessary. The special request are line item specific so you can have multiple requests depending on how many line items in your order. Finally we use the Subscription Summary Type to track if it was a renewal with changes, renew the same or a new order. We then use Subs Summary Status to track a basic change request (like change-center) and then update it if we can improve them or not. The subscription summary is mostly for tracking after the fact.
The package seating report works with the upgrade mode to run lists of who needs changes but it doesn’t always work the way it is supposed to for me I have found. There is documentation on the procedures I have outlined in Package Processing document.
Elizabeth Carlock
Director, Ticketing Services
The Granada Theatre
From: Tessitura Ticketing Forum [mailto:forums-ticketing@tessituranetwork.com] On Behalf Of Brian O'Neill Sent: Wednesday, July 06, 2011 7:22 AM To: Elizabeth Carlock Subject: [Tessitura Ticketing Forum] Tracking Seat Change Requests
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!
We also use CSIs to do this.We have one category for changes that need to be made before we rollover and one that we use for current renewal requests.Another option would be to use 'Special Requests' which you can find information on in the Package Processing-Renewals Sales and Printing documentation.
Thank you everyone for your wonderful feedback! I will definitely be setting up CSI's for seat changes next season.
We too use CSIs. We like that the info is kept in the constituent record and can be easily accessed when needed and compared to previous seasons. We run various CSI reports when we're doing the reseating and fill requests from there. The lack of a paper form hasn't been a problem for us really, but a hard habit to break for sure!