Counter and service information
Which counter does what, and which are open.
Government and public sector
Public notices,
current everywhere.
A public office runs the screens that decide how long someone thinks they have waited. Counter information, service notices, wayfinding and entitlement information — published to every office from one browser, with a record of every change.
Plans, prices and trials are set by your ScreenQube partner.
Where it ends up
You work in a browser.
They see the wall.
The screen above is what you publish. This is where it ends up — a display a customer stands in front of, driven by a player that fetched it on its own.
What goes on the screens
Six things worth putting up.
Every one of these is ordinary media, arranged in Composition and sent out by Publish. Nothing here needs a separate system.
Notices and entitlement information
The printed sheet, legible, current, and changed in one place.
Wayfinding
Floors, departments and accessible routes.
Service changes and closures
Published on a schedule, with a start and an end.
Multiple languages
A composition can carry more than one language; the rotation is part of the content.
Safety and emergency notices
The notices that must be visible in a public building.
Where the screens go
Four walls that earn it.
-
Entrance and queue hall
Wayfinding first, then what to have ready before reaching the counter.
-
Counter line
Now serving, and which counter to go to.
-
Waiting areas
The longer content people have time to read.
-
Staff and back office
Internal notices on the same estate.
How it is run
Four steps, then it runs itself.
The same four steps whether you have four screens or four hundred. This is the real console, not an illustration.
-
Add facilities, pair screens
One facility per site, branch or building. A screen joins by showing a registration code, which you type in once. Switch between facilities from the header.
-
Upload and compose
Media goes into the library, in folders, with tags. Composition arranges it into zones — your own files, plus App Store apps like weather, news or a ticker.
-
Publish three ways
On a schedule, with day sequences. Or QuickPlay, which the console describes as displaying content instantly for a flash sale or an emergency. Or as the default composition a screen falls back to.
-
Check it, without going there
Live Monitoring reports each screen's state. Take Screenshot shows what one is really displaying. Reload, clear the cache or reboot it remotely.
What it fixes
The three complaints we actually hear.
- Each office prints its own notices and none of them match.
- One Media Library, in folders, and Publish choosing which offices see which composition.
- An audit asks when a public notice was changed.
- Audits records every create, update and delete with the person who made it.
- A screen at a district office has been dark for a month.
- Live Monitoring counts disconnected screens per facility.
Set it up as
The solutions this usually becomes.
Nearby
Other industries with the same problem.
Questions
What government and public sector teams ask first.
Can it call tokens from our queue management system?
No queue-system integration has been observed in the console. Screens are published from the Media Library and Composition.
Can content be restricted to one office?
Yes. Each office is a facility, and users belong to groups that decide what they can reach.
Is there a record of who published what?
Audits logs created, updated and deleted actions with the person responsible.
Can it be hosted on our own infrastructure?
On-premise hosting has not been confirmed. Ask us and we will get a direct answer.
Put it on every screen.
Talk to us about becoming the partner who sells it.
We will introduce you to the partner who covers your region.