What is the best way to track seat change requests for a subscription campaign?
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!