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

Say it. Don't type it.

Somebody standing in front of a problem can describe it in fifteen seconds of speech. Ask them to type it and they will give you six words and a spelling mistake, if they finish at all. Reporting now takes a voice message and photos.

whoot. team · September 2026 · 6 min read

Clip length
≤110s
Photos per report
4
Photos per alert
8
Audio
16 kHz mono
  • Record up to 110 seconds straight from the browser, with no app and no account
  • Every clip is transcribed automatically and summarised for the operator reading it
  • Voice messages land in your team's room as radio traffic, not in a queue nobody watches
  • On a live alert the recording is kept first and processed second, so nothing is ever lost
Sheet 1Emergency Response · September 2026 · 6 min read
TimeFromEntryAction
Sep 2026

whoot. team

A text box is a bad interface for somebody with one free hand.

Typing is the wrong ask at exactly the moment you most need detail. The person reporting is outdoors, holding a phone in the rain, maybe walking away from whatever worried them, possibly frightened. What comes back is “man acting weird by gate 4”, and everything that would have made that report actionable, what he was wearing, which direction he went, whether anyone else was with him, stays in the reporter's head.

Speech does not have that problem. Fifteen seconds of talking carries more usable detail than two minutes of thumb-typing, and it costs the reporter almost nothing. So both public reporting pages now take a voice message and photos: the “report an issue” page behind your QR codes, and the private response page that every emergency alert links to.

The recording does not sit in a folder waiting to be listened to. It is transcribed on arrival, so it is searchable as text and readable at a glance. A short synopsis is written for whoever picks it up, what is being reported, where, and any urgency in the speaker's own words, along with flags for abuse or a message that is obviously not a real report. That summary is decoration on the recording, not a replacement for it: the audio is always there to play.

And then the clip goes where your team already is. An issue report lands in a transmit-only room you nominate when you build the form. During a live alert it lands in that alert's own room, arriving next to your team's own radio traffic, transcribed, in sequence. Nobody has to remember to go and check a queue, because the report reaches them on the channel they are already listening to.

Detail

What it does

Fifteen seconds of speech, handled six ways.

What happens between somebody pressing record and an operator acting on it.

Hold The Button, Say What You See
  • Record up to 110 seconds in the browser, with no app and no account
  • The mic is only ever asked for at the moment somebody chooses to record
  • Clips upload as they finish, so every state on screen reads sent, never attached
And Show It
  • Up to four photos on an issue report, up to eight during a live alert
  • Each one is downscaled on the handset before it leaves, so a weak signal still works
  • Photos open in a gallery beside the report or on the incident's own media tab
Transcribed On Arrival
  • Every clip is transcribed automatically, so a report is searchable as text
  • A short synopsis is written for the operator: what is being reported, where, how urgent
  • Warning flags mark abuse or a message that is plainly not a genuine report
Into The Room, Not Into A Queue
  • An issue-report clip lands in the transmit-only room you bind to the form
  • During an alert it lands in that alert's own room, beside the team's radio traffic
  • The sender is an external party record, never a user account somebody has to be given
After The Answer, Never Before
  • On a live alert the recorder appears only once someone has reported their status
  • Nothing about media sits on the path between opening the link and "I need help"
  • Per-alert switches decide whether photos, voice, or neither are offered at all
One Place To Watch It Land
  • The Active Incident media tab lists every photo and clip as it arrives, newest first
  • Filter by kind or by person, and play a recording inline without leaving the incident
  • The list keeps polling on its own, so a dropped connection never freezes the view
Design

How it is built

The recording is the evidence. Everything else is decoration.

Mid-incident, the failure that matters is not a missing transcript. It is a person who recorded a message about where they are trapped, saw an error, and gave up. So on the response page the audio is stored and the record written before anything clever is attempted with it. Only then is the clip handed off to be transcribed and delivered into the room.

If the cluster is busy, or the summariser is unreachable, the clip is simply marked as awaiting its transcript and your team still gets a recording they can play. The reporter is never told, never blocked, and never asked to do it again. The same reasoning is why the response page carries no CAPTCHA at all: the cost of a challenge is somebody injured failing to reach “I need help”, and no amount of abuse prevention is worth that trade.

  • During an alert the recording is stored first and processed second
  • Transcription, summarising and delivery to the room are all best-effort decoration
  • A busy cluster or an unreachable model marks the clip and moves on
  • The person in the emergency is never shown an error or asked to try again
  • A failed upload keeps the audio on the handset and offers one calm retry
  • The response link is the credential: no CAPTCHA stands between somebody and help
End of sheet 1Back to the top

A report page can afford to reject a bad submission. A person trapped in a stairwell cannot afford to be rejected.

So during an alert, nothing is allowed to fail.

The two pages run the same recorder over deliberately opposite contracts. On the public reporting page a clip must pass its checks before it is accepted. On the response page the recording is kept the instant it arrives, and every other step, transcription, summarising, delivery into the room, is allowed to fail quietly behind it.

Keep reading

More from the blog

Emergency Response

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

A public reporting page behind the same QR code your sign-up links already use. Anyone can report a chained fire exit, a broken barrier, or behaviour that worries them. You write the questions, and every report lands in a triage queue where your team sets priority and owner.

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

Fifteen seconds of speech. Everything you needed to know.

Voice messages and photos on your public reporting page and on every emergency response link, transcribed on arrival and delivered into the room your team is already in. Start a free trial and try it on your own site.

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