Saturday night, 22:43, and a two-technician locksmith outfit off Beyers Naudé Drive in Randburg has its weekend phone doing what weekend phones do. Three missed calls from an unknown Joburg cellphone in the last twenty minutes. A voice note on WhatsApp Business from a woman in Melville who has locked herself out on the balcony while her toddler is asleep inside. Two messages from a managing agent in Craighall Park about a jammed communal gate. A missed call from Kempton Park, no message left. Roshan, the owner, is at his sister-in-law’s birthday, phone face-down on the table.

By 08:00 Sunday he will pick up the phone, hear the toddler-in-Melville message, call back, and get a polite “we already got someone last night, thanks.” That job was a R2,600 emergency call-out he trained eleven years to be able to do at midnight. It went to whoever answered first.

AI does not open a Kaba safe. It does not pick a Mul-T-Lock. What it can do is stop those jobs walking to the competition while the owner is sitting at a family dinner.

Where the money actually goes at 22:43

Emergency locksmithing in South Africa is an asymmetric business. A weekday rekey booked for next Tuesday afternoon runs at fifty percent margin on a good week. A Saturday-night lockout on a private residence in Fresnaye, priced honestly with the after-hours loading applied, is often the entire week’s profit in a single hour. Miss five of those a month and the shop is on the edge, working harder to earn less.

The leaks are specific and repeatable across every one-to-five-technician outfit we have looked at.

None of those is a locksmithing problem. All of them are admin-arriving-when-the-tech-is-tired problems, and admin problems are the kind AI actually handles.

The first-minute capture layer

The single change that shifts the business is answering every enquiry within a minute, in writing, twenty-four hours a day. Not with the corporate “we have received your message” template. With something a mother locked out on a Melville balcony at 22:43 actually reads and responds to.

A properly built WhatsApp Business first-response, tied to the outfit’s own number, does four things in under sixty seconds. It confirms the message reached a real business, not a void. It asks two questions the technician needs answered before he gets in the bakkie: the actual street address, whether anyone or a pet is inside, whether the caller is at the property now. It states the after-hours call-out fee, in rands, before the tech is dispatched. And it commits to a person calling back within a stated window, say five minutes, with a firm ETA.

The voice note is the hardest part and the most important. A woman standing on a balcony at that hour is not going to type. She is going to hold down the microphone and speak. The system transcribes that voice note within seconds, extracts the address, the phone number if she reads it out, and the nature of the emergency, and puts it in front of the owner as one line of text with the audio linked underneath. He does not scrub through a six-minute file at a family dinner. He reads one line and decides.

That is the entire mechanism. It is not clever. It is just present at 22:43 when he is not.

What a bot must never do at a locksmith

Some of the honest limits.

Dispatch decisions. The bot does not decide which technician goes. That is a routing call informed by who is in what state: sober, close by, awake, willing to attend a residential job alone at midnight. Every dispatch we have seen go wrong went wrong because someone tried to shortcut this.

ETA promises. The customer wants “how soon.” The bot must not answer that. What it can say is that the technician on standby will confirm an ETA in the next five minutes. A wrong ETA at 23:00 is worse than no ETA. It turns a warm lead into an angry one before the bakkie leaves the workshop.

Verifying the person at the door. A locksmith is being asked to defeat a lock. The person on the phone claims to live there. In some circumstances, in some suburbs, that claim needs a proof-of-address or a landlord confirmation before the job proceeds. That judgement call is not a chatbot’s call. It sits with the technician standing at the gate.

Anything security-classified. If the enquiry is about a safe, a business alarm interlock, or a firearm safe, the bot’s job is one message: “One of our accredited technicians will call you back personally.” A locksmith outfit doing safe work sits under PSIRA registration as well as SALA membership rules, and a bot chatting freely about safe types is a compliance liability the owner does not need.

The rule I use with every trades business we build for: the bot handles the inbox, the human handles the decision, and the boundary between the two is written down so nobody argues about it at 02:00.

