Alarm Scheduling and Dispatch Software: 4 Queues

Ask an alarm dispatcher what their hardest decision is and they will not say routing. They will say deciding whether the company or the customer is paying for the visit, at eight in the morning, with the customer on hold.

A plumbing dispatcher assigns a job that generates revenue when the truck arrives. An alarm dispatcher assigns a job that, more often than not, costs the company money the moment the van moves, because a monitoring agreement or a warranty already covers it. Route optimization does not touch that problem.

The short answer

Security alarm scheduling and dispatch software is worth buying when it can tell your dispatcher, before the truck moves, which agreement covers this visit and what the site's signal history looks like. It is not worth buying when it is a field service calendar with an alarm logo on the pricing page.

The test takes one question in a demo. Open a service call on an existing monitored site: does this screen show the active agreement, what it covers, and whether this site called for the same reason last month? If the answer requires a second system, you have bought a scheduling app and kept the guessing.

Why alarm work breaks general field service software

General field service management was designed around one shape of job: one technician, one address, one visit, one to three hours, customer pays. Everything in a standard dispatch demo follows from that shape, which is why the map with the moving pins is always the opening slide. An alarm company runs four shapes of work at once, and only one of them fits that model.

Three of those four rows have a payer or a constraint that a generic board cannot see. That is why so many alarm shops run the schedule out of a whiteboard and a group text while paying for software that only holds the calendar. A security company owner posting a product validation thread in r/lowvoltage listed the same failures: no single place to track open projects, service calls and fire inspections, billing unaware of scope changes, and "having to manually dispatch techs to jobs every day by either calling or texting them individually." The dispatching stays manual because the calendar does not hold the information that makes the assignment decision.

The payer question comes before the routing question

Here is the math no dispatch vendor puts on a slide. Field service benchmarks put a fully loaded truck roll at roughly $150 to $300. Broader industry estimates run $250 to $500, and the Technology and Services Industry Association puts the true all-in cost near $1,000 per dispatch once labor, vehicle, fuel, dispatcher time and overhead are counted. Roughly a quarter of truck rolls across field service are classified as avoidable.

Now put that against what an alarm account bills. Basic residential monitoring sits around $15 to $25 of recurring monthly revenue per account, with typical residential accounts often valued near $32 and commercial accounts carrying interactive and video above $50.

So a single uncovered visit to a $30 a month residential account costs you five to ten months of that account's revenue. Two of them in a year and the account runs at a loss no matter how clean your monitoring margin looks in aggregate.

So the payer field is the most economically loaded field on the ticket, and it has to be visible at dispatch rather than discovered at invoicing, which is where most shops find it. The dispatcher needs three things on screen before assigning: the active agreement and what it covers, the install date and warranty status, and whether this site has called for the same symptom before. Get those visible and a large share of dispatch decisions change. Some calls get quoted as billable on the phone. Some get held for a batched visit next Tuesday. Some get solved without a truck at all.

Queue 1: the false alarm callback

This is the largest unbillable queue in most alarm shops, and almost nobody measures it.

Roughly 96 percent of alarm system activations occur when no crime is taking place, according to the widely cited U.S. Department of Justice figure. Local data runs harder still: police in Gastonia, North Carolina found that of 5,560 alarm calls for service in 2021, seven were real threats.

Subscribers absorb the fines directly. Los Angeles charges an alarm user $176 for each false alarm. San Francisco escalates from $100 for the second event in a calendar year to $250 for the fifth and beyond. Howard County, Maryland gives two warnings, then $50 escalating by $50 per event. They do not experience that as a municipal problem. They experience it as your system failing, and they call you. That call becomes a truck roll you probably do not bill, on an account you now have a retention problem with.

Two things follow for the board.

Tag the reason, not just the ticket. Every callback needs a cause code at close: subscriber error, pet or environmental, faulty device, installation defect, communication failure, or verified event. Without that field you cannot see which sites are chronic and which technicians are producing the callbacks. With it, ten minutes a month tells you where to send a training visit instead of a repeat truck.

