Welcome and expected visitors
Published for the day, by the team that owns the diary.
Visitor and reception
Named before they
reach the desk.
A visitor screen does most of a receptionist's first thirty seconds: welcome, where to go, what the rules are, and who is expected. Self-service sign-in is a different capability, and this page says so.
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.
-
A reception board is a composition
Panels, rules and welcome messages arranged once and published.
-
Expected visitors as published content
Names for the day, published by whoever holds the diary.
-
Per building
Each building is a facility with its own screens.
-
Restricted publishing
Groups decide who can put a name on a wall.
What you get
Six things it does today.
Site rules and induction
The notices a visitor has to see before going further.
Where to go next
Wayfinding beside the welcome.
Practical information
Wi-Fi, assembly points and who to ask.
Per building
Publish targets facilities.
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 visitors sign themselves in on the screen?
Not that we can evidence. Touch interaction has not been observed in the console.
Can it notify a host?
No.
Can we show the day's expected visitors?
Yes, as published content — arranged in Composition and published to the reception screens.
What runs on the screen?
An Android player app on a display you own.