A proposal that includes "managed networking" or "24/7 monitoring" sounds complete until you ask what is actually being watched, who gets the alert, and what still needs someone standing in your mechanical closet. Those are fair questions to put to any integrator before you sign, and the answers vary more than the marketing language suggests.
What devices are actually monitored
A managed-networking line item usually means your gateway, switches, and access points are enrolled in a cloud management platform rather than left to run unsupervised. On UniFi hardware, that platform is UniFi OS running on the gateway itself, with the UniFi Site Manager dashboard providing remote visibility. The gateway's built-in ISP Health Monitoring gives real-time status on the WAN link and pushes email and app alerts when connectivity degrades, which is one of the few checks that genuinely runs continuously rather than on a schedule (UniFi Cloud Gateways).
If the project includes Crestron control hardware alongside the network — processors, touch panels, DM NVX endpoints — those devices can be separately enrolled in Crestron's XiO Cloud service, which lets a remote team view device status, configure settings, manage licenses, and update firmware from one central cloud location (Overview | XiO Cloud Manual). Ask your integrator explicitly which platform covers which device class, and whether alerts from the network side and the control side land in one place or two — that's a reasonable thing to have spelled out in the proposal rather than assumed.
It's worth asking what happens if a device itself goes dark rather than just losing network connectivity. XiO Cloud's offline-detection logic has changed over different service versions — newer versions wait several minutes and attempt repeated pings before marking a device offline, rather than flagging it on the first missed check-in (FAQs | XiO Cloud Manual). That detail matters because it affects how fast you actually learn something failed versus how fast the dashboard says it did.
What a remote team can fix without a visit
Firmware updates are the clearest example of work that happens entirely off-site. XiO Cloud is built to push firmware to many Crestron devices across an installation simultaneously, without a technician touching each unit (Overview | XiO Cloud Manual). On the network side, a remote-capable team can reconfigure VLANs, firewall rules, and Wi-Fi settings from the UniFi dashboard, restart a misbehaving device, and review traffic logs to diagnose congestion or a misbehaving client — all without a truck roll, provided the gateway itself is still online and reachable.
What remote tools generally cannot resolve: a dead access point, a severed cable, a power supply failure, or a device that has lost network connectivity entirely and can no longer phone home. Those require physical access. This is the honest boundary to ask a vendor to define in writing — which failure categories are covered under remote support, and what the dispatch terms look like when a visit is actually required. If you want a deeper look at how segmentation and redundant hardware reduce how often that physical visit becomes necessary in the first place, our networking upgrade page walks through the design side of that question.
What stays your responsibility regardless of the agreement
A managed-networking contract does not transfer ownership of a few things that remain yours:
- The ISP account and contract. No management platform — UniFi or Crestron — can renegotiate your internet service agreement, change your plan, or resolve a billing dispute with your carrier. Monitoring can tell you the WAN link dropped; it cannot fix a problem on the provider's side of the demarcation point.
- Physical access. Someone has to be able to get a technician into the mechanical closet or rack room when a visit is required. If the property is seasonal or the owner travels, ask how access is arranged before an emergency forces the question.
- Credential hygiene. Enrollment in XiO Cloud supports single sign-on through SAML, OpenID Connect, or Microsoft Entra ID, which is useful for an organization managing dozens of users (FAQs | XiO Cloud Manual), but someone still has to decide who gets access, retire old logins, and avoid sharing a single account across household staff or contractors indefinitely.
Questions worth asking before you sign
Before accepting a managed-networking line item, it's reasonable to ask a prospective vendor:
- Which specific devices — gateway, every switch, every access point, every control processor — are actually enrolled in a monitoring platform, versus just the gateway?
- Is the cloud dashboard optional or mandatory for daily operation? An on-premises controller that treats cloud as an optional secure proxy is a different architecture than one that requires constant cloud connectivity to function.
- What is the alerting path — who receives a notification first, and what is the expected response time for a WAN outage versus a failed access point?
- If the home has both Crestron control and a UniFi network, do alerts from the two platforms land in one place, or are they tracked separately? Ask the vendor to explain how that's handled rather than assuming it's unified.
- What exactly triggers a truck roll versus a remote fix, and is that distinction written into the agreement or left to judgment at the time?
A managed-networking agreement is only as useful as the specificity behind it. Cave Group designs and services enterprise UniFi networks and Crestron control systems for luxury homes, and treats the service boundary — what's monitored, what's remote-fixable, and what the homeowner still owns — as something that belongs in writing before a project starts, not something discovered during the first outage. For the hardware and design side of a network built around that kind of clarity, see our networking upgrade service page.