Alarm Company Software: Monitoring, Service and Billing, and Where AI Helps

Alarm company software has to keep one customer record that ties together the monitoring account, every service visit and the monthly invoice, so a signal, a technician job and a charge never drift apart. AI helps with the admin around that record, such as call summaries, visit reports and payment chasers, and stays out of signal handling.

The costly failures sit in the gaps between systems: an account that is monitored but never invoiced, or one still invoiced after the monitoring centre removed it. Ask every vendor how it prevents those two cases before you ask about features. A worked example further down puts a price on one such gap for a 1,200-account company.

Follow me on Instagram@sagnikteaches

Two kinds of alarm software, and which one you are buying

Vendor pages blur two different products, and the mix-up wastes demo time. The first is central-station automation: the software a monitoring centre uses to receive signals, show them to operators and follow each account's call list. The second is the dealer back office: customers, contracts, service tickets, inventory and recurring invoices for the company that sells and installs the systems.

Connect on LinkedInSagnik Bhattacharya

The pages I read in October 2026 split along that line. MicroKey separates Millennium Monitoring, which it aims at central stations and monitoring centres, from AutoBiller Plus (recurring billing and accounting built for alarm dealers) and Service Management (jobs, dispatch, inventory and customer history). Bold Group lists stages and Manitou for monitoring stations, dealers, integrators and security operations centres. SecurityTrax calls itself an operating system for security dealers, with leads, customers, scheduling, work orders, inventory, billing and reporting in one place.

Subscribe on YouTube@sagnikteaches

If you pay a third-party monitoring centre per account, sometimes called wholesale monitoring, you need the second kind plus a dependable link to the centre's account list. If you run your own centre you need both, and the automation software is a separate buying decision that this tutorial does not try to cover.

One customer, from sale to cancellation, step by step

Vendor listicles rank products. A map of steps ranks nothing, but it shows where software has to do something. Walk one customer through the table and mark, for your current setup, which system holds each fact and who re-types it. Every re-typed cell is a place where two records can disagree.

Steps 3, 6, 9 and 10 are where the money leaks, because each one changes a record in two systems. Steps 1, 2, 4 and 5 are ordinary back-office work that every product handles to some degree. When you judge software, spend your demo time on the first group.

Monitoring: what the dealer side has to show and sync

The centre handles signals. Your software handles the account that the centre's list is built from, so the test is whether the two agree. Five things to demand:

• One account number, formatted the same way in both places. Leading zeros are the usual casualty: a spreadsheet that opens 0042 as 42 will match the wrong account.
• Status values that mean the same thing. If billing says "suspended" and the centre says "out of service", write the translation down before go-live.
• Signal history and last-test dates you can read without phoning anyone. A report you can run on request is enough.
• A list of accounts that have stopped reporting, each one turning into a service ticket with an owner.
• One controlled route for call-list changes: who may ask, how the caller is verified, who enters it, where it is logged.

Test mode deserves its own line. Most monitoring centres expect a technician to put an account on test before working on the system and take it off afterwards, though each centre sets its own procedure. If your software records both times against the service ticket, an account left on test shows up the same day. If it cannot, keep a morning list of every account currently on test and clear it before the first customer call of the day.

Picture a dealer whose technician swaps a panel and forgets the second call. The account stays on test for nine days, the customer believes they are protected, and the only trace is a status that nobody was looking at. Nothing in the billing system would ever flag it, which is why the status needs a ticket, a time and a name against it.

Service visits: what the technician needs at the door

A good ticket opens with the answers already filled in. The technician should see the panel make and model, communicator type, zone list, battery fitting dates, open trouble signals and whether the customer has a monitoring or service plan. It closes with parts used, photos, test times, the signature and any follow-up. SecurityTrax describes work orders that link jobs to customers, appointments, equipment and documents, and MicroKey's Service Management lists jobs, dispatch, inventory and customer history, so both cover the basic shape.

Here is a filled-in ticket of the kind worth asking a vendor to reproduce on screen during a demo. All details are illustrative.

SERVICE TICKET  ST-0000 (illustrative)
Customer record: [first name], one site, monitored, plan MON-STD at $39.95 a month
Equipment on file: panel (model recorded at install), 6 zones, cellular communicator, 2 keypads
Reason: keypad beeping, "system trouble" shown
Found: panel backup battery low; rear door contact (zone 4) loose
Work done: battery replaced (1 part, from van stock); contact re-fixed and tested
Test: on test 10:05 / off test 10:40 (logged by technician)
Photos: battery label, contact after repair (2)
Signature: captured on phone
Billable: labour 0.75 h; battery; no call-out fee (monitored customer)
Follow-up: battery check in three years; none open today

