· 4 min read

Security Guard Companies Are Half Right to Fear AI Phone Agents

Your night dispatcher’s phone rings at 1:47 a.m. An officer posted at a warehouse says his car won’t start and he can’t make the 2:00 relief. You have thirteen minutes before that post goes dark and a property manager starts asking questions.

That moment is why most owners running 30 to 300 officers dismiss AI phone agents on the spot. Part of that instinct is correct and worth defending. Part of it is quietly costing you billable hours every week. Five beliefs, five blunt verdicts. (If the difference between an agent and the phone tree you already hate is fuzzy, read this first.)

”A bot can’t handle a 2 a.m. call-off. Coverage is life-safety.”

Half right, and the wrong half is the expensive one.

The decision is life-safety. The legwork isn’t. Once your dispatcher knows a post is going uncovered, the next twenty minutes are mechanical: pull the officers cleared for that site, rank by proximity and overtime status, call or text down the list, wait, call the next one, confirm, notify the account manager.

An agent works that list in parallel instead of one call at a time, logs every response, and hands the dispatcher a short summary: two officers available, one already at 38 hours this week. Your dispatcher still picks. Scheduling platforms in this space do part of this already. TrackTik publishes open shifts to a pool of eligible guards, and Belfry’s Shift Marketplace ranks suggested officers by availability, certification, distance, and overtime. A phone agent reaches the officers who don’t open the app at 2 a.m.

The math is the argument. Industry pricing guides put unarmed commercial posts around $25 to $45 per hour billed. An uncovered 12-hour shift is roughly $300 to $500 you can’t invoice, before any contract credit or the conversation about an empty guard shack.

”Our clients are property managers. They’d be insulted by an AI.”

Overblown.

Your property manager contacts are not calling for a relationship. They want to know why the March invoice shows 14 hours of overtime, whether you can add a post for a tenant event on the 22nd, and who was on site Sunday night. Those calls either get answered fast or sit in voicemail until Tuesday.

Clients do get insulted by three things: an agent fielding a complaint about an officer’s performance, an agent anywhere near a contract renewal, and an agent standing between an already-angry caller and a person. Route those to a named human immediately, no menu in between. And say plainly that the agent is automated. California’s bot-disclosure law (SB 1001) was written around online commercial persuasion, so how far it reaches into a phone call isn’t settled, but “this is an automated assistant for ABC Protective” costs you nothing and ends the argument.

”Guards won’t respond to an automated text asking them to pick up a shift.”

Mostly wrong. The format decides it.

Officers already ignore your texts. “OPEN SHIFT AVAILABLE, CALL OFFICE” gets ignored because it hands work back to the reader. “Warehouse post on Kensington, 2 a.m. to 10 a.m. tonight, $22/hr, 9 minutes from your address. Reply Y or N” gets answered because every decision is already made.

Two practical notes. Informational texts to employees who gave you their number for work purposes sit in a lower-risk category under the TCPA than marketing texts, but document that consent in onboarding paperwork anyway. And your contact list goes stale fast: ASIS International reported guard force turnover climbing to roughly 77% in 2024. An agent that flags dead numbers as it dials is doing real work.

”It’ll dispatch someone unlicensed or unarmed to the wrong post.”

A correct fear, and the reason this rollout needs one hard rule.

The agent proposes. It never assigns. Final dispatch stays with a human or with your scheduling system’s own eligibility gate.

California shows how much detail hides behind one officer’s name. Before a guard card is issued, an applicant completes 3 hours of Power to Arrest and 5 hours of Appropriate Use of Force training. After registration comes 32 hours of skills training within six months, including 16 hours in the first 30 days, then 8 hours annually. Status is publicly verifiable through the state’s license search, and armed posts require a separate firearm permit. That gets checked against the state record and your own file, never inferred from a phone conversation.

Post orders follow the same rule. An agent can read a post order to a covering officer. It should not improvise one.

”Incident and alarm calls would go to a machine.”

Correct. This line does not move.

An in-progress incident, an alarm response, a medical event, an officer who sounds like he’s in trouble: human, first ring, every time. If the agent can’t detect those and hand off within a few seconds, keep it off your main line entirely. Put it on a dedicated scheduling and billing number and let it earn the main line later. Fire protection companies land in the same place, starting on inspection scheduling rather than alarm calls.

Pick the Queue Nobody Fights Over

Start with hiring. A licensing-heavy pipeline plus 77% turnover means your recruiter spends the day asking the same six questions: current guard card, card number, overnights, reliable transportation, willing to work in Fontana. That screening is clean agent work, and it mirrors what staffing agencies do to win back recruiter hours.

This week, pull 30 days of call logs and sort them into four piles: call-offs, client admin, applicants, incidents. Count the applicant pile. That’s your pilot.

Sources

  1. ASIS International, guard force turnover — asisonline.org
  2. Belfry Software, how much security companies charge clients — belfrysoftware.com
  3. Belfry Software, security guard scheduling software — belfrysoftware.com
  4. Trackforce, TrackTik vs. Belfry vs. WinTeam — trackforce.com
  5. California BSIS guard card fact sheet — bsis.ca.gov
  6. CALSAGA training requirements FAQ — calsaga.org
  7. Belfry Software, security guard license lookup tools — belfrysoftware.com
  8. California SB 1001 (bot disclosure) — leginfo.legislature.ca.gov
  9. Perkins Coie on California's bot disclosure law — perkinscoie.com
  10. TCPAWorld, TCPA in the workplace — tcpaworld.com

Keep reading