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
John,
That is very helpful! It seems like we might have the default setup in place. I checked someone who had returned a ticket on Monday (yesterday) and they were still being pulled into the list of "current" ticket holders, and their ticketing history still showed the returned concert. Knowing this, I will get a support ticket created to ask the procedure be updated for us. Thanks!
It may also simply be due to how often you have it running. Depending upon your organization and how many tickets you run, this can be a VERY time intensive procedure. I have ours running every night, but I believe some places only run it once a week. If so, that would again affect the results. Either way, yes, checking with RAMP is probably the way to go.
Hi Kari! We do not remove returned ticket lines from our ticket history, as it helps us with certain reporting options down the road. If a ticket has been deleted it is removed, but a printed and then returned subline item stays. However, those SLI's now have 0 seats. So if you use Ticket History Number of Seats, you should be able to weed out those that have been returned.
Hmmm...another good option, but it also looks like our ticketing history shows the original number of seats before the return as well. Looks like either way the best option is to have RAMP tweak our nightly procedure
Last but not least, I forgot to mention, when looking at ticket history, depending upon what you are intending to do to the list, it is always good to keep in mind the ticket history role, too. Someone could be on there as Initiator or Owner who never had tickets to the event but whose order is still active on the Recipient account.