Announcements that land
A screen does not need to be opened.
Employee communication
Reach the people
who are never at a desk.
Most internal communication is written for people with an inbox. On a production floor, a ward or a depot, the screen on the wall is the only channel that reaches everyone on every shift.
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.
-
Written centrally, published locally
One composition, published to the facilities that should carry it.
-
Shift-aware by schedule
Publish carries the schedule, so a night-shift board is a schedule and not a second system.
-
Local teams within their reach
Users belong to groups; groups decide what a person can reach.
-
Live content beside it
The App Store carries weather, news, currency, YouTube and tickers, beside your own media.
What you get
Six things it does today.
Safety messaging
The notices that legally have to be visible, visible.
Recognition and new starters
Names and faces, on the wall people walk past.
Shift and handover information
What this shift is walking into.
Per site, per department
Publish targets the facilities you choose.
Every change on record
Audits records who published what.
Who runs this
The industries that ask for it.
Nearby
Solutions that go with it.
Questions
The things people actually ask.
Does it send desktop or mobile alerts too?
Not that we can evidence. ScreenQube publishes to screens.
Can each site publish its own content?
Yes. Each site is a facility, and users belong to groups that decide what they can reach.
Can we prove a message was displayed?
Reports run in three kinds — media, uptime and audit logs; Audits covers who changed what.
What runs on the screens?
An Android player app on displays you own.