Know the local cancellation rule. In Raleigh, if the alarm company requests cancellation before the responding officer reaches the site, the event does not count as a false alarm and no fine is assessed. Several ordinances have a version of this, which makes verification and cancellation a dispatch workflow with a dollar value attached rather than a courtesy.

Queue 2: the signal report is a dispatch queue

This is the queue that separates alarm dispatch from every other trade, and no general field service product ships with it.

Your central station knows things about your accounts that your service board does not: which panels have not sent a supervisory signal in 30, 60 or 90 days, which sites are throwing communication failures, which have low battery troubles nobody has cleared. Every one of those is a service call that should be scheduled proactively, and none of them will ever ring your phone. The subscriber does not know their system stopped talking. They find out during a break-in.

The financial case for turning that report into a dispatch queue is unusually concrete, because it is the same data buyers use to value your company.

Alarm portfolios trade on multiples of recurring monthly revenue, not EBITDA. Current 2026 guidance from acquisition advisors puts residential monitoring on multi-year contracts at 35 to 50 times RMR and integrated fire and security accounts at 45 to 55 times, with attrition setting the position in the range: sub-5 percent supports 40 to 50 times, 12 to 18 percent supports 25 to 32 times. Then comes diligence. Buyers verify account quality against 12 to 24 months of central station signal data, and accounts showing zero signal activity over 90 days are discounted or excluded outright.

Read that back as a dispatch instruction. A no-signal report is a list of accounts currently worth nothing to a buyer and on their way to cancelling, and it is invisible in a system that only schedules inbound calls. Pull it weekly, filter for no-signal beyond 30 days and repeat communication failures, and give it a standing block on the schedule. Two accounts a week, batched geographically, costs a fraction of a technician and holds the number that sets your multiple.

Queue 3: inspections are calendar work, not call work

Recurring inspection and testing is the most predictable revenue in an alarm business and the most commonly scheduled badly, because it gets scheduled reactively.

NFPA 72 requires semiannual visual inspection and annual functional testing for most fire alarm devices, with waterflow switches tested quarterly, and your local authority having jurisdiction can require more than the code minimum. Adoption cycles move the target: when California adopted the 2025 edition effective January 1, 2026, every existing system in the state came under the newer chapter requirements. None of that arrives as a phone call. It arrives as a date that was knowable a year in advance.

So the scheduling logic inverts. Inspections go into the calendar first, batched by due month and by postal code, with reactive capacity scheduled around them. A tool that cannot generate next quarter's inspection list from contract terms and route it as a batch forces your office to rebuild that list in a spreadsheet every quarter, which is exactly how inspections slip past their due date and become your customer's AHJ problem.

Fire and integrated accounts carry premium valuation multiples specifically because code-mandated inspection revenue and lower attrition make them sturdier. Running that calendar well is not admin. It is the part of the book that compounds.

Queue 4: campaign work nobody plans for

The fourth queue shows up every few years and wrecks a schedule with no room for it: fleet-wide equipment change.

Resideo has announced that the VISTA-21iP and VISTA-21iPLT control panels will be discontinued for sale in the United States and Canada effective May 1, 2026, and those panels are not compatible with modern LTE networks. Anyone who lived through the 3G sunset, when AT&T ended its network in February 2022 and Verizon followed that December, knows the shape of what comes next: a defined population of accounts that must be visited before a date, or they stop being monitored accounts.

Campaign work is scheduled by geography and panel type, not by call order, so your system has to produce a list filtered by installed equipment and hand it to the board as a routed batch. That is an installed-system database question before it is a scheduling question, which is why shops that track equipment on the site record handle these transitions in weeks.

Installs do not belong on the service board

An install is not a long service call. It runs several days behind a permit, an equipment lead time, a rough-in that may depend on another trade, a monitoring account creation step and an AHJ inspection. It consumes a crew, and its start date is decided by dependencies rather than by an open slot.

