Hi all,
We generally have a pretty strict e-ticket release date of one week before a performance across all modes of sale, but have started to get requests from group bookers to send tickets earlier in order to facilitate their larger bookings, and are happy to allow this on an occasional basis. Is anyone aware of a way to force send e-tickets before the MOS release date, ideally by order?
Obviously we could create a new Groups MOS and set their release dates to be earlier, but this would mean applying it to all groups when many seem happy with the standard one week.
Any insights are appreciated!
Thanks!
Isaac
Hello,
Well, my suggestion was going to be essentially what Annabel Robson is doing, just more specifically. If I wanted to do that for specific group orders, I would simply create a second Group Sales MOS that is otherwise identical to the first (same price types, performances start/end dates, pricing rules, etc...) but with an immediate delivery date for e-tickets. Then, if one group calls in and asks for their tickets to delivered separately, and whatever business rules you have in place would allow that, you just change the MOS on the order from the first Group Sales MOS to the Immediate Delivery Group Sales MOS. That would allow all group reporting to remain consistent, and you would be able to force immediate delivery for any specific order while leaving the rest alone. You WOULD have to add that second MOS to all existing and new builds, but that should not be too bad.
Now, this is an okay idea for a specific option like "Group Sales". But I can certainly see how this would be annoying if you wanted to create the ability to do this for ALL modes of sale (Box Office, Web, Sponsor, Donor, etc...). Creating a second MOS for a specific use case makes sense. Doing that for all MOSes would get annoying fast. But I otherwise have no other great ideas for getting around that particular thing.
Best of luck!
John A. Moskal II
Interesting, and timely. I have to test ticket design for a show that has 24 hr delivery, and was trying to figure out a way to print just my test tickets, but not release all tickets that we sold in that MOS. So I guess I could mimic everything in the MOS I sold my test order in, creating this new MOS, and then just go in and change the MOS of the order. I was leery to test it out as I didn't want to accidently unleash all e-tickets, and of course did not have enough lead time prior to the on sale of the event to test things out properly.
For this particular situation we have a specific testing MOS that is always set to have immediate delivery of etickets!