How CrowdSense looks from the control room, not from a sales deck
At 21:00 with three queues building, you need one number you can say over the radio. This is written for that moment, not for the demo.
Who this is for
Venue managers, event ops leads, control-room operators, and the person who already owns the radio net and the run of show.
The first demo is the control-room view and the companion app, on a layout like yours. If a number is not radio-friendly we will not put it on the wall.
What the first event actually looks like
Not a rollout plan. The shape of one event, done properly.
- 01
We map the radios, not the product
Who calls occupancy, who calls queues, who can open a lane. CrowdSense has to fit that net. We will not invent a new channel you have to staff.
- 02
The wall shows what you can act on
Occupancy by zone, gate throughput, queue time at the pinch points you named. Pretty heatmaps stay in the debrief unless you ask for them live.
- 03
A trial weekend with your crew, not ours pretending
Your operators on the companion app. Your language on the labels. We stay on comms for the first one, then we get out of the way.
- 04
The debrief is for the next event, not for us
Where the plan was wrong, which gate was early, which zone sat empty. You already know most of this in your gut. The numbers let you change the site plan with the producer, not argue about it.
Questions we will actually ask
These are the same questions in the demo form. We ask them because the answers change the kit, the room, and who needs to sit in.
We will ask
What do you currently look at when a queue builds?
CCTV, a steward at the fence, a guess. That tells us what “better” has to beat, in your units, not ours.
Question 1
We will ask
In-house crew or contracted, and how many on radio?
A six-person net and a sixty-person net need different alert noise. We will not page everyone for a gate that is merely busy.
Question 2
We will ask
Where does the control room actually sit?
A proper room can take a wall. A hatchback takes a phone. We will not design you a video wall you cannot house.
Question 3
We will ask
What must never go on a public screen?
Safety numbers, medical, anything that would move a crowd if it leaked. Crowd-aware signage is optional and gated. Default is ops-only.
Question 4
Straight answers
Will this add another screen I have to watch?
Only if you want a wall. Most event managers live in the companion app and a handful of alerts. If your control room is already full, we will not fight for pixels.
Does it work when the site has no reliable phone signal?
Yes. Off-grid communications is a product we already run, not a future promise. Tell us in the form if the site is a paddock, a basement, or a tunnel. That changes the kit, not the conversation.
Can security and medical see the same occupancy I see?
Yes, with the same numbers and the same zone names, on their own logins. We will not give medical a different occupancy to the one you are calling on channel 1.
What if I am not the person who signs the contract?
Say so. Bring the producer or the venue owner to the second meeting, not the first, if you want a clean ops look before the commercial one. We will not bounce you to sales in minute five.
What do you collect about the people in the crowd?
We measure crowds, not people. Our sensors count and classify — they do not identify. No facial recognition, no biometric identification of people. Ever. What leaves a camera node is counts and events, not video.
Rather talk it through first?
Book a time and your answers come with you, or call the office line. Either way you get the person who reads the enquiries.
Talk to a person
Wesley Pearson, Managing Director
It's in Brisbane right now.
“You will get a reply from me within a business day, and a straight answer if we are the wrong fit.”
Book a time
Tell us about the event, in your words
The form is seven short steps. A person reads it. If you would rather talk, book a time.
