I was looking at some constituents where we've returned seats and I noticed that those folks are no longer in Ticket history which makes sense. But that means that when we are building marketing lists for years to come we are going to have to find another way to find patrons that bought those shows. I guess we will have to remember to pull those lists by SLI Status? Something to think about.
As soon as we went work from home we pulled the order export for all of our upcoming shows for this reason. We've had this issue in the past, but you can still pull the information from the back end.
Hi Gregory -
As you pull lists to contact ticket holders about cancellations, you might consider adding a Constituency or Attribute to those lists (using the related utilities to add the attribute in bulk). This would help easily identify these groups for future marketing use.
Thanks,
Patrick
I really wish there was some way to apply a "refund reason" as we can specify for comp price types.
We've pretty much had to refund at least one show a year as long as I've been working here: originally it was usually foreign artists having their visas revoked for dubious political reasons, of course occasional artist illness, but now we're pretty much guaranteed an climate change based natural disaster every season, which typically affects multiple events, and the smart money suggests that we should anticipate pandemic waves for easily another year. At least now we've finally gotten some kind of utility for real mass refunds (although too late for us to use it this time). But we've always suffered from losing information about refunded shows customers, and had to do manual SQL pulls to try and get mailing lists for those. If instead we could have been flagging every one of these refund events ("2019 Wildfires #2"), and also other events that are considered refunds in Tessitura ("Ticket Exchange"), then we would have a lot more power to work out the ramifications of these events after the fact, pulling accurate metrics for doing reconciliation, for instance (a huge chore, as I have to try and distinguish between normal exchanges and event cancellation refunds).
Hi Gregory. We wanted a triggered email to those folks who would have come to the show to commiserate with them and give them some content and a message from our Artistic Director.
I whipped this up and pasted it into the "show query" section of the list. I've put notes in the where column. Now this will also show anyone who has a subline item in the perf including the refunds and exchanges pre COVID. That was ok for us but if you wanted them out you could fiddle with this code a little. You could also find people from the Payment table but I went with this and it worked.
Cheers,
use impresario
SELECT
DISTINCT a.customer_no
FROM T_ORDER_SEAT_HIST AS a WITH (NOLOCK)
join VS_PERF AS p WITH (NOLOCK)
on a.perf_no = p.perf_no
where
prod_season_no = 725 --current Productionand p.perf_dt between getdate()-1 and Getdate() -- today's showand customer_no is not null and customer_no not in (SELECT customer_no from T_list_contents where list_no = 11589) -- Donorsand customer_no in (select customer_no from T_CUSTOMER where cust_type in (1,7) and inactive = 1) -- individuals and households onlyand p.perf_no <> 769 -- excluding closing night