The display itself
Composed once, published to the branches you choose.
Queue and counter displays
Which counter,
and how long.
A queue display answers two questions and removes most of the reason people approach a desk. ScreenQube publishes and monitors the display across every branch.
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.
How it is made
What is actually behind it.
Named against the product's own modules rather than invented for a marketing page.
-
The layout is a composition
Token panels, counter numbers and the waiting list are artwork arranged in Composition.
-
Published per branch
Each branch is a facility with its own screens.
-
Counter information as content
Which counters are open, and what each one does, published on a schedule.
-
Monitored like every other screen
Active and disconnected counts on the dashboard.
What you get
Six things it does today.
Counter hours and closures
Published on a schedule, with an end.
More than one language
Part of the composition's rotation.
Per branch
Publish targets facilities.
Outage counting
A dark queue screen is a headline number.
Change history
Audits, with a name against each action.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Can it call tokens from our queue system?
Not that we can evidence. No queue-system integration has been observed in the console. Ask us and we will get a direct answer.
What can it do for a branch estate today?
Publish and schedule counter information to every branch, monitor which screens are active, report on playback, and audit every change.
Can each branch differ?
Yes. Publish targets the facilities you choose.
What runs on the screens?
An Android player app on displays you own.