> ## Documentation Index > Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt > Use this file to discover all available pages before exploring further. # Overview > What the Domotz network monitoring integration brings to your Neo Agent setup Domotz monitors the networks at your clients' sites: a collector at each site finds the devices on the network and watches their status, latency and power. The tickets it causes are routine. A device went offline, the internet is slow, an IP conflict, a frozen access point. Connect Domotz to Neo and your agents check the site from the ticket, power cycle the device through its switch port, and resolve the alert once the device is back. Domotz uses one API key per MSP. Connect it once and every agent you enable can use it, with permissions you control per agent. ## What Neo can do with Domotz Tell whether the site is down or just one device, see when a device dropped off, and read latency, packet loss, internet speed history and IP conflicts. Record a device's name, type, room and notes, tag it, or add a sensor to watch a service. Read the alert behind a ticket, the rule and profile that raised it, and resolve it once the device is back. Power cycle a frozen access point, camera or phone through its PoE switch port or PDU outlet, so nobody drives to the site. Stop alerting on a device the client retired, or bind the right alert rule to a new switch. Add a routed subnet a new branch office brought, change a scan policy, or close a VPN session left open. Find every collector of the ticket's client, and keep a new site and the client's contacts filed under the right Organization. Give a new technician a Domotz login or remove a leaver's, from an onboarding or offboarding ticket. ## Your clients are mapped automatically Neo matches each Domotz collector to a company in your PSA and keeps the mapping on the Domotz card's **Organization Mapping** tab. It refreshes the mapping when you save the API key, and again on each nightly PSA sync. A client with several sites has one collector per site, so several collectors map to one company. Matching starts with the name of the Domotz Organization the collector is bound to, then the collector's own name: exact, then after stripping a legal-form suffix (Ltd, Inc, LLC). Last comes an AI match for the rest. **A name match, or one you confirm, is handed straight to your agents**, so they start from the client's collectors without looking them up. An AI match is not handed to your agents automatically. It shows on the Organization Mapping tab, where you can confirm or correct it. Anything Neo could not match stays unmapped and visible on the same tab, where you can set the right company by hand. A mapping you set by hand survives every later sync. ## Next steps Save an API key in Neo and choose what each agent can do. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.