How do you dynamically pull a list of all ticket-buyers for an event including those who may have registered on the day you are pulling the list?

I am shocked that this isn't a very basic functionality, but no one seems to be able to give me a straight answer. To explain:

We have an event this Sunday. We're allowing people to register right up to when the event begins. We would simply like to be able to send out an email right when the event starts to say, "Hey, here's the link to the event!" I would like to schedule this email in advance.

Has anyone found a basic way to create a dynamic list of registrants for an event with emails? Every time I pull anyone with the correct ticket history, but because ticket history only updates overnight I have to then look at anyone who had done an order that day to see if their order was for the right event, and then I have to basically manually put the lists together. Surely someone has a solution! Will I just have to end up writing some SQL here?

  • Have you tried using the Order Export Utility located under Reports and Utilities to generate your list of emails for that performance?

  • Hm, I get an error here that I'm unable to pull it because I haven't filled in a certain Parameter that is not an option for me (so there must be something wrong with the way the utility is built in our environment I suppose?)

    But yes, this looks like a decent solution for pulling an event or several. However, we sometimes want to pull our class roster which is around 40 classes taking place over four days. So I'd either have to go through and select each one individually, or pull one day at a time using the performance start date and performance end date options.

    Although, I'm still left with the issue of it not being a dynamic email list I can set for the weekend. That being said, thank you very much for the help!! This will definitely make things easier for when I just need a few events!

  • Could it be that you didn't click the Next button and select/enter another parameter? Some reports/utilities have the Next button active and you need to enter/select additional parameters. Whenever I get an error I double check what I selected and check for the Next button.

  • Hi Robert, 

    I share your sentiment totally. We didn't realise this was a limitation for the ticket history criteria in dynamic lists until last year, when we had an issue with all of the event cancellation communications going out.

    The recommendation I received from Tessitura Support was to build a custom list element looking at the order line/subline instead of ticket history. 

    Unfortunately for us, we don't have those SQL skills in our team (I'm a total beginner), which means we're getting this quoted as a consulting task. I don't mean to piggyback, but needless to say, if anyone is willing to share codes/instructions to help with this, I'd be so grateful. 

  • Writing a bit of SQL into your list is an easy way to do that for scheduled dynamic lists (especially for curly things like cancelled performances where all the tickets disappear from the tkt history table).  If you need a hand writing any of that I'm happy to help. 

  • What a legend, thanks Heath! I'll email you about this soon :) 

  • Try this and exchange XXXX with your Prod Season No

    select distinct customer_no
    from T_ORDER o WITH (NOLOCK)
    Join T_LINEITEM L WITH (NOLOCK)
       on o.order_no = L.order_no
    where L.perf_no in (select perf_no
                                    from VS_PERF WITH (NOLOCK)
                                    where prod_season_no = XXXX)

  • This is amazing--thank you Heath!

  • Any time.  Using Show query in a list is a good way to get your toes wet in SQL and do those tricky or rare lists that need a bespoke solution.  If it comes up a lot &/or there are associate data you want exposed (like a show name and date for an email output set) then a Local View is a good investment. 

  • Thank you so much for posting this question! We're hoping to set up triggered emails in Wordfly for our performance reminders, and need to be able to capture that day's sales - especially for virtual events where folks are buying very last-minute. We don't have SQL skills on our team but this is all very helpful info!