Hello there!
We are beginning the process of rolling out PAH ticketing and are discussing situations where we would not want PAH to be applicable.
In reading the documentation and other forum posts it mentions that orders with many tickets should be excluded as it may cause the email to either not send or not be accepted by the recipient's email because the attachment is too large.
What have other PAH users found to be an approximate threshold for number of tickets in the same order starting to cause problems?
We also know that composite ticket designs are an option for subscriptions (though that is a bigger and different discussion we will have to have later). Does anyone have examples of their own composite tickets they could share with me so i can show the group some different ways this has been accomplished? They are curious to see how others have made composite tickets work and what level of detail they were able to accomplish in such a small space. Please feel free to email them to me directly if you are willing to share!
Thanks!Bethbhawryluk@winspearcentre.com
Hi Beth - We set our limit to 8, without too much data to back it up :D
Hi Beth,
We don't use composite tickets, but with our normal events we tend not to send anything out that has more than 10 tickets in the order.
We also have logos on our tickets, so we make sure that the PDF's are as compressed as possible, without loosing quality, as the size of the original template will affect the limit of what can be done.
Caryl
Beth,
We don't limit at all. We do however ensure that our ticket designs are small in size to begin with so that once all the pieces are added they come in under 100KB when complete.
We've sent attachments as large as 6299 KB which represented 77 tickets.
The issue we have come across is that we can send, but the constituent's email provider cannot receive.
Michele
Thanks for the responses! I just had a lightbulb moment when I was reading them and realized that obviously the number of tickets we can send is going to be determined by our ticket design size. I feel so silly now for even asking. :)
But on a related note then, how do you prevent an order with too many tickets from selecting PAH as the delivery? If, for example, we determine that 10 tickets is our max based on our design size how do we prevent someone with 12 tickets from selecting PAH and risk not getting their tickets? I know we can set ticket limits online but that is related to the performance and not the order (to my understanding anyway). So if they have multiple shows then they could exceed the PAH limit. I'm not seeing any kind of "max tickets" flag in the PAH documentation. Am I missing something?
Our limit is set by our custom web code, so it looks at the number of tickets in the order and if it's over our max it doesn't present PAH as a delivery option.
We do the same for certain price types and seating areas too (so if it has a price type we say can't be PAH it won't offer PAH for that order regardless of if every other ticket in that order qualifies for PAH)