Hi friends,
This season, we opted to move our subscriptions entirely to Mobile Tickets unless patrons specifically asked for Will Call. Our regular season performances are not starting until February, but subscriptions have been on sale since April 2021. We have our mobile tickets set up to send via email and publish on the patrons' TNEW account, but not until they have been "printed". I was not with this company when this set up was implemented, but I now need to find a solution for sending these mobile subscription tickets. A handful of our patrons utilize their TNEW accounts, but the majority are anticipating the mobile ticket email. Is there a way to send the mobile ticket emails in bulk? We have implemented the recent service pack that shows the E-ticket release date in Season Manager, but I am under the impression that will only work for PAH tickets, which I believe is a different template and wouldn't work with the orders set as Mobile Ticket delivery method. In an ideal world, I'd love to be able to send the tickets show-by-show, instead of sending the whole package at once.
As it stands, my best solution at the moment is to pull a list and have my ticketing staff work through it all manually, and hope for a better option when we're able to implement v16. Any suggestions would be greatly appreciated!
Hi Codashti,
I don't have a solution for you, but I am in the same situation.
Due to various reasons, we've decided step away from PAH tickets and go with Mobile Tickets. Everything is all set up and in place, the only final hurdle for us is that we don't want to send out the tickets until 2 weeks before the performance and we have some performances that were postponed from last year that were already partially ticketed and so we need to resend these in Mobile format.
Currently, the only way we can do this is manually order-by-order, but we're hoping for a solution to send in bulk in one go.
Since your post have you come across any developments on this? We're working on some customised scripts that we can run in the background to push these out, but I'm still holding out for a magical solution to show up.
Hi Emma,
Unfortunately, I did have to go ahead with the manual push, and the full package of tickets were sent. The process itself wasn't terrible. I pulled the Subscription Detail by Constituent report (I think), exported a CSV, and removed any extraneous info that they didn't need. I have a ticketing staff with 3 part-time and 1 full-time representatives, and they were able to push them all out over the course of two days. We only have about 900 subscribers this season, if that gives you any frame of reference.
It's been a rough transition for our patrons though. Many of them struggle to access the mobile tickets on their phone, either through the email or TNEW, the QR codes on mobile tickets won't print seemingly more than half the time because the patron needs to go into the print settings and check a box to show "background graphics," (which is not intuitive), and many times if they are able to access the ticket initially, they can't once they get to the venue either due to data/wifi signal issues or website errors. I understand that the implication of mobile tickets is that patrons shouldn't print them (or shouldn't need to), but it's not a very accessible practice to make them unprintable. We've done our best on the customer service front, and created a Will Call solution to help these people quickly at the shows, but I sure wish we didn't need to. It's one of our biggest pain points this season, which is a saying a lot with covid vaccine and mask policies in place.
Frustrations aside, if your scripts solution pans out, would you be willing to share an update once you've worked it out? And please let me know if I can help at all in preparing your organization for mobile ticket troubleshooting for patrons.
Thanks for your reply and for the info. It's really useful and I appreciate the shared feedback of the experience.
Happy to share our findings once we've cracked it. Our fallback at this stage is probably to send them manually as well, but we're looking at single tickets per performance and a large amount of numbers so am trying to avoid that if possible.
I'll let you know how we go :)