Ticket design Element- Tot Tickets Purchased

Former Member
Former Member $organization

I'm having an issue with our Header cards.  Aside from the standard format of constituent data, someone decided many years ago to include the number of tickets in the order as well.  They've done this by inserting the "Tot Tickets Purchased" data element from the "Orders" data group into space at the bottom of the header card and labeling it "Total Tickets".  

This works well for new orders with only purchased tickets in it.  The problems come up when tickets are returned and reseated in a new line item in the same order.  Every returned ticket adds a tic to the "Total Tickets."  Instead of a patron having just two tickets, their header card shows four tickets.  Two of them from the return and two of them from the new tickets.  This confuses the patron into thinking we've charged them for four tickets and not two.

I could add another element to the header that shows the number of tickets returned with the "Tot Tickets Returned" data element, but that would require the patron to MATH.  I don't want to be liable for the head injuries that may result from this, so I'm turning to the forums for help.

How can I display, on a header card, the total number of tickets in an order minus the total number of returned tickets in that same order?  I'd like to have it formatted into one field that I can label as "Total Tickets" on the header.  

The header has the correct information.  The patron doesn't have to math.  I don't get sued for resulting injuries.  Everybody wins!  Your help is much appreciated.

Parents Reply Children
  • We just moved to Tessitura and our legacy system would print on the header the amount of tickets that were actually being printed. IE: if there were 10 seats on an order and we were only printing 2 the system knew that only 2 tickets were printing and would print "Number of tickets: 2" on the header. This is important for us because the majority of our tickets are will call so now our CSRs have to count the tickets in front of the guest instead of just looking at the header.

    We also  could void printed tickets in our legacy system if we hadn't hit done on the order yet. IE: Guest says I'll go ahead and take those, the CSR prints the tickets and then the guest says well actually let me leave those at will call. As long as the CSR had not hit Done on the order you could hit escape and it would ask you for a void password, a supervisor could enter the password and the order would still be in the system but the tickets would show as not printed so they would print with a batch the day of the show.

    Thanks,
    Daniel Williams

    Box Office Manager
    Flat Rock Playhouse

  • Former Member
    Former Member $organization in reply to Daniel Williams

    We have this information there for the same reasons, Daniel.  In addition to that, we have volunteers that assist us with putting together all of the season packets to mail out during the summer.  The total number of tickets on the header helps them to know that the ticket bundle is correct and that nothing is missing.  When that number if off, our box office reps have to look into the order.  Nine times out of 10, the tickets are correct, but the header count is wrong.  

    Figuring out how to have the total amount of tickets show correctly on the header would save us a lot of time and headache. 



    [edited by: Owen Craig at 9:57 AM (GMT -6) on 22 Aug 2016]