Notice what the ticket does beyond recording work. The test times protect the customer, the plan field decides whether a call-out fee applies, and the parts line feeds stock. If a vendor can only offer a free-text notes box for all of that, the ticket will be written differently by every technician.

Recurring billing: eight rules a bill run has to follow

1. Bill from plan lines, not from last month's invoice. Each site carries lines such as monitoring, communicator fee and service plan, and the run builds the invoice from them.
2. Prorate part months one agreed way. An activation on the 19th of a 30-day month at $39.95 costs 12 days, so 12 ÷ 30 × $39.95 = $15.98. The software should do that sum, not a person.
3. Track "paid through" dates for quarterly and annual pre-billed plans, so a renewal is a date, not a memory.
4. Apply price rises by date, to a list. A $3 rise on 800 accounts is $2,400 a month, or $28,800 a year. Missing 60 accounts quietly costs $180 a month, and the gap persists until someone looks.
5. Collect on a fixed day and show failures the same day, with the customer, amount and reason in one list.
6. Chase in stages, each with its own message and owner. The tutorial on chasing unpaid invoices with AI covers wording that stays polite.
7. Handle multi-site customers on one statement while keeping a separate monitoring line per site.
8. Stop billing on the cancel date set at the centre, with a clear rule for overlap days, so neither side has to guess.

Rules 3 and 8 are where alarm billing differs most from ordinary subscription billing, because a monitoring contract has a term, a renewal and a physical system left behind. The renewal letters and reminders tutorial shows how to word the notices that rule 4 depends on.

A 1,200-account dealer, 42 mismatches and $17,700 a year

Take a dealer with about 1,200 monitored accounts at an average of $39.95 a month. Nobody has ever matched the billing list to the monitoring centre's list, because each looks plausible on its own. On a quiet Friday the office manager exports both.

The two exports and the match

Billing shows 1,184 accounts with an active monitoring line. The centre shows 1,213 active accounts. Matching on the monitoring account number gives 1,171 present in both, 42 active at the centre but absent from billing, and 13 billed but not active at the centre. The sums tie: 1,171 + 42 = 1,213 and 1,171 + 13 = 1,184.

The spreadsheet step has one trap. Import the account column as text, because opening the file directly strips leading zeros. Then ask an assistant to write the formula rather than do the matching itself, since an assistant matching 1,200 rows in a chat will quietly drop some.

Two sheets. "Billing": column A = monitoring account number stored as text (for example 0042), column B = monthly amount.
"Centre": column A = account number stored as text, column B = status.
Write a formula for a new column C on Billing that returns "Not at centre" when the account number is missing from Centre, and "OK" otherwise.
Compare the text exactly: 0042 and 42 must not count as the same account. Explain the formula in one sentence.

Expect an answer built on SUMPRODUCT with an equals sign, such as =IF(SUMPRODUCT(--(Centre!$A$2:$A$2000=A2))=0,"Not at centre","OK"). COUNTIF is the version an assistant offers first, and it treats numeric-looking text as numbers, so it can match 0042 to 42. Test the formula on five accounts you know before trusting the other 1,195.

What the 42 turned out to be

• 19 customers had moved. The new address was activated at the centre, but the billing line stayed with the old record.
• 11 had an add-on fitted, such as a cellular communicator, with no billing line.
• 7 were promotional months that never converted to paid.
• 5 were staff homes and test accounts that are meant to be free.

That leaves 37 accounts that should be paying: 37 × $39.95 = $1,478 a month, about $17,700 a year. The 13 billed-but-unmonitored accounts are the more urgent half of the problem. Those customers may believe they are protected while the centre holds no active account. Contact them before you do anything about the revenue.

What software would cost against that

SecurityTrax publishes usage-based pricing, so the maths is checkable. At 1,200 active customer records at $0.15 a month, that is $180. Fifteen new customers a month at $3 each adds $45. Six people on the Operations Plus bundle at $5 each adds $30. The total is $255 a month, plus a $250 one-off setup fee, against a $250 monthly minimum that the usage just clears. Its AI, called Intelligence, is billed in tokens outside that minimum: each paid month brings 5,000 tokens that last 30 days and do not roll over, and further use draws on a prepaid wallet with spend limits you set. Even with the 37 recovered accounts as the only gain, the recovered $1,478 a month covers the bill several times over. Software did not find the gap, though; the match did. The software's job is to make sure the next gap closes itself.

