Solution · Alert routing and notification
The right alert reaches the right responder in seconds.
Detection is the easy part. Getting the right alert to the right person on the right channel, without burying responders in noise, is where deployments succeed or fail.
- NDAA-compliant
- Platform-agnostic
- 1,000+ deployments over 15 years
How can we help?
Tell us what you're working through. We'll route it to the right person.
Safety alerts are the routing layer that turns a camera detection or sensor signal into a notification on the device of the right responder. Tec-Tel deploys safety alerting that covers slip-and-fall, occupied-restricted-area, missing-PPE, weapons, gunshot, vehicle-pedestrian conflict, and fire/smoke. Alerts route by role, shift, and severity to SMS, Slack, Teams, PagerDuty, or radio. Free consultation.
§01 Alert categories
Seven event classes, one routing engine.
Detection happens inside the camera, the access control system, or a dedicated sensor. Safety alerts take that detection and put it on the responder's device with enough context to act.
§02 Why routing is the hard part
Detection has commoditized. Getting the alert to the right person has not.
The major camera platforms, camera-agnostic analytics overlays, and acoustic gunshot sensors all surface high-quality events. The harder problem is landing the right alert on the right person's device inside the right window. A floor supervisor needs an SMS in 5 seconds. A SOC operator needs a Slack thread. A facility manager needs a daily digest. Same event, three channels. Routing rules eat the integration cost.
The routing matrix is the artifact that matters. Every alert class maps to a primary channel, a secondary channel, an acknowledgment SLA, and an escalation path. The matrix lives as a customer-owned document. We update it during the quarterly review.
§03 Routing channels
Five delivery patterns cover most environments.
SMS to on-shift supervisor: lowest-friction channel. Works on any phone. Best for floor-level events that need a 30-second response. Inline link to the camera feed.
Slack or Teams channel: best for SOC-style monitoring teams who already live in Slack or Teams. Threaded discussion, history, easy escalation. Not ideal for after-hours coverage.
PagerDuty or Opsgenie: on-call rotation, escalation policies, acknowledgment timeouts. Best for 24/7 corporate security operations centers and security-aware managed IT shops.
Two-way radio over IP: manufacturing, warehousing, hospitals, schools. The radio is already on the responder's hip. Voice page lands faster than text.
PA system override: active shooter, fire, evacuation. Pre-recorded announcement triggers across all zones. Tied to lockdown automation on doors and gates.
§04 False-positive economics
A system that pages too often becomes an opt-out program.
A safety alert system that pages the floor supervisor 30 times a day for non-events is not a safety system. Within two weeks the supervisor silences the channel, and the next real event lands in a queue nobody reads. We've seen this play out at customer sites that bought analytics without thinking through routing.
The fix is design discipline. Confidence thresholds get raised. Zone masks get added. Time-of-day rules suppress alerts during scheduled activity (chemistry tests, vacuuming, scheduled forklift loading). Early in any deployment, alerts run silent or to a supervisor email digest only. Phone-and-radio alerting goes live once the volume is inside spec.
We document the noise floor in the routing matrix. If alert volume creeps up later (a model update, a new vendor pushing more sensitive defaults), the quarterly review catches it before the supervisor turns the channel off.
- → Untuned analytics run a high false-positive rate out of the box.
- → After tuning (zone masks, confidence thresholds, time-of-day rules) the false-positive rate drops to a level responders can trust, lower for object detection than for behavior detection.
- → Tec-Tel's deployment plan front-loads tuning before any alerts route to phones or radios.
§05 Cost framing
Single-vendor alerting is often zero incremental. Multi-vendor consolidation runs $1,500 to $6,000 per site per month.
Single-vendor alerting (using the built-in tools inside a major camera platform) typically adds zero incremental cost on top of the existing license. The alerting capability is bundled.
Multi-vendor consolidation through a security-operations platform typically runs $1,500 to $6,000 per site per month depending on event volume, number of integrations, and after-hours coverage. Custom builds on a messaging API plus Slack plus webhook routing land lower at the software line but require IT capacity to maintain.
Mass-notification platforms are usually priced per recipient per year, in the $2 to $8 range, with floor prices around $3,000 per year per site. The consultation produces a side-by-side so the customer picks the model that fits the size and operations posture.
Questions buyers ask us
FAQ
- Why is alert routing the hard part, not detection?
- Detection has commoditized fast. The major camera platforms, camera-agnostic analytics overlays, and acoustic gunshot sensors all surface high-quality events. The harder problem is landing the right alert on the right person's device inside the right window. A floor supervisor needs an SMS in 5 seconds. A SOC operator needs a Slack thread. A facility manager needs a daily digest. Same event, three channels. Routing rules eat the integration cost.
- What is the realistic false-positive rate, and how do you handle it?
- Untuned analytics run a high false-positive rate out of the box. After tuning (zone masks, confidence thresholds, time-of-day rules) the rate drops to a level responders can trust, lower for object detection than for behavior detection. Tec-Tel's deployment plan front-loads tuning before any alerts route to phones or radios. Early on, alerts run to a supervisor email digest while we calibrate.
- How do alerts integrate with our existing security systems?
- The major camera platforms emit events via webhook, SDK, or built-in integrations. The major access control systems emit door, badge, and forced-entry events the same way. Acoustic sensors and IoT inputs add their own webhook channels. The alert routing layer (a security-operations platform or a custom integration on top of a messaging API plus Slack) consolidates everything into one routing engine.
- Can a single alert trigger automated lockdown?
- Yes, with guardrails. Active-shooter and fire alerts often trigger automated lockdown: doors lock, gates close, PA announcement plays, law-enforcement gets paged. False-positive lockdowns are operationally expensive and erode trust in the system, so the guardrails matter. Most customers require a two-source confirmation (gunshot sensor plus weapon-on-camera, for example) before a lockdown automation fires. The consultation walks each automation through the customer's risk team.
- What does this cost?
- Alert routing platforms typically price per endpoint per month or per event volume. Single-site deployments using built-in vendor alerting often run zero incremental on top of the existing license. Multi-vendor environments using a security-operations consolidation layer typically run $1,500 to $6,000 per site per month depending on event volume. The consultation produces a side-by-side so the customer can pick the model that fits.
- Who picks up the page at 3 AM?
- Routing depends on the customer's coverage model. Sites with their own SOC route to whoever is on shift via PagerDuty or Slack. Sites without a SOC route to a third-party central station. Tec-Tel monitoring partners offer 24/7 coverage with documented response SLAs at the central-station tier. The consultation names which model fits each site, plus the on-call protocol when the page does land.
- Does mass-notification fit inside this scope?
- Yes. Mass-notification (SMS or app blast to every employee or student in a zone) integrates with the same routing engine through the major mass-notification platforms. The use case is active threat, severe weather, evacuation, or chemical release. Tec-Tel sets up the segmentation by building, role, and shift so the right population gets paged without saturating everyone every time.
- What about legal exposure for missed alerts?
- The exposure is not the missed alert. It is the documented design choice that buried the alert. Customers who deploy safety alerting and then route everything to an unmonitored mailbox are building a paper trail against themselves. The consultation produces a written routing matrix showing which event class lands on which channel, with which acknowledgment SLA. We deliver the matrix as a customer-owned document the legal team can put in front of an insurer or a regulator.
Book a walkthrough
Want a read on your alert routing?
The free consultation covers the existing detection stack, the channel each alert lands on, and the gaps where a real event dies in a queue nobody reads. You leave with the routing matrix and a tuning plan, so the safety committee can see what's getting paged on day one.
- Tell us how many sites you run and what's already in place. We'll show you what a build or upgrade looks like.
- Straight answers from the team that does the work. We're platform-agnostic, so you get the system that fits your sites, not one brand's catalog.
Since 2010 · 1,000+ deployments nationwide · ISN-accredited
How can we help?
What you're looking for, plus any details. We review it and follow up, usually the same day.
Related from Tec-Tel
Operational safety
PPE, near-miss, and forklift detection on existing cameras.
Read on SolutionVision intelligence
The AI analytics layer that generates the events safety alerts route.
Read on ReferenceVendor comparison matrix
Full capability table across camera, access, and analytics platforms.
Read on