Screen remote control: change what's on air, live
Switch a screen, or a whole group of screens, to different content from a computer, tablet or phone — without building a playlist or republishing anything. The schedule handles what's planned, the remote handles what isn't.
Remote control — one button, one zone of screens
Your turn — Press a shortcut on the phone: only the screens in its zone switch, the others keep playing.
The shop's screens
Storefront
Counter
Room
The schedule handles what's planned, the remote handles the unexpected
A well-run display relies first on the schedule: playlists composed in advance, placed on a timeline, that start and stop on their own. That's the normal regime, and it covers the vast majority of what's on screen on an ordinary day.
What's left is the unplanned. A production line stops and the instructions need to go up at the workstation. A class changes rooms an hour before it starts. An item runs out of stock and the announcement needs to go out now, not tomorrow. In these moments, opening the platform, creating a media file, building a playlist and then assigning it to a screen takes several minutes and some familiarity with the tool — while the person who has the information right in front of them isn't necessarily the one who knows how to do that.
The remote control answers exactly that case. It's a web page where you pick a piece of content from a list and send it to the screen you want. The switch is immediate, and returning to the normal programme works the same way. Nothing gets republished, nothing gets overwritten: the schedule stays in place underneath and takes back over as soon as the override is lifted.
One screen, a group, or a whole site
Screens are grouped by Tags in the platform — that's the product's own vocabulary, and it's the same mechanism used across the rest of content distribution. A Tag can describe a place (north workshop, reception hall), a role (storefront screens, checkout screens), or an organisation (Lyon site).
The remote control relies on this structure. You control a specific screen when the information is local, or an entire Tag when it concerns a whole set: the six screens on the shop floor, the four storefront screens across the network, a full floor. Content goes out to every screen in the group in a single action.
This grouping is set up once, calmly, when the fleet is installed. That groundwork is what makes the remote usable in a hurry by someone who doesn't have time to think it through: all that's left is to pick the zone, then the message.
Three situations where the remote beats opening the platform:
- A workshop supervisor switches the line screen to a safety instruction or a stop-production message, from wherever they already are.
- A gym changes a studio's content on the fly when a class is moved or a coach is swapped in at the last minute.
- A shop triggers a promotional announcement at the exact moment it matters, then hands the screen back to its usual playlist once the operation is over.
What the remote control doesn't do
It doesn't replace the platform. You pick existing content there, you don't create it: producing media, building playlists and configuring schedules stay in the back office. That's a deliberate choice — a remote that let you do everything would take as long to use as the platform itself, defeating its own purpose.
It also doesn't excuse letting the schedule go stale. A display that's only ever driven by hand ends up depending on a single person, and it stops the day they're away. The remote is built for the exception: if you're using it every day at the same time, that means a slot is missing from the schedule.
Nor does it have the reach of the emergency alert. The alert takes over the entire fleet, regardless of what's playing, and it's the tool for safety situations. The remote, by contrast, works at the scale of a screen or a group, within the normal course of operations.
On the network side, finally, switching follows the same rules as the rest of content distribution. Content is cached locally on each screen, which lets playback continue if the connection drops. A command sent during an outage, however, is applied once the network comes back, not before: the remote needs to reach the screen to talk to it.
Questions fréquentes
What is a screen remote control used for?
It lets you change what's showing on a screen, or on a group of screens, from a web page opened on a computer, tablet or phone. You pick a piece of content and send it: there's no playlist to build and nothing to republish, and the usual programme resumes afterwards.
What's the difference between the time-based schedule and the remote control?
The schedule handles what's planned: playlists placed in advance on a timeline, which start and stop on their own. The remote handles the unexpected: an immediate switch decided on the spot, without republishing anything. The two work side by side, and the schedule takes back over as soon as the override is lifted.
Can several screens be changed at the same time?
Yes. Screens are grouped by Tags — by place, by role or by site — and content is sent to an entire Tag in a single action. You can also target one specific screen when the information only concerns it.
Do you need to install an app to control the screens?
No: the command goes through a web page, opened from the browser of a computer, tablet or phone. Nothing to install, and no extra cost: the remote control is included in the plan — see the Pricing page.