Adding remote patrols to alarm monitoring

The panel reports events: a contact closed, a PIR tripped. The round reports conditions: the dock door was down at 01:00, the yard was empty, the camera could see. A client with both has an answer to two different questions, what happened and whether the site was in order, and the second is the one the insurer asks. The alarm verification use case covers the camera's role at the moment of a signal; this guide covers the hours in between.

Not the alarm workflow. Camzify does not receive panel signals and does not replace alarm receiving software. What arrives beside it is a second stream: automated rounds running on their schedules across every client site, failed checklist items messaging the designated person with a frame, and critical notifications for a risk the AI sees at a stop that the checklist did not ask about. The operator handles the failures, and the rounds that pass produce their reports without anyone touching them. The scheduling page has the detail.

Manual rounds stay available for the checks an operator should make in person from the console: after an alarm is stood down, for instance, walking the site's cameras and recording that it was found clear.

The monitoring company holds the account. Each client, or each agency you monitor for, is a sub-user scoped to its own sites and cameras, with a permission group that decides what it can open. License quota is allocated from what you hold and can be reclaimed. A client reads its own reports through its own login and sees nothing that belongs to another. The monitoring companies page covers the model, including the reverse arrangement where an agency holds the account and you are the sub-user.

Cameras reachable from the internet connect by RTSP directly. Cameras on the client's LAN connect through the Camzify Connector, a small application on a PC inside that network, with no port forwarding on the client's router. Encoders push RTMP. A site can mix all three, and nothing the client has installed is replaced; the on-site recorder keeps recording. The RTSP setup guide walks through adding a camera.

A report per round: every stop, every item, its result, the frame, the before-and-after pair for anything fixed, timestamps and a compliance percentage. Beside the alarm log, it is the evidence that the site was checked and found in order between events. Nothing in it is typed in afterwards.

Camzify is priced per camera and quoted for your portfolio; we do not publish rates. Price the round to your client per site per month, separately from the monitoring fee, so the client can see what each buys. The agency mode of the ROI calculator takes your client count and your price and shows the recurring revenue; the quote comes back against it.

Not integration with the panel, not a false-alarm reduction figure, not a response time, not that the round attends. Say what the round does, show a report, and leave the rest to the trust page, which lists what we do not claim so you never have to walk something back.