Est.

Police Dispatch Priority for Video-Verified Security Alarms

Unverified alarms sink in the dispatch queue, but video changes that.

· 11 min read · Updated
Cover illustration for “Police Dispatch Priority for Video-Verified Security Alarms”
Threat Response SLAs · September 30, 2026 · 11 min read · 2,459 words

Video-verified security alarms occupy a different place in the police dispatch queue than ordinary alarm signals, a structural split built on decades of false-alarm data, a slow-moving wave of municipal policy, and a technical definition of "verification" that most property operators never see spelled out. If you understand that split, and what actually produces a Priority 1 response versus a Priority 4 one, you have the operational knowledge that separates commercial security spending that works from spending that sits unused in a queue.

Why police treat burglar alarms as low-priority by default

The starting fact is statistical. Across U.S. jurisdictions, somewhere between 94 and 99 percent of burglar alarm calls turn out to be false, a pattern the DOJ COPS Office documented in its problem-oriented policing guide and one that holds up in department-level data from cities including Phoenix, Seattle, and the LAPD. A dispatcher looking at an unverified alarm signal has almost no reason to treat it as a crime happening right now, because 19 times out of 20, at minimum, it isn't one. The computer-aided dispatch systems that run American police departments assign a priority level to every incoming call, and that incentive structure runs straight through the math: an unverified residential or commercial burglar alarm almost never earns Priority 1. It typically runs at Priority 3 or Priority 4, and an officer responds when one becomes free, often without lights or sirens, sometimes a long while after the signal first came in.

San Jose's 2025 call data shows what that looks like in practice. More than four in five alarm calls in the city carried a Priority 3 designation, the lowest tier in the system. The alarm going off, on its own, does almost nothing to move the call up the queue. A property owner who assumes that a triggered sensor functions like a 911 call for an active break-in is operating on a false premise, and the dispatch data makes that plain without needing much interpretation. The system is tuned, deliberately, to the reality that the overwhelming majority of what it receives from alarm panels is noise, and tuning it any other way would mean sending officers lights-and-sirens to false alarms dozens of times a day.

The traditional monitoring relay

Before a call even reaches a dispatcher's screen, the standard alarm monitoring workflow has already added a series of required steps, and each one consumes time. The sequence runs in a fixed order: a sensor trips, the signal travels to a central monitoring station, an operator places phone calls under a process called Enhanced Call Verification, and only after two or more of those calls go unanswered does the operator request police dispatch. The International Association of Chiefs of Police formally endorses this process, and it recommends that alarm companies attempt at least two calls to two different numbers before asking for a police response. Each of those calls takes time to place, time to ring, and time to go unanswered, and all of it happens while whatever triggered the alarm is still unfolding on the property.

The DOJ COPS Office checked how well this process works and found that Enhanced Call Verification cuts false alarm calls by only a quarter to two-fifths. It does not confirm that a crime is in progress. Calls processed through ECV still arrive at the dispatcher's desk unverified, no matter how many phone calls were placed first, and the dispatcher treats them exactly the way the false-alarm math says to treat them, as a low-priority event. Monitoring contracts tend to advertise a response time, but that number covers only one link in a much longer chain: signal transmission, the ECV phone calls, operator review, and then whatever priority the dispatch system assigns once the request finally goes out. None of those stages happens instantly, and none of them, on their own, change what the responding officer knows about the scene. A property operator reading a promised fast response time is reading about one segment of a longer relay, not the full distance between a sensor trip and an officer arriving on site.

The verified-response policy wave

Some jurisdictions have gone further than simply deprioritizing unverified alarms informally. They have written verification into law, making it a prerequisite for any police response at all, and the number of cities doing so has grown since 2024. Salt Lake City set the template in December 2000, when it became the first major U.S. city to put verified response into a formal municipal ordinance, following a practice Las Vegas had run since 1991. The result in Salt Lake City was a roughly 95 percent drop in alarm dispatches, from thousands of calls a year down to a few hundred, without any documented increase in burglaries that were actually completed.