Customer portal and call logging, the features that sound small

Portals are the feature most often assumed rather than checked. MicroKey's page describes no customer portal and links only to a pay-my-bill page. SecurityTrax lists a Secure Information Portal inside its Operations Plus bundle and says it needs a payment gateway. ServiceM8's asset pages describe a QR code that lets a client view equipment details and report an issue, which suits equipment records more than invoices. Ask to see the portal in the demo, logged in as a customer, and check four things: paying an invoice, updating contact numbers, seeing past visit reports and requesting a visit.

Many customers know only the app that arms their system, so ask how the arming app and the billing portal relate. Two logins for two things is workable if you tell people up front.

Call logging is the other quiet gap. Every customer call should land on the customer record with a reason, an outcome and a follow-up date, whether a person types it or a phone system supplies it. Add-ons exist on the general field service side: Jobber Receptionist is a $29 a month add-on covering 30 conversations, then $0.79 each, and ServiceM8 lists ServiceM8 Phone from $19 a month, with call recording and transcription among its features. If you add an AI voice line, write its escalation rules first, and tell callers when you record.

SecurityTrax, MicroKey, Bold Group and field apps compared

Prices below are USD list prices from the vendor pages. Vendors run promotions, and several publish no price at all.

None of the three general field service pages lists a monitoring-centre connection, so a company on one of them matches account lists by hand. I read pages, not live accounts: a demo with your own data is the only test that counts.

Choosing by size

These thresholds are my rules of thumb, not vendor guidance.

Where AI earns its place, with prompts you can copy

The wins are in writing and summarising, where a person reads the result before it leaves the building. SecurityTrax's token-priced Intelligence is one route and a general assistant is the other. The assistant needs copy and paste and de-identified text, but it is cheap and available today; the in-product tools see your records directly and bill by use. For most small dealers I would start with the assistant and revisit when the volume justifies it.

Visit reports a customer can read

Technicians write notes in shorthand. Paste the shorthand, not the customer's details:

Turn these technician notes into a visit summary for the customer. Plain words, under 110 words, no zone numbers, no codes, no promises about future performance. Do not add facts that are not in the notes.
Notes: keypad beeping, panel battery low, replaced battery; rear door contact loose, re-fixed, tested ok; on test 10:05, off test 10:40; next battery check in three years.

An illustrative result:

Thanks for having us out today. The keypad was beeping because the backup battery in your control panel was low, so we fitted a new one. We also re-secured a loose door sensor at the rear and tested it. Your system was on test with the monitoring centre from 10:05 to 10:40 while we worked and is back to normal monitoring. We suggest a battery check in three years. Call us if the keypad starts beeping again.

What I would fix: confirm the times match the ticket, remove "zone" detail if it crept in, and delete any warranty or battery-life claim the assistant added from its own knowledge. A summary that invents a guarantee is worse than none.

Overdue notices in three stages

Three messages beat one angry one. Draft them once, have your adviser approve the last, and keep them in your billing system as templates.

Ask the assistant for the three versions from your contract wording, then read the final notice aloud. Suspending monitoring on a life-safety system is a decision for a person who has read the contract, so the template should end with a name, not a robot.

Call notes without codes

For phone calls, the assistant turns a transcript or your quick notes into a record with four fixed fields: reason, system mentioned, what we promised, follow-up date. Tell it to replace any passcode, alarm code or verbal password with "[code withheld]". Check the output for one thing in particular: invented callback times. An assistant asked for a "follow-up date" with none in the notes will often supply one.

A monthly recurring-revenue note

Export four numbers and let the assistant write the paragraph, then do the sum yourself. Opening recurring revenue $48,420, new accounts +$2,115, cancellations -$1,630, so closing should be $48,905. If the paragraph says anything else, discard it. For ordinary price-rise letters and renewal reminders, the tutorial on alarm leads and follow-up and the renewal tutorial above give you wording to start from.

Where AI stays out of the loop

• Signal handling and dispatch. Operators follow each account's call list and the centre's procedures. An AI agent on your phone line should not verify a passcode, cancel a dispatch or promise a response time.
• Call-list and contact changes by email or chat. Changing who gets called is exactly what an impostor would request. Route it to a person, with a verification step the software records.
• Codes and passwords. Keep them out of every note an assistant can read.
• Fire alarm decisions. A chatbot can answer scope questions, as covered in the fire alarm servicing support tutorial, but it should not interpret a fault or recommend isolating a device.
• Suspending or ending monitoring. A named person decides, after reading the contract.

