Skip to main content
whoot.
Venues & eventsIncident managementMartyn's LawPricingFeatures
Sign inStart free
Venues & eventsIncident managementMartyn's LawPricingFeatures
Sign inStart free

The people who see it first don't work for you.

A contractor notices a fire exit chained shut. A visitor watches someone try three car doors in a row. Neither has your number, your app, or any idea who to tell. So they tell nobody, and the first you hear of it is afterwards.

whoot. team · September 2026 · 6 min read

Account needed
none
Question types
5
Triage states
5
Priority levels
3
  • Public reporting on the page your QR codes already open, with no app and no account
  • You author the question set: categories, location, and anything else you need asked
  • Reports arrive in a triage queue with priority, owner, status, and a full activity trail
  • Priority is set by your team, never by the reporter, so the queue sorts by risk
Sheet 1Emergency Response · September 2026 · 6 min read
TimeFromEntryAction
Sep 2026

whoot. team

Most of what goes wrong is seen by someone with no way to tell you.

Every site has a reporting gap. Staff have a radio, a room and a supervisor. Everybody else has nothing: contractors, visitors, delivery drivers, stallholders, the crowd. On the days that matter most they outnumber your team by a wide margin, and they are the ones standing next to the problem.

The usual answer is a generic email address on a sign, which works about as well as you would expect. Nobody has their laptop, nobody remembers the address, and what does arrive is a paragraph of prose that somebody has to read, interpret, chase and remember to close. A reporting channel that costs effort to use gets used after the fact, by which point it has stopped being a report and become an incident review.

So reporting now lives on the page you already point people at. The QR sign-up link that puts somebody on your alert list can carry a second, entirely independent section: Report an issue. Scan the code, answer your questions, send.

The two halves of that page do not depend on each other in either direction. Somebody who never enters a phone number can still report. Somebody who signed up ten minutes ago can report without doing it again. And when the recipient list behind the link reaches the end of its date window and stops taking sign-ups, reporting carries on regardless. A list window decides who gets texted. It has no business deciding whether a hazard can be reported.

Detail

What it does

From a code on a gate to a named owner.

Six things the reporting page does between somebody noticing a problem and your team closing it.

The Code Is Already On The Wall
  • Reporting rides on the sign-up page your QR codes already open
  • No app to install, no account to create, no login to remember
  • One printed code now does two jobs: join the alert list, and report a problem
Your Questions, Not Ours
  • Build the question set yourself: free text, single choice, multi-choice, number, location
  • A live preview beside the editor renders the real page a visitor will get
  • One form can serve several links, and reporting works on the plain unbranded page too
Where, Precisely
  • A location question takes a typed answer: north stand, level 2, by the lift
  • Optionally offer a one-tap browser position alongside it, with its accuracy recorded
  • Category and location fill the queue's own columns, so a report is sortable on arrival
A Queue, Not An Inbox
  • Reports arrive in Security Ops as new, acknowledged, in progress, resolved or dismissed
  • Priority is low, normal or high, and your team sets it, never the person reporting
  • A notification deep-links straight to the report that raised it
Someone Owns It
  • Assign a report to a named person with a typeahead, and unassign as easily
  • Reporter contact details can be hidden, optional or required, per form
  • Self-declared details are labelled as unverified, because that is what they are
A Record That Holds Up
  • Every answer is stored with the question it was actually asked
  • Editing a form later never rewrites what an earlier reporter was shown
  • Status changes, assignment and resolution notes build an activity trail per report
Design

How it is built

Open to everyone. Not open to everything.

A page that anyone on the internet can post to needs its limits designed in rather than bolted on. Access is the unguessable link itself, a CAPTCHA challenge, and rate limiting on both the reporter's connection and the link. Generous enough for a whole venue sharing one network, tight enough that a queue cannot be buried.

It is also, deliberately, not an emergency channel. Your own wording sits at the top of the form telling people what to do if somebody is in danger right now, and the queue describes itself the same way to the team working it. Emergencies belong on the alert path, where the response page, the roster and the incident map are waiting.

  • Reporting never depends on signing up: no number entered, or already entered, both work
  • It keeps working after a recipient list's own date window has closed
  • A list window decides who gets texted; it does not decide whether a hazard can be reported
  • Access is the unguessable link, a CAPTCHA challenge, and rate limits, not an account
  • Your own emergency wording sits at the top of the form, so nobody uses it to call for help
  • The form is separate from your brand templates, so an unbranded page can still take reports
End of sheet 1Back to the top

A public form where anybody can tick “urgent” sorts by confidence.

Yours sorts by risk.

Reporters describe what they saw. Priority, ownership and status are set inside Security Ops, by people who can see every other report on the site that day. It is the one decision that keeps a public queue usable past its first busy afternoon.

Keep reading

More from the blog

Emergency Response

Say it. Don't type it.

Reporting a problem now takes a voice message and photos, not just a text box. Speak into the page and the recording is transcribed, summarised for the operator triaging it, and dropped into the room your team is already listening to. The same controls appear on the incident response page mid-alert.

Emergency Response · September 2026 · 6 min read

Read the post

Emergency Response

One tap says "I'm safe."

Every emergency alert now carries a personal response link. It opens in any browser with no app and no account, records a one-tap status reply, shares live location with consent, and displays operator updates the moment they are posted. Your dashboard tracks every reply in real time.

Emergency Response · July 2026 · 5 min read

Read the post

Emergency Response

Live location. On an actual map.

During an incident, people who consent can share their position, and the incident map comes to life with live pings, movement trails, and a what3words square for every location. App users can share continuously in the background, with a pause control that is always one tap away.

Emergency Response · August 2026 · 5 min read

Read the post

Sheet 2Sign-off
Today

You

One scan to join. One scan to report.

Author your question set, attach it to a sign-up link, and the next person who scans the poster can tell you what they have just seen. Start a free trial and have it live this afternoon.

Signed
Date
Start free trialBook a demo

14 days · full access · no card

whoot.

Push. Talk. Heard. Incident and crowd management for venues, events and operations, built on an always-on voice core.

  • whoot. on LinkedIn (opens in a new tab)
  • whoot. on Instagram (opens in a new tab)

Product

  • Features
  • Incident management
  • Pricing
  • Roadmap
  • Documentation
  • iOS app (opens in a new tab)
  • Android app (opens in a new tab)

Use cases

  • All use cases
  • Venues & events
  • Incident response
  • Financial services
  • Operations teams
  • Trader voice
  • Martyn's law

Company

  • About
  • Case studies
  • Blog
  • Investors
  • Contact
  • System status

Legal

  • Privacy
  • Terms
  • Acceptable use
  • Security
  • Accessibility

© 2026 Eager Lobster Ltd, trading as whoot. Registered in England and Wales, company number 17038042.

Registered office: First Floor, 1 Des Roches Square, Witan Way, Witney, OX28 4BE. Prices exclude VAT and other applicable taxes.

all systems operational