Wondering what the common practices are for this. Some common examples:
Consider that all orders are purchased in advance and held at will call. Some of the challenges that arise:
We book the tickets under the constituent record of the person purchasing the tickets, then use the Custom Data tab in the order to add Collecting Customer name, which is then included on the header.
Hi Nick,
Thanks for starting this conversation. We've recently started requiring ID upon pick-up and are thinking more about this.
So far we've done as Sarah describes and used a field in the Order Custom tab to enter Hold Under Name. Now that we're in v12, for some organization records where the order is booked under the group constituent, we've used the Initiator field for the individual who will be picking up the tickets (assuming we are given that information), and we print the Initiator on the header instead. I've created a custom user-defined Header element that looks first for an Initiator different than the Order Owner, then for data in the designated Custom tab field, then, if finding both those blank, prints the Order Owner name.
The problem we encounter is that the data in the Custom tab and the Initiator field applies to the whole order. Many constituents book multiple productions at once and the person picking up may not be the same for every lineitem in the order. Or they may not yet know at the time of booking who will be using the tickets.
The new recipient field on the sub lineitem seems like an obvious solution, but the need for the recipient to have a Tess ID slows down phone operators and begs questions about creating Tess IDs for constituents for whom we don't have good contact information.
Looking forward to hearing from others.
Frannie
We went with a simple approach of using Order Notes as "Booking Contact information" so that customers booking online can nominate a name and contact number of someone authorised to collect tickets on their behalf. It obviously only works at the entire order level, rather than drilling down to sub-line items.
The main benefits are that the order notes field is right there for the operator to see when it comes time to print out the tickets, and it was really easy to implement online. It obviously doesn't allow the audit trail of Owner/Initiator/Recipient, though!
Hi, Frances. I know this is an older post, but I was wondering if you'd be willing to share your coding for your user-defined Header element that checks for initiators? I have an organization asking for just that and I imagine it would be popular with others in our consortium. Thanks in advance!