By Greg Allan, tradesman and creator of Data First Coaching
Why do callouts quietly eat the margin on a service contract?
On paper, a monitoring or service contract for a commercial or strata client can look like clean recurring revenue, priced once and collected every month. The reality is different. Every time a camera drops off the network, an alarm panel throws a fault, or an access control reader stops reading a fob, the job often gets resolved the same way: send a technician to site.
That truck roll rarely gets booked as a cost against the contract. The technician's wage, the fuel, the hour or two lost that could have gone on a paying install or upgrade, none of it shows up as a line item eating into the service contract's gross profit margin. The contract still looks healthy on the P&L. The real margin, the one that matters, is being stripped out callout by callout, and nobody is tracking where.
What is the real cost of a truck roll that never gets logged?
Most security technicians can rattle off their monthly contract value without blinking, but few can say how many of this month's callouts were genuine onsite faults versus something that could have been checked remotely. That gap in the data matters, because every unlogged truck roll is unbillable labour masquerading as a cost of doing business rather than a cost that is actually chipping away at net margin.
Picture a CCTV and alarm business running forty service contracts across a mix of commercial sites and strata buildings. A handful of callouts a week for things like a camera reboot, a reset access control credential, or a false alarm trigger, each one pulls a technician off a paying job for an hour or more. None of those trips are quoted or invoiced separately because they sit inside the service contract. The cost is real. It just never gets counted.
How can a security technician use remote access to stop the truck roll before it starts?
You treat every unbillable truck roll the way you would treat a wholesaler run that eats a technician's afternoon: as something to track, question and test a fix for, not absorb as the cost of running the business. The fix is rarely a new policy on paper. It is a practical substitution that lets the job move forward without a technician leaving the van.
For a security technician, that substitution is remote access. A camera that has dropped off the network, an alarm panel reporting a fault, or an access control system refusing a credential can often be checked, reset or reconfigured from the office through the same remote login used for install and commissioning work. The job gets resolved. The technician stays on the paying job they were already on. The service contract keeps its real margin instead of leaking it out truck roll by truck roll.
What changes when AI agents handle the diagnostic check before a callout is booked?
An AI agent is software that does a job the way you would do it yourself, following your own rules, your own wording and your own judgement about when a site visit is genuinely needed. For a security business, that means the triage step, working out whether a reported fault is something a remote check can fix or something that genuinely needs a technician on site, no longer has to sit on an admin desk or in a technician's head.
Before a callout gets booked, an AI agent can work through the same questions a good tech would ask: is this camera or alarm fault one that has shown up before, has a remote diagnostic already ruled out a network or power issue, does the client's monitoring history point to something onsite can't fix anyway. The truck roll that does get booked is the one that actually needs a technician, not the one that could have been sorted with a remote session. That is two AI agents doing real office work: one working the diagnostic logic, another keeping the data first record of what was checked and what it found, so the pattern shows up next time instead of disappearing into another unbillable trip.
Can every callout be avoided with remote access?
No, and treating remote access as a way to avoid every site visit is its own mistake. Some faults are genuinely physical: a chewed cable in a roof space, a vandalised camera housing, a battery that has failed in an intercom unit, a wiring fault from a renovation or fit-out that has nicked through conduit. No remote session fixes a cut cable or a damaged lens.
The useful question is not whether remote access replaces every callout. It is which callouts, in your own data, are the ones that keep repeating for reasons a remote check could resolve. For a security technician, both situations show up in the numbers, not in memory. Some service contracts might carry a run of recurring access control glitches that remote diagnostics handle well. Others might be dominated by physical faults on ageing cabling that no amount of remote access will fix, and that points to a different conversation with the client about an upgrade. The data tells you which is which. Guessing does not.
How does Data First Coaching approach this?
Data First Coaching starts from the security technician's own numbers, not a guess about where callouts are coming from. Through the Trade Business Intelligence, Greg Allan's approach looks at what each service contract is actually costing in technician time once every truck roll, billed or not, is counted against it, then works back to find where the pattern starts: which sites, which fault types, which clients call before anyone has tried a remote check.
That is where the real problem usually sits, not in the callout itself but in what happens before it is booked. The how, building the checks and the agents that catch it early, is worked through inside the Academy, with members, because the Trade Business Intelligence is powered by every member and the Academy is built for owners who are open minded, innovative and willing to share what they learn.

