A call button anywhere you need one
Someone in aisle nine needs help. A button on the wall reaches whoever is free, wherever they are on the floor.
The problem it solves
In a large space — a store, a ward, a plant — the person who needs help and the person who can give it are rarely in the same place, and neither wants to go looking for the other.
- A fixed call point puts the request where the need is
- The request reaches a channel, so whoever is free answers rather than a specific person being paged
- Response times become measurable, which is the part that lets you actually staff the floor properly
How it works now
An administrator creates a QR Assist point in Console, assigns the channel responsible for that location and prints the poster. The public address remains stable until the point is retired.
- The scan page checks that the team is online before the visitor can send a request
- Everyone on the channel is alerted at once, and the first person to take it gets it — the others are told it is handled
- The visitor sees acceptance and completion while the operation gets response-time history
The public boundary is explicit
A visitor cannot be issued a member device key, so QR Assist does not pretend its public request is an end-to-end encrypted channel message. It is a separate, tightly bounded operational event.
- No visitor name, message, microphone access, contacts or device location is collected, and no IP address is stored with the request
- The scanner never sees the channel id, channel name, staff roster or account identifiers
- Short-lived hashed browser capabilities, rate limits, pause and revocation contain a code posted in public
Start with the place people already ask for help
Create the point, print its poster and route it to the team already responsible for that part of the floor.