A printed square instead of a call box
Post a code where people need help. Someone scans it, a channel gets the request, whoever is free takes it.
Why a code rather than hardware
A call point that costs a sheet of paper can go in fifty places. One that costs a tablet goes in two, and the two are rarely where the problem happens.
- No power, no mounting, no device to be stolen or go flat
- Different codes for different locations, so the request arrives with its context
- Reprint to move it; revoke to retire it
One scan, one clear request
The scanner opens a branded page in their camera browser. There is no app, account, message form, microphone prompt or location permission between them and asking for help.
- The page checks that somebody on the response channel is online before it offers the call button
- It confirms when the first teammate accepts and gives the scanner only that responder’s first name
- A lost connection resumes the same request instead of ringing the team twice
A public request, not an encrypted message
A member of the public has no channel key, so the request is deliberately kept outside member conversation history and labelled as an operational QR Assist event on both sides.
- It stores the assistance point and lifecycle times — no name, free text, microphone data, contacts, device location or IP address
- The link the visitor gets is random, expires quickly, and cannot be worked backwards to anything about them
- The private channel and staff roster are never exposed to the scanner; rate limits and immediate revocation protect a code posted in public
The first available teammate takes it
The channel you chose gets the request straight away, at the desk and on every handset. Two people can tap at the same moment without both thinking it is theirs — only one of them gets it, and the other is told.
- Waiting and accepted requests stay visible above the responder’s current screen
- Whoever helped marks it done, and it clears from everyone else’s list
- Console shows live workload, response time, outcomes and the last fourteen days of activity
Put the first call point where help gets lost
Create a point in Console, assign its response channel and print the poster. The code keeps the same address until you retire it.