• Replies 4 replies
  • Subscribers 416 subscribers
  • Views 98 views
  • Users 0 members are here
Related

How does your organization do tickets purchased and picked up by different people?

Nick Reilingh
$organization

Wondering what the common practices are for this. Some common examples:

  • I am an artist purchasing tickets for a number of different guests.
  • I am a donor purchasing tickets for a friend.
  • I have a ticket that I can't attend in person, but I am sending some friends instead.

Consider that all orders are purchased in advance and held at will call. Some of the challenges that arise:

  • Simply having the guest pick up will call using the name of the purchaser is easiest, but breaks down when the purchaser has many different guests for the same performance. (Or if your organization requires ID to be presented to pick up tickets.)
  • Tessitura requires payments to come from the order Owner; this is also the name printed on the will call header.
  • Using the person to pick up tickets as the order owner, charging someone else's card will add that card to the wrong person's constituent record.

Parents
  • $organization

    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

Reply
  • $organization

    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

Children