The patrol leaves. The site does not stop.
Mobile patrol economics are simple: one vehicle, one officer, a route of client sites, a few minutes at each. It is efficient coverage and clients know it. They also know what happens in the other fifty minutes of the hour. The construction site gets hit right after the patrol car pulls away. The storage facility’s gate is propped open at 2 a.m. The dealership lot sees someone trying door handles while your officer is across town.
Most of those clients already have cameras. What they do not have is anyone watching them between visits. Patrol companies have tried adding remote monitoring as an upsell, but staffing a room to stare at every client camera all night costs more than the patrol contract is worth.
Where patrol companies get stuck.
- Coverage is a schedule, not a signal. Patrol visits are timed by route, not by what is happening on site.
- Officers arrive blind. When a call comes in, the officer gets an address and a vague description, not a picture of who is where.
- Proof of service is thin. Clients see a GPS stamp and a checkpoint scan. They do not see what happened between.
- Remote monitoring does not pencil out. A full monitoring staff for every camera on the route is too expensive for the margins in patrol.
How Semaphor fits mobile patrol.
Semaphor turns remote monitoring between patrols into something one dispatcher can run. Put your clients’ camera dashboards on a central monitoring station, whatever software each client uses. Semaphor captures that screen, separates each camera pane and keeps track of which view is which as layouts cycle. See works with existing camera software.
While the patrol is on the road, person and vehicle detection watches every visible view. Activity on a closed site puts an alert in the dispatcher’s inbox immediately; Semaphor is alert-first, so nobody waits on the AI to see that something moved. Then an AI scene report adds what is happening, what was observed and a recommendation. The dispatcher decides whether to reroute the patrol, call the client or close it out.
Send the patrol in with context.
A dispatch that says “person near the north fence, second camera from the gate, walking toward the equipment yard, one vehicle parked outside” is a different call from “check the site.” Semaphor’s cards carry the camera, the time, the original frames and the AI’s description, so the dispatcher can brief the officer before they arrive. That matters for after-hours trespassing on construction sites, car dealership lots and solar farms, where the officer is usually alone.
Between visits, without Semaphor
Cameras record. Nobody watches. The client learns about the break-in from the morning crew.
Between visits, with Semaphor
Activity on a closed site reaches the dispatcher as a prioritized card with evidence. The patrol goes where it is needed.
Fewer wasted runs, better-timed visits.
Patrol routes get stretched by calls that turn out to be nothing: an alarm panel tripped by wind, a raccoon on a motion sensor, a tenant who forgot their code. Every one of those pulls the car off route. When the dispatcher can open a card and see what is actually on camera, with the AI’s description beside the original frames, a lot of those runs become a two-minute check instead of a forty-minute detour. The patrol spends its time on the sites where something is happening.
It works the other way too. Semaphor keeps repeated activity on one card with duplicate suppression and cooldowns, so a delivery truck parked at the dock does not generate a new alert every few minutes. The dispatcher sees the sites that changed, not the ones that are simply busy. That is how one central station can realistically watch a whole route’s cameras overnight. Our guide on loitering detection covers one of the patterns patrol clients ask about most.
Evidence for the client report.
Every card keeps the original frames next to the assessment, hashed at capture, with exportable JSON manifests. Pair that with your patrol logs and the client sees the full night: what the cameras caught, what your dispatcher did and when the officer arrived. See evidence and audit trail.
How to start.
Pick a route.
Choose a patrol route with clients who already have cameras you can view. Put their dashboards on one central station.
Run it overnight.
Semaphor watches between visits. Your dispatcher works the inbox and routes patrols on real activity.
Show the client.
Compare missed events, nuisance alerts and response delay, and turn the evidence into a better service report.
See how a pilot works or book a live demo.
Patrol company questions.
Do officers need a new app in the vehicle?
No. Semaphor runs at the central monitoring station. The dispatcher uses your existing radio, phone or patrol app to brief officers.
What if a client’s camera drops off the dashboard layout?
That view is marked unobserved for the gap. Semaphor never treats a camera it cannot see as quiet.
Does it identify people?
No. It detects people and vehicles and numbers tracks per camera. There is no facial recognition or identity matching.