Hi all,
We try to avoid the waitlist situation but sometimes it's inevitable and we would like to find a way of tracking requests through Tessitura.
If anyone could share their approach that would be really helpful!
Thanks
Daisy
What we do is start a new order for the constituent, add the amount of seats requested, but leave the order unseated. Afterwards, when it's time to contact waitlist registrants, we run the Single Sale Order Listing report for unseated orders to that specific performance. The report can be sorted by order creation date, so it gives us a very accurate list of who is on the list, how many seats they are requesting, and when they joined the waitlist-- plus an order is already set up and ready to go for if and when seats come available to be purchased.
Hope that helps.
Brett
Just wanted to say thanks for all your responses, it's given us a good starting point!
Hi Donna,
We've also used CSIs to track waiting lists and it's been pretty successful.
What we do is set up a CSI Activity Type called 'waiting list' and then set the Perf Ind to 'Performance'. That way when this type of CSI is opened the customer services rep has to enter the performance for which the patron is requesting tickets.
The CSI tracking report allows us to track which performances have requests.
The only downside to this is that an order isn't created at the outset and therefore the customer needs to be contacted to complete the transaction.
But, it's easy to set up and get going very quickly.
T.J.
Did you try any new ways of tracking waiting lists, and how did it work?
We sadly always have lots of people on waiting lists as we have so few performances. Often patrons ask to be on the waiting list for every performance of a particular opera, or for the whole season - so creating a CSI or an unseated order for each date seems like a long process. Any cunning solutions would be really helpful!
Thanks, Vanessa