The ticket, the service and the required documents,
on your office screens

The turn by transaction orders the swamped room. A council or agency office mixes very different transactions, and one queue clogs. Calling the turn by type of transaction, each queue with its own letter and QR code, orders the room and lowers the tension: the citizen sees their queue moving, and all by number, without exposing any personal data.

When someone goes ahead of the queue, the room needs to know why. Priority access is written into the law, but the person who has been sitting for forty minutes does not see the law: they see someone going ahead of them. That is where almost all the bad feeling in a public waiting room comes from — not from the delay, from what looks arbitrary. A separate priority queue with its own letter, so the screen calls P-003 rather than what looks like a jump, does the job no clerk should have to do out loud: explaining, ten times a morning, that it was not a favour. The rule ends up written on the wall, and a written rule gets argued with far less than a decision that looks like somebody's.

Digital eases the counter. Many transactions do not need to be in person, but the citizen does not always know it. Informing about appointment booking and access to the online services in the office itself directs to digital what can be done from home, and frees the counter for whoever truly needs in-person help. And the legal notices up to date meet the required transparency.

To be straight with you: we do not integrate with internal government or council case-management systems. The screen shows the turn — by number, with no citizen data — the transactions, the documents and the notices uploaded; to call the turn it uses its own queue — tickets taken by QR code and called from a staff phone — not an existing ticket machine. Digisini is the citizen-service screen layer.

What tends to close the gap without reversing the policy:

• A way to book from inside the building. A terminal, or simply staff who can make the booking on someone's behalf. The barrier is rarely the internet itself; it is doing it alone.
• Stating the alternative where it is needed. A phone number displayed at the entrance helps the person who is already at the entrance. On the website it reaches somebody who did not need it.
• And publishing the wait, not just the process. "Next available: eleven days" lets someone decide whether to keep trying today. Silence sends them back tomorrow.

There is a measurement problem hiding underneath, and it explains why this persists: the people affected are invisible in the data. They do not appear in booking statistics because they never managed to book. The system reports that online booking works, and it is correct about everyone it can see.

Which means the number worth counting is one nobody usually collects: how many people arrive without an appointment and are turned away. That figure is the size of the gap, it is countable at the door with a tally, and until someone counts it the assumption stands that it is small.

Count for one week how many people arrive without an appointment. If it is more than a handful a day, the booking system has a second entrance and nobody has designed it yet.

Nine o’clock, the doors open on thirty people. Council Tax arrears, a housing question, two blue badge renewals and a man who has been told to “come in with ID”. The red ticket machine by the entrance has jammed again, and security is handing out numbers scribbled on scraps of paper.

A QR code on the welcome desk gives each matter its own line. T for Council Tax, H for housing, G for general enquiries: each letter has its own code. Residents scan the one that fits, tap “Take a number”, and their phone shows the count of tickets in front and an estimate drawn from how quickly that desk is genuinely moving — so a parent can take the toddler outside rather than pacing the foyer. When an officer presses “Next”, the screen calls “H-009 → Desk 4” with a chime. People who don’t own a smartphone, or would rather not use it, are handed a ticket at the desk, same queue, same order. Setting up the QR queue.

No reference number, no data required. The ticket is just a number, which suits a public body that would rather not hold anything it doesn’t need. The optional name field stays off unless you turn it on, and even then it never reaches the screen.

To be straight with you: the queue doesn’t book appointments, prioritise vulnerable residents on its own or link to your CRM — officers decide. The phone alert needs the page open.