Integrations

Two kinds of connection, one place to decide.

WhiteGlove AV doesn't replace the tools you already run, it connects them, and those connections come in two distinct kinds. Some are cloud and system integrations that give the room its identity and context. Others are device platforms the room monitors and controls in the space itself. Neither kind decides what the room does. That stays in one place, with the rules and the record.


Cloud & system integrations

Where the room gets identity and context.

These reach out over the internet to your systems of record. They tell the room who someone is, what they're booked for, and the local context that makes a decision explainable. This is the room's knowledge, not its hands.

Understand

Microsoft 365

This is how the room knows who someone is and what meeting is on the calendar. It looks a recognized person up in the company directory to read their role, and it sees what's booked, so the room understands both who is present and what they came to do.

Sense

Azure AI

This is the face recognition that turns a person at the door into a name the room can act on. Basic detection is live and verified today; the full enterprise-scale matching is awaiting Microsoft's access approval, and it drops into the same recognition step once cleared.

Understand

Obsidian

This is the room's notebook of how each space and team actually works. It holds the local context the room can lean on, so a decision can be explained in plain terms, not just made.


Device monitoring & control

The hardware the room reads and drives.

These are the physical platforms in the room, reached over their device APIs. They sense that the space is in use, carry out the chosen setup, and confirm the room really changed. This is the part that's meant to be swapped and extended as a room's gear changes.

Sense

Neat

These are the sensors that tell the room it's genuinely in use. They confirm people are actually in the space and the gear is awake, so the room responds to what's really happening rather than a guess.

Act

Cisco

This is the gear that physically sets the room. When a setup is chosen, it aims the camera, picks the right screen, and adjusts the lighting, turning the decision into a real change in the room with no one touching a panel.

Confirm

Utelogy

This is the check that the room did what it was told. After a setup loads, it watches the AV gear and reports back the room's real state, so the result is confirmed rather than assumed.

Built to grow

Bring your own room gear.

Because the decision lives in the rules and not in any one device, a new control system or codec drops into the same act-and-confirm steps without rewriting how the room decides. These are the platforms next in line.

PolyCrestronQ-SYSMicrosoft Teams RoomsLogitechSamsung / LG

Splitting the two kinds apart is deliberate, and it's the same reason the decision stays out of all of them. The cloud and system integrations add who someone is and what they came to do; the device platforms sense the room, act on it, and confirm the result. But what the room should actually do lives in one set of rules that every one of them feeds. That separation is what lets a different control system or a new cloud source drop in later without rewriting any of the rules that decide the room.