In this next episode of this special series on Alarm Calls to 9-1-1 on TiPS: Today in Public Safety, Fletch digs into ASAP, the Automated Secure Alarm Protocol, and why it is quietly becoming one of the biggest workflow upgrades available to ECCs.

If you have ever taken an alarm call the “old way,” you already know the pain. A phone call from a monitoring center, a queue, a verbal read-off, a dispatcher typing it all into CAD, and the inevitable moment where someone asks, “Can you repeat the address?” ASAP flips that model on its head by sending actual alarm data digitally and securely straight into a PSAP’s CAD workflow. No phone call. No transcription step. No slow-motion obstacle course.

This episode walks through how ASAP came to be, why it originally leveraged NLETS as the backbone, and what the results looked like in early proof-of-concept deployments, including turnaround times of 15 seconds or less from alarm to dispatch. Then we break down what ASAP is at a practical level, including the ALQ and ALR message exchange model and how agencies can accept, reject, update, and clear alarm events digitally.

We also take on the uncomfortable reality behind alarm traffic. The numbers are blunt. Most alarm activations are not emergencies, and a huge percentage are tied to simple user errors like entering the wrong code or forgetting to disarm. ASAP helps cut the waste and the friction, and it lets cancellations and updates move as fast as the data can travel.

Finally, we look at how deployment is evolving beyond the traditional NLETS model, including newer options like cloud-based connectivity and lightweight approaches such as ASAP View for agencies that are not ready for full CAD integration.

Follow Fletch for more:

911TiPS.com

Fletch.TV

x.com/@Fletch911

Copyright ©2026 Fletch911, LLC Media Productions http://Fletch911.com