We're planning to pivot from having one daily general admission to timed admissions so that we to keep the number of visitors at a safe level inside. We're trying to figure out how to keep track of people leaving so that the number of people inside does not gradually go beyond our new limited capacity and we don't oversell to unsafe levels.
I'd like to hear how other organizations are handling this, or what plans you are making.
Thanks.
Standard NScan functionality scans a ticket on exit. You can control how many people are in at any given time.
I'm looking at the documentation now- thank you for that!
Is there a way to set an amount of tickets that are allowed (by the system) as 'In' house?
Nathanael Pearson Wouldn't a venue capacity control how many tickets are allowed?
I'm not sure what you mean by 'venue capacity'- for General Admission facilities, the capacity of any one zone might not be (and usually wouldn't, I think) be the total on-site capacity. We have GA zones of 1100 set up currently.
If Customer A and his 1099 friends all check in for one of our Admission Zones, they'll all get marked as attended. If they stay past their two-hour time, and Customer B comes along (in a different time zone), NSCAN will still mark him as Attended, but he'll be taking up a seat in a new zone, which has a new capacity. We'll then have 1101 total people on campus, and NSCAN will mark them all as attended.Is there a way within Tessitura/Nscan to set up limits on how many people can be marked as 'attended' in any one performance, when that performance is broken up across multiple zones?
I see. Maybe manually control the limits by running a SQL query to count 'exited' tickets?