Cross Posted in Ticketing & Admissions
So I have an odd issue that I don't know if Tessitura can solve.
Our Art Explorers class filled up and then some this weekend for the first time ever (we have been running this class forever, except for the 1-2 years during Covid). Anyway, I figured out why we over sold. It's the same problem we've always had where parents can go with their kids to this class if they want. Well, we only have 20 physical chairs in the room for the students, but we can have as many parents as we want (because they can just stand around the room for the hour). The problem is we have to get attendance numbers of the parents as well. So we have our capacity set at 20 because of the 20 physical chairs, but that means that adults are getting sold chairs in our current set-up (which is the set-up we had pre-Tessitura).
It was never a problem until now because this class was never this popular! It's a great problem to have; I just want to know if anyone else has this problem and how did you fix it?
What I would love for Tessitura to do is give me a capacity of 20 for our Child/Student price type, but then say 50 for our Adult price type. Is there a workaround for this?
Hi Chelsea, have you used allocations? You can specify that certain seats are only available to certain price types, just as you describe. We don't use them, but we almost did for something I can't remember so I read through the documentation. It involves changes to your facility, so be sure to try it in Test before pushing out changes (I've learned that one the hard way!).
Anne
We've never tried them. I will have to wait until our v16 upgrade to test it (end of January), but that sounds like a perfect fix if it works! I'll look into the documentation! Thanks!
They are in v15 and nothing should change with them in v16, so if you have the time you could test it before your upgrade.
It may be worth considering having a Student zone with 20 seats and an Observer zone with 50 (or whatever you'd like to call them). That would make it very easy to keep track of how many you've booked of each. The price types can be limited to each zone, if you need/want to report on it by price type. Alternately, if using a single price type might be desirable, you could also do that instead and then report on who's who based on the zone. Which would be preferable will depend on how you're reporting on other classes/things you might want to compare this perf to, and whether those other perfs might have similar limitations, etc.
setting aside a couple of seats for access (and labelling them as such if you are using TNEW) might help accessibility issues arising.
UX of booking distinct things within an order (allocations/zones etc) and what that looks like in the purchase path incl. confirmation, can be key to making these things work.