Hi all. We sell a mixture of fixed and flex packages yearly. Our Classical fixed packages are 18, 9, and 6 performances and Pops are 9 or 6. In the past, the Classical 18 has been challenging to get to print-at-home. We are looking to set print-at-home only for all of our packages and I'm wondering if any of you have any advice, experience, or pearls of wisdom to share. Will this lock up our PAHT server if we send masses of subscription PDFs at once? Currently, we do not utilize composite tickets, so it's one PDF per performance/seat.
Thank you in advance!
Heather
Are you on v15 or v16? Is it feasible to make the switch to Mobile Tickets instead of PAH? We've been sending Mobile Tickets for packages since 2021, and it's gotten much easier in v16, but was still doable in v15. It was a downside for me that all season tickets would send in a single email in v15, but you can set it to release show-by-show in v16 if you want. Mobile tickets can still be printed from the email they receive.
As to the stress on the server, I know you can limit the number of orders that pull to send at a minute interval in TR_MOBILE_TICKET_CONFIGURATION, but that same field doesn't appear to be in the PAH configuration table.
Thank you for your response! We are on v15 and not sure when v16 is happening. Mobile Tickets are on the docket for us, we are not set up currently. It sounds like the best solution. Am I correct in that you do not use composite tickets for the mobile tickets for subs? Once you integrated Mobile Tickets did you do away with the print-at-home delivery method?
I appreciate your help,
Hey Heather,
Prior to 15.1 (for us 12 months ago) we would send out the whole sub as PAHT. With 16 Productions and big groups that could be huge. Good luck finding your tickets in that pile.
From 15.1 we got access to PAHT delivery on the line-item level which saved us a lot of subs package issues. It was mid-season so it caused a couple, but we needed to do it for our move to hosted. We renamed our PAHT delivery to a Delayed delivery method. and set the timing to 52 hours. I have our docs (plagiarised from the Help docs) if you want them.
Either way getting your PAHT template as small as poss. was a key. I think you can find discussions over the years on the forums that file size over maybe 20Mb could cause delivery issues.
Mobile tickets are the wish list option.
We do not use composite tickets, but I will note that we only have 4 productions in our season currently. The mobile tickets send as an image in the email body itself, so for a 16 show series, that would be a really long email if they are all sent together. Unfortunately, delayed delivery for Mobile tix isn't available til v16, as far as I'm aware. Heath's delayed delivery suggestion for PAH seems like it might work better for you right now. We haven't used PAH since we made the switch, and quite a bit has changed since the last time I was at an org that did use PAH.
Thank you for this Heath. I think we've decided to get Mobile Tickets rolling. If that turns out to be delayed I may ask you for your docs. We keep our PAHT PDFs to about 30-48 KB, we'd had that problem in the past. As always, thanks for your advice!