Put that on the same board as 90-minute service calls and either the crew's multi-day commitment gets fragmented, or the board pretends a three-day install is one appointment and stops being an accurate picture of capacity. Keep two boards over one record of the site and system, or the handoff after install becomes the leak. We covered that handoff in how to track security alarm jobs from lead to invoice.

The capacity math for the service board

Two numbers run a service day, and neither is drive time. Stops per technician lands between three and five in most alarm shops, fewer in dense commercial work where badging in and finding an escort eats an hour before anyone opens a panel. Held capacity means one slot per technician left unassigned, because alarm work generates real same-day emergencies: fire trouble conditions, commercial sites that cannot arm, accounts whose alarm just cost the subscriber a fine.

Then add the step that only exists in this trade: placing the system on test with the central station before work begins and clearing it afterward. Skip it at the start and you generate a false alarm and possibly a police response your customer pays for. Skip it at the end and the account sits on test, unmonitored, until someone notices. It belongs on the ticket as a required step with a timestamp, not in a technician's habit.

What to actually buy

There are three honest options and the boundary between them is not company size, it is where recurring revenue and signal data live.

Generic field service software. Jobber, Housecall Pro, Workiz and BlueFolder schedule, dispatch, invoice and sync to QuickBooks well, and their pricing is public: BlueFolder lists around $30 per user per month billed annually, and Workiz starts near $225 a month for up to five users with additional seats in the $46 to $54 range. None of them model monitoring RMR, contract coverage at dispatch, or central station data. Under roughly 200 monitored accounts, a generic tool plus a disciplined coverage field on every customer record works fine.

Alarm-specific platforms. FieldHub, WorkHorse SCS, Rev.io, Bold Group and Cornerstone are built around the alarm model: RMR billing with proration and deferred revenue, installed systems as first-class records, native central station integrations. FieldHub connects to Rapid Response, AvantGuard and Affiliated Monitoring, and records a reason code on every RMR change so attrition is measured rather than reconstructed. None of them publish pricing, so every comparison starts with a demo and a quote.

A custom system. Worth considering when your operation has a shape the market does not sell, for example a dealer program plus a self-monitored commercial book. The CRM side of the same decision is in best CRM for security alarm companies.

The rule is short. If your dispatcher can see agreement coverage and recent signal history without leaving the ticket, your stack is fine regardless of what it is called. If they cannot, no amount of route optimization will fix your service margin.

The demo script

Take these into every demo and do not let the salesperson drive.

1. Open a service call on a monitored site. Show the active agreement, what it covers and warranty status, without a second screen.
2. Show me a false alarm callback. Where does the cause code live, and how do I list every site with three or more this year?
3. Import a no-signal report. Turn a central station export into scheduled work. Watch whether it becomes a queue or data entry.
4. Generate next quarter's inspections from contract terms and route them by postal code as a batch.
5. Filter the customer base by installed panel model. If they cannot, campaign work stays manual.
6. Book a three-day install, then drop a same-day emergency into that crew's day. Watch what the board does to the install.
7. Ask what the on-test step looks like on a ticket, and whether an incomplete clear blocks close.
8. Ask for the total price at your headcount in year two, including implementation, seat growth and any per-account fee.

Most vendors do well on one and three and stall on the rest, which tells you what you are buying.

The bottom line

Alarm shops feel badly served by dispatch software because the category was designed for businesses where the truck roll is revenue. In your business the truck roll is frequently a cost against a $30 monthly subscription, and the value of the whole company is a multiple of the subscriptions you keep alive.

That reframes what the board is for. It is not a tool for filling a day. It is a tool for deciding, before each truck moves, whether this visit protects an asset worth 30 times its monthly billing or quietly burns half a year of that asset's revenue. Buy the board that answers the payer question, ingests your signal report and holds the inspection calendar. The map with the pins is the least important thing in the room.