Other cities have since adopted versions of the same rule. Memphis will not dispatch officers for an alarm call unless video verification shows a crime underway, and Pittsburgh requires verification of some kind, video, audio, a secondary sensor trip, or a witness, before sending anyone to a burglar alarm at any hour; Pittsburgh separately declines in-person response to all non-emergency calls between 3 AM and 7 AM. Akron and Las Vegas run on that same no-verification-no-response standard too. Seattle joined the list on October 1, 2024, becoming the 19th law enforcement agency in the country to adopt the policy, the Security Industry Association reported.

That list is still short relative to the 19th-in-24-years pace of adoption, with only 19 agencies having adopted the policy in that time. Most cities have taken a middle path instead, adopting permit-and-fine ordinances modeled on the SIAC/IACP Model Alarm Ordinance: property owners register a permit, pay escalating fines after a set number of false alarms, and lose police response entirely if they rack up too many of them. Adoption of full verified response has moved slower than the policy's visibility might suggest, and it has not been a one-way trend everywhere. The Security Industry Association counts eleven agencies that tried verified response and then reversed it, including South Salt Lake City, Dallas, Madison, San Jose, and Henderson. The honest read of this landscape is that verified response has not swept the country, and it is not likely to in the near term given how few agencies have adopted it formally over 24 years. But the direction of the policy conversation, and more importantly the direction of how dispatchers already treat unverified calls informally, both point the same way. Commercial operators who wait for their own jurisdiction to pass a verified-response ordinance before investing in verification are already behind the curve the dispatch system is quietly operating on, ordinance or no ordinance.

Evidence that moves a call up the dispatch queue

Verification is a term that gets used loosely in the security industry, and the loose usage obscures a real distinction that determines dispatch priority. Several kinds of evidence can push an alarm event up the queue. Audio verification, where a monitoring center operator hears glass breaking, voices, or movement inside a property, counts. So does video verification, where an operator looks at a camera feed and confirms an unknown person on-site. Cross-zoning, where a second sensor in a different part of a building trips, suggesting someone is actually moving through the space rather than one sensor malfunctioning, counts as well. A panic or duress signal sits in its own category, and it gets treated almost universally as a Priority 1 in-progress crime.

The security industry has built a formal standard around this question of evidence quality. ANSI/TMA-AVS-01-2024 defines five alarm levels: Level 0, no call for service at all, Level 1, a call with limited or no additional information, Level 2, confirmed or highly probable human presence with unknown intent, Level 3, confirmed threat to property, and Level 4, confirmed threat to life. The International Association of Chiefs of Police ratified a resolution that endorses the standard and encourages emergency communications centers to use it. That endorsement lines up with the spread of verified-response ordinances described above: an AI-detected intrusion that comes with a labeled bounding box and a confidence score supports a Level 3 or Level 4 classification, while a bare sensor trip with no visual confirmation sits at Level 1. The level assigned to an event is not fixed at the moment the sensor trips. An alarm may start at Level 1 when the signal first arrives, and it can be escalated or de-escalated as more information comes in, so the monitoring center's review process works as a dispatch-tier decision in its own right, made before the call ever reaches a police dispatcher.

The caveat that property operators need to hold onto is that the standard does not guarantee an outcome. AVS-01 gives agencies a shared framework for communicating threat levels, but it does not bind any jurisdiction to respond at a particular tier for a particular level. Local policy, the specific circumstances reported, and the resources a department has available at that moment all factor into the actual response, regardless of how the alarm event was classified. And a detail that trips up a lot of commercial buyers: a camera that records footage but is not wired into the monitoring workflow does not produce verification in any sense that matters to a dispatcher. Installing an alarm panel and a separate camera app, with no connection between the two systems, does not create the evidence chain that moves a call up the AVS scale. Verification has to be built into the monitoring process itself, not bolted on as a separate piece of hardware that nobody is watching when the alarm trips.

Site-specific context separates noise from verified evidence

