Cross-Posted in Ticketing & Customer Service
My museum just upped our pricing for children. As a good-will thing (and to hopefully stop the potential pushback), we want to create a "Pay It Forward" option. We offer Free Admission to all on Saturday mornings, and a lot of the time patrons will tell us 'oh we want to donate what would have been admission to the museum anyway.' So we figured this "Pay it Forward" would get supplied by that.
However, I do not know of an easy way of doing this. Originally, I was going to create a Fee with a solid $10 attached (because the kids tickets are now $10) to accept the donation. Then when a family wants/needs to use it, I would create a ticket type in our GA performance labeled "Pay It Forward." That seemed simple enough until I realized we need a way of tracking how many we use, so as to not offer tickets we don't have.
We are currently creating a physical pass (a business card size) to hand to a family, who will then fill out the info requested and hand it back to our Front Desk staff. But I want a way in Tessitura to track as well. I can use a "Ticketing Fee Revenue" report, but is there a better way in real time for my Front Desk staff to know how many of those passes are left?
We recently switched to v16 if that makes a difference.
Do you want this to also be online or just for onsite? If only onsite, just make the new price type adjustable and set the price to $0. You can always adjust it up to $10 using the Price Details button.
If online also, do you use TNEW? If so, you can.
This is what it looks like on the website when a price type amount is editable (in between the red arrows – the red arrows do not show up on website).
To enable this feature online, the price type
Product Type Editor:
Component Editor:
But it does not work with Select Your Own Seat. So for performance venues it is not an option, unless you switch the whole performance to Best Available.
Sorry for "rubbing salt in that wound." I've now added that Select Your Own Seat exception to my notes. Glad you pointed that issue out, again.