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.
I'll lend my voice to this as well- we're looking for ways to keep track of visitors on-site.
I'm also interested! I'm working on building timed ticketing, but wondering if there is a way (assuming we count people leaving) to integrate that data easily into Tessitura besides simply adjusting holds manually.
Hi all,We encountered the same questions and have put the following solutions in place. We are lucky that our building is quite large, so this might not work for you, but wanted to add my two cents.1. We are switching to timed ticketing. Each one of our slots has a max capacity and when we add up the total tickets across all slots, this total does not surpass our maximum capacity at one time. So, for example, if our max capacity is 500 at a time, and we have 3 time slots, we have 167 tickets in each time slot available. 2. We are staying nimble and only releasing a week or two of tickets at a time. Therefore, if we are selling out, or have lines that are too long, we are prepared to add time slots, increase capacity, and come up with a different formula as things continue to change quickly.3. We have 'Sensource Cameras' installed on our doors. These currently track the number of entries to the building. We will continue to use these for entries and also are exploring getting them setup for exits as well. This is a bit of a backup system if ever we were concerned about ticketing for some reason.4. I believe NSCAN has the possibility to do exit scanning...we considered going down this route, but simply don't have the staff resources available right now to have additional people scanning...and it would also add another 'touch point'. We might look back at this option once Tessitura releases some of the proposed self scanning pieces.
More than willing to discuss more with anyone if you have any questions :)
Standard NScan functionality scans a ticket on exit. You can control how many people are in at any given time.
It can scan out? How do you do that? I was just told yesterday that there isn't a scan out option!!
https://www.tessituranetwork.com/Help_System/Content/N-Scan_Application_Guide/Exit%20Mode.htm
Got it, thanks so much! It looks like it doesn't update Tessitura, just an Nscan table--but maybe that data could be used somehow!
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?