Hi everyone -
Has anyone successfully figured out the setup to use order information for criteria sets? We want to send out another email to patrons with a cancelled concert, ideally suppressing out people who have returned their tickets? Currently, if I just use Ticketing History, that still includes people who initially purchased this concert and then subsequently returned their tickets. Their ticketing history still shows as them having the concert (I'm assuming this is the way it's supposed to work?).
If I can use order information, that might make it easier to identify patrons to suppress (in more or less real time).
Thanks in advance!
Kari,
Comparing ticket history between organizations can get you into a bit of hot water pretty quickly, since there are many different custom approaches in play.
For my own understanding, and, given the way our organization has its ticket history procedures set up, though, no, returned tickets are NOT left on the patron's account. Once the ticket is returned, that history line is removed. Now, that said, it is a procedure that we have running nightly. Which means that if I pull the list at 5:00 PM on Tuesday, all of the tickets that were returned that Tuesday will still be on that list. That is a list and an e-mail that I am going to want to pull and send on Wednesday morning to make sure it covers everyone.
But you may have things set up differently. If that is not how you are seeing your results, and you are using, as far as you know, the standard ticket history functionality, I would check with your database manager and/or RAMP.
Best of luck!
John
I suggest trying the Order Export Utility and pull for SEATED orders only, that should only return orders where there are valid seats. You cannot save the results as a list directly,(at least I haven't been able to do it) but you can save it as a CSV file and then import it into Tessitura as a list. From there you can use that list however you need.
Good Luck!