A person visible on camera is not, by itself, evidence of a crime. What turns that footage into something a monitoring operator can act on is the ability to judge it against what is normal for that property, at that hour, in that zone. If someone climbs a fence after midnight, that same detection can mean a criminal intrusion at one site and a contractor doing scheduled work at another. A vehicle parked near a loading dock might be a theft in progress or an early delivery arriving ahead of schedule. A cleaning crew moving through a lobby at 7 PM reads as routine, but the same movement pattern inside a locked server room at 2 AM calls for immediate escalation.

None of that context lives in the raw sensor data or the video feed. It has to be built into the monitoring platform as site-specific rules and schedules, because the camera has no way of knowing on its own what counts as authorized activity at a given address. The human operator makes the final call under the monitoring procedure, but that judgment only works when the system feeds the operator the right contextual information to judge against.

Different categories of commercial property carry distinct patterns of normal activity, and a generic, one-size-fits-all monitoring setup tends to misread them. Construction sites run active work in low light and changing weather, with contractor traffic that shifts as a project moves through phases, so monitoring with site-specific rules distinguishes legitimate after-hours work from an actual intrusion more reliably than motion analytics that just flag movement in frame. Logistics yards see vehicle patterns that change by shift and by season, and a vehicle parked at 3 AM could be a routine overnight stop or the setup for a cargo theft, a distinction only site context can resolve. Retail locations and multifamily housing see heavy foot traffic during business hours and a very different profile after closing, and the monitoring rules need to reflect both states rather than treating every hour the same way.

Older, purely motion-based alarm systems generated so much of the noise that produced the 94 to 99 percent false-alarm rate in the first place because they lacked that contextual layer. Shadows, insects, weather, moving vegetation, headlights, and wildlife all trip motion sensors, and without a layer of contextual judgment behind them, operators had to review every one of those events by hand, which is the workload that made scalable monitoring so difficult to run well. Systems that correlate signals across motion detectors, door contacts, glass-break sensors, access control events, cameras, and environmental sensors, and that apply rules about direction of travel or restricted zones, are doing something different in kind from a camera that just flags motion in frame. They are weighing whether what they are seeing fits the pattern of activity that is actually authorized at that specific site, which is the judgment a dispatcher needs translated into evidence before a call can move up the AVS scale.

The ASAP-to-PSAP protocol

Once a monitoring center has produced a verified, site-contextualized alarm event, there is still one more structural bottleneck standing between that event and a dispatcher: the phone call. A data-sharing protocol between monitoring centers and emergency dispatch systems removes that bottleneck by transmitting the event digitally instead of by phone. A standard alarm still requires the two or more calls under Enhanced Call Verification described earlier, but a verified event with video confirmation can skip that callback sequence and go straight to the dispatch center electronically.

The Monitoring Association reports that ASAP is now running in more than 100 emergency communications centers around the country and credits the protocol with cutting dispatch time by roughly two minutes per call simply by taking the phone relay out of the sequence. Two minutes does not sound like much written down, but in the context of an intrusion already in progress, it is the gap between an officer arriving while the suspect is still on the property and arriving after the suspect has already left.

The real case for this layered approach lies in how the pieces compound rather than in any one of them alone. AI-assisted filtering cuts the time a monitoring operator spends reviewing an event down to seconds, site-specific context pushes the event to a higher AVS classification, and ASAP-to-PSAP strips the phone relay out of the transmission to dispatch, and each layer compounds the speed gain, with none of them working without the others. A monitoring system marketed as responding within 15 to 30 seconds of detection is describing only its own side of the process. The full timeline that actually puts an officer on scene runs through dispatch priority, and dispatch priority is set by the quality of the evidence the call arrives with, not by how fast the monitoring center itself reacted. A property operator evaluating a security system's claims should ask less about how quickly the system detects something and more about how that detection gets classified, contextualized, and handed to the people who decide how fast an officer actually responds.

Sources

  1. Ending the Era of False Alarms - ESA

More in Threat Response SLAs