MenuStart a projectStart

Spaces & devices

Room, signage & tannoy automation

Room automation turns a booking into a coordinated set of device actions. A shared schedule can update signage, prepare lighting and queue an announcement, with changes and cancellations flowing through to each device.

An example of how the studio would build it. No live services are connected.

One booking. A room that’s ready.

  1. Step 01

    Booking confirmed

    A new or changed booking identifies the room, time and purpose.

  2. Step 02

    Room checked

    Work out which devices and settings the booking needs.

  3. Step 03

    Signage updated

    Show the room’s availability and the permitted meeting information.

  4. Step 04

    Announcement queued

    Schedule a tannoy cue at the right time, respecting quiet hours.

  5. Step 05

    Space prepared

    Set the lighting before arrival and restore the room afterwards.

The result

The diary, the display and the room agree.

Changed bookings cancel outdated instructions. Device failures are reported, and staff can always take manual control.

Before we connect it.

Where this is useful

Useful when staff prepare the same spaces repeatedly or keep displays and announcements aligned with a timetable. Each room can have its own equipment and rules while the booking remains the common source of timing.

What we need to connect

  1. 01Bookings with a stable ID, room, purpose, start time and end time.
  2. 02A device inventory with supported protocols and commands for each room.
  3. 03Preparation windows, quiet hours, approved display information and manual overrides.

What needs careful handling

Sending a command is not proof a device acted on it. Track acknowledgements, surface failures and give staff a way to take control. Cancel obsolete commands when a booking changes and restore a known state at the end.

Questions people ask.

Can existing displays, speakers and lights be connected?

It depends on the control interfaces the devices expose. A supported API, protocol or controller can provide the connection. The equipment is assessed before promising a particular integration.

What happens if the network goes down?

Each device needs an agreed fallback, such as normal signage, a local schedule or manual operation. The proposed system reports missing acknowledgements and avoids replaying expired instructions when the connection returns.

Appointment found → Display reset
Automation 03

Calendar-triggered TV welcomes

Lead submitted → Email sent
Automation 01

Lead, CRM & calendar automation

All automation examples