Before you switch on any vendor AI, ask whether it is on by default, what it costs, whether it can be turned off and whether your customers' data trains anyone's model. The ten-question AI vendor questionnaire gives the security half of that conversation.

Twelve questions to put to every vendor

1. Can I export every customer with monitoring account number, plan, monthly amount, status and last invoice date as one file?
2. When I change an account's status here, which changes reach my monitoring centre automatically and which do I re-key?
3. Does cancelling a monitoring plan stop the next invoice, and does stopping an invoice flag the monitoring account?
4. How are part-month starts, price rises and annual pre-billing handled, and can I schedule a rise for a list of accounts with notice letters?
5. Which payment methods can customers save, what happens after a failed payment, and who sees it?
6. What does a technician see on a phone, and does it work without a signal in a basement plant room?
7. Can a ticket record when an account went on and off test, with names and times?
8. What can a customer do in the portal, and is it the same login as the arming app?
9. How are inbound calls logged to the customer record: typed, recorded, or fed from the phone system?
10. Which features use AI, what does each cost, can each be switched off, and is customer data used to train a model?
11. What will it cost at 1,000, 2,500 and 5,000 accounts, counting setup, user fees, SMS and payment processing?
12. How do I get my data out if I leave, in which format, at what cost, and who does the migration?

Write the answers down in a sheet, one column per vendor, and score each from 0 to 2. A vendor that answers question 1 with "we can run that report for a fee" has told you how exit will go.

A 30-day trial that proves the software before you migrate

Do not move 1,200 accounts on the strength of a demo. Load 50 real accounts, including awkward ones, and run these checks over a month:

1. Days 1 to 3: import the 50 and compare plan, amount and account number against your old records. Zero unexplained differences is the pass mark.
2. Days 4 to 10: run five life events end to end: a new activation, an add-on, a house move, a price rise on 10 accounts and a cancellation. Time each one and count how many fields you re-keyed.
3. Days 11 to 20: run a parallel bill run for the 50 and compare invoice totals with your old method to the cent.
4. Days 21 to 30: have two technicians close real tickets on phones, including test start and end times, then match the ticket list to the invoice list.

Finish by repeating the account match from the worked example. If the new system produces a mismatch on 50 test accounts, it will produce hundreds on 1,200.

Questions alarm company owners ask before buying

Do I need central station automation software?

Only if you run your own monitoring centre and receive signals yourself. A company that pays a third-party centre per account needs the dealer back office instead: customers, service tickets and recurring invoices, plus a dependable way to keep its account list in step with the centre's. Buying centre automation by mistake is a common and expensive demo detour.

Can a general field service app run an alarm company?

For a small installer with few monitored accounts, often yes. Apps such as ServiceM8, Jobber and Housecall Pro schedule visits and send invoices. None of the pricing pages I read lists a monitoring-centre link, so you would match the two account lists yourself each month. Past a few hundred monitored accounts that routine becomes a risk.

How often should billing be matched to the monitoring centre?

Do the first match now, then monthly before the bill run. Add a quick weekly check of accounts that changed status: activations, moves and cancellations. The point is to catch a monitored-but-unbilled or billed-but-unmonitored account within weeks, not at the annual review.

Is it safe to put customer details into ChatGPT or Claude?

Keep names, addresses, passcodes and zone detail out of any assistant. Paste de-identified notes, and use a business plan, since ChatGPT Business and Claude Team do not train on business content by default. Never paste an alarm code or verbal password, whichever plan you use; those belong only in the monitoring system.

Further reads

• CCTV Maintenance Contract: Remote Health Checks and Renewals With AI — The same recurring-contract logic applied to camera systems.
• AI Job Scheduling and Dispatch for Trades and Field Service Teams — How scheduling and dispatch tools for field teams compare.
• Alarm Installation Business Marketing: Contracts and Referrals With AI — Contract wording and referral habits for alarm installers.
• Setting Up an AI Answering Service That Never Misses an Emergency — Emergency-call rules when AI picks up the phone.
• Pool Service Business Software Compared: Skimmer, GorillaDesk and Jobber — Another recurring-visit business compared tool by tool.
• AI Camera Software for CCTV Installers: Analytics You Can Sell Clients — Human detection, line crossing, counting and plate recognition compared for installers, with a 14-day false-alert test, privacy checks and margin sums.
• AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.

Sources: SecurityTrax home and pricing pages, MicroKey home and pricing pages, Bold Group home page, the Jobber, Housecall Pro and ServiceM8 pricing pages, and ServiceM8's asset-management and phone feature pages, all read in October 2026.