The pricing argument that never happens

Most of the resentment in an after-hours locksmith business is not the tiredness. It is the arriving-in-a-Camps-Bay-driveway-at-midnight-to-be-haggled-with feeling. Fixing that is boring and mechanical, and every honest owner we have worked with wishes they had done it years earlier.

Before dispatch, the customer receives, on WhatsApp, one message with three lines. The after-hours call-out fee, in rands, in bold. The estimated additional work range for a standard house lockout, say R400 to R1,200. And one sentence saying that if the job turns out to be more involved — a broken key extracted from a mortice lock, for instance — the technician will call and confirm the additional cost before starting. The customer replies with a single word of confirmation. The tech leaves.

That message does two things. It filters out enquiries that were never going to convert at an emergency price, and it removes the driveway argument on the ones that do. In practice most SA locksmiths who add this layer see roughly one in four after-hours enquiries drop off at the pricing message, and roughly zero of the remaining ones argue on arrival. That is exactly the right trade.

Insurance and body-corporate work: the six-week paperwork tail

A Sunday-morning break-in repair in a Bedfordview cluster complex generates two conversations. The urgent one is with the homeowner. The slow one is with Santam or Old Mutual and the body corporate’s managing agent, and it usually happens six days later, or six weeks later, or never.

This is the other side of the automation. A dictated voice note from the technician at the scene — unit 14, front door frame splintered on the strike-plate side, replaced Yale lock and reinforced strike, four hours on site, photos on the group — becomes a draft invoice pre-populated with the tech’s line items, a draft insurance-facing damage report with the photos attached, and a draft update for the body corporate WhatsApp group. The owner reviews all three in fifteen minutes on Monday morning instead of losing a Wednesday to it, or losing the invoice entirely.

Xero is where most one-to-five-technician outfits keep books. Yoco or iKhokha is often the card device in the bakkie. Nothing here requires a new platform. It requires the message from the scene to be caught before the technician’s memory of the frame damage fades.

A note on SALA, PSIRA, and the customer at the door

South African locksmiths are not tightly regulated at a national level. The South African Locksmiths Association is a voluntary body, membership is a genuine trust signal, and reputable outfits are members. Safe work, alarm-linked lock work, and any armed-response coordination pull the operation into PSIRA registration territory as well.

None of that is a reason to avoid automation. It is a reason to build automation that never leaves the outfit in a position where a customer could later claim they were misled by “your automated system.” The rule: any commitment that goes to a customer — pricing, ETA, technician identity, whether the job can be done at all — carries a human sign-off before it lands. The bot drafts, the owner or the standby technician approves, and the message goes out in the business’s own voice from the business’s own WhatsApp number.

Insurers ask for this. The Information Regulator would ask for it if it ever came up. And customers, in my experience, treat a locksmith who confirms the price in writing before turning up the way they treat a doctor who confirms the diagnosis in writing before prescribing. As a professional.

Where to start

The whole thing is tempting to build at once, and that is the way it fails. The outfit that gets value out of this picks one thing, gets it running for a month, and only then adds the next.

For a two-to-five-technician SA locksmith, the right starting point is the after-hours WhatsApp first-response with the voice-note-to-line-of-text loop, tied to a five-minute human callback commitment. That single layer catches the R2,600 Saturday-night lockout that used to walk. It requires no new phone number, no change to what the technician does on site, and no new bookkeeping. It runs on the WhatsApp Business number already printed on the bakkie.

Once that has run quietly for a month, and the tally of Monday-morning “we already got someone” replies drops to near-zero, the pricing-in-writing layer goes in front of dispatch, and the voice-note-to-invoice loop from the scene follows.

Two owners we have built this for describe the same shift. The Saturday-night phone is no longer the enemy. The Monday-morning inbox is not a graveyard of missed jobs. And the technician arriving at a Camps Bay driveway at midnight is doing so having been paid, in writing, before he left the workshop. Which, when you have been doing this work for eleven years, is not a small thing.