Dev.to Security 🔐 Cybersecurity 👁 0 📖 6 min read

Security & Alarm Installation: Why Your Dual-Revenue Business Needs Two Phone Systems, Not One

Every other trade sells one kind of revenue. Security and alarm companies sell two simultaneously — and they behave nothing alike. The first is project revenue: an install with equipment, labor, wiring, permits, and a c

Every other trade sells one kind of revenue. Security and alarm companies sell two simultaneously — and they behave nothing alike.

The first is project revenue: an install with equipment, labor, wiring, permits, and a completion date. The second is recurring monthly revenue (RMR) from monitoring, the annuity that makes a well-run alarm company worth a multiple a plumbing company is not. RMR accrues whether anyone answered the phone today. It compounds with every site added. It is the number a buyer actually values.

Running both through one phone line, one calendar, and one billing system is where most alarm companies quietly break. The pattern separating operations that scale is simple: they stopped treating every inbound call as the same event.

The three callers who share your number

Technicians are in attics, crawlspaces, and ceiling grids. Pulling cable above a drop ceiling is not a state you interrupt for a phone call. In a shop with three techs and no dedicated office, the phone is essentially unattended between 8 AM and 5 PM. Meanwhile, three different callers dial the same number and need three entirely different conversations:

  • Homeowner shopping for cameras. Needs a consultative conversation and, almost always, a site survey appointment rather than a phone quote.
  • Landlord with a building that has an abandoned panel. A takeover — a distinct product with its own intake questions.
  • Existing customer whose siren has been shrieking since 2 AM. Highest priority, service path, immediate escalation to on-call.

Handling them identically fails all three. An answering service takes a message and hands you a name, which is close to useless when the difference between two categories is a technician being woken up or not. A phone tree is worse — it asks a frightened customer to navigate a menu.

What a takeover intake actually needs

A takeover — adopting an existing panel and sensors rather than installing new — is one of the fastest paths to RMR in the trade. It is priced almost entirely on information a scripted interview can collect:

  • What brand and model is on the wall, and how old is it?
  • Is it hardwired, wireless, or hybrid?
  • Does the customer have the installer code? (Without it, some panels cannot be reprogrammed and must be replaced. This single question determines the price more often than any other.)
  • How many zones and what devices?
  • Who monitors it now, and is there a contract in force?
  • Does it still communicate?
  • Is there an existing permit on file with the municipality?

Getting those seven answers on the first call means the site visit either becomes unnecessary or becomes a short confirmation. Not getting them means a technician drives out to discover a panel nobody can program.

Site surveys are not estimates

A site survey is not an estimate visit and it is not an install. It is a walkthrough that produces the information the install depends on: camera count and placement, existing infrastructure, network capacity, power availability, lighting conditions at night, and who actually has authority to sign.

That is a real appointment with a real duration, and it needs to occupy a slot on a specific person's calendar — usually a senior technician or the owner, not a junior installer. If your calendar treats "estimate" as a generic thirty-minute block, you will either underrun a complex commercial walkthrough or waste a lead technician's morning on a two-camera doorbell job.

The survey outputs belong in a permanent site record: camera positions, panel model, zone list, wire routes, network details, gate codes, and the customer's stated concerns. That record is what makes the second visit cheap, and it is what makes a service call two years later something other than an archaeology expedition.

The billing problem that breaks alarm companies

This is the layer that separates alarm companies from every other trade. Install revenue is a project: equipment, labor, possibly a deposit, a final invoice, sales tax on materials, and done.

Monitoring revenue is an annuity per site. It bills monthly or annually. It continues indefinitely. It has to survive a card expiring. And it has to be reconciled against what the central station is actually billing you per account.

RMR that quietly stops billing is the single most damaging silent failure in this business, because nobody notices a missing $42 charge the way they notice a missing $4,200 invoice — and twenty of those going unnoticed for a year is real money against the company's valuation.

What the operations layer has to do:

  • Hold both revenue types against the same customer and site record, so you can see what a site is worth in total.
  • Run recurring charges on a schedule with stored payment methods and automatic retry when a card fails, plus an alert when it keeps failing.
  • Track contract terms and renewal dates per site, so a three-year monitoring agreement reaching term is a scheduled conversation rather than a surprise cancellation.
  • Surface per-site profitability, because a site with a low monitoring rate and four service visits a year is losing money.

Three AI workflows that fit this trade now

1. Call classification before conversation. An AI receptionist's first job is not to sell — it is to classify. The six categories that matter: active alarm/trouble condition (highest priority, immediate escalation), non-urgent service need, new residential install prospect, new commercial prospect, takeover of existing system, and monitoring-only inquiry. Monitoring-only is the highest-margin call in the entire trade and the one most often handled poorly.

2. Site survey booking as its own appointment type. Separate durations, separate assignable resources. A residential survey books into a wide window. A commercial survey routes to the person who handles commercial. The booking tool needs to know the difference.

3. The 3 AM alarm call workflow. The call arrives frightened or annoyed. What has to happen: identify the customer and site immediately from the calling number, determine panel state, capture which zone or device, escalate to the on-call technician with all context already collected, log it against the site for false-alarm pattern visibility, and schedule the follow-up service visit in the same interaction. The thing to avoid is the sales script. Nobody at 3 AM wants a package comparison.

Your customers are already using AI to call you

Google announced this week that Duplex — the AI phone-calling system it first demoed in 2018 — is now built into Tasks in the Gemini app. Users can ask Gemini to call businesses for them: book appointments, check availability, ask about service prices. The AI clearly discloses itself, handles multi-constraint requests, and adapts when a receptionist suggests another slot.

For alarm companies, this matters in two directions. First, your inbound call volume is about to include AI callers from Gemini users checking availability or booking surveys. The classification and booking system you build now needs to handle both human and disclosed-AI callers cleanly. Second, the same technology stack is available to you: voice agents that can classify calls, collect the seven takeover answers, book site surveys into the right calendar slots, and escalate true emergencies — all while your technicians stay in the ceiling grid where they belong.

Honest boundaries

A voice agent can classify calls and collect structured information. It cannot climb an attic or read a panel model number off a keypad in a dark closet. The site survey is still a human visit. The install is still a human visit. The 3 AM alarm call still needs a human technician with a truck.

What AI changes is the front office — the thing that separates the alarm companies that scale from the ones that miss calls, misroute emergencies, and quietly lose monitoring accounts to competitors who picked up.

Struggling to separate your install pipeline from your monitoring billing? The AI Clarity Sprint is a $1,495 CAD fixed-fee service that maps your actual revenue streams, identifies where calls and bookings are leaking between your two businesses, and sets up the first automated workflow — typically call triage or RMR billing reconciliation — in two weeks. Learn more.

Sources: Run with Jarvis automation stack analysis (August 2026); Google Research blog, "How Google Duplex evolved to also call businesses for you in Gemini" (November 20, 2026). All claims attributed to third-party research; no personal business experience claimed.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.