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.
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.
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
And Show It
Transcribed On Arrival
Into The Room, Not Into A Queue
After The Answer, Never Before
One Place To Watch It Land
The inversion
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.
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.
More from the blog
and what else shipped.
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.