Roadside and Motor-Club Dispatch Calls (2026): The B2B Volume Most Locksmith Shops Handle Badly

Roadside and Motor-Club Dispatch Calls (2026): The B2B Volume Most Locksmith Shops Handle Badly

Most locksmith shops treat every ringing phone the same way, and for retail work that is roughly correct. Network dispatch work is a different animal, and shops that run it through the retail script lose accounts without ever understanding why.

As of August 2026, a large share of automotive lockout volume in any metro moves through motor clubs, roadside assistance programs bundled with insurance policies, and vehicle manufacturer roadside benefits. That work does not arrive as a customer asking for a price. It arrives as a dispatcher on the phone or a job offer in an app, with the rate already set, a location, and a countdown. Everything a shop does well on a retail call — qualifying, quoting, building value — is irrelevant, and some of it is actively counterproductive.

This is an operational guide to that channel: how the work reaches you, why it behaves differently, what the economics honestly are, the single failure mode that costs shops these accounts, what has to be captured on a dispatch call, and how to keep network work from cannibalizing your retail day.

How network work actually reaches a shop

There are two arrival patterns, and most shops that do this work see both.

The dispatcher call. A human at a motor club or roadside network calls your shop directly. They have a member with a lockout or a lost key, they have a location, they have a covered benefit, and they need to know whether you will take it and how fast you can be there. The conversation is short and transactional. They are not evaluating you. They are filling a job.

The app or portal offer. Newer networks push jobs to enrolled providers electronically. A job appears with location, vehicle, service type, and rate, and there is an acceptance window measured in minutes. If you do not accept, it goes to the next provider on the list, and your acceptance rate is recorded.

Both patterns share the defining trait: someone else has already made the decisions your retail call is designed to make. The customer's problem is diagnosed, the service is categorized, the price is set by contract, and the buying decision has been made by a third party. What remains is a yes or a no, and how fast you can produce it.

Why this is not a retail call

The differences are structural, not stylistic. Running a retail script at a dispatcher does not just waste time — it signals that you do not do this work.

The price is already set. Network rates are contracted. There is no quote, no upsell inside the covered scope, and no negotiating with the dispatcher, who has no authority to change a number anyway. A shop that starts pricing on a dispatch call reads as unfamiliar with the channel.

The decision is accept or decline, on a clock. Retail calls tolerate a callback. Network calls do not. The window is short by design, because the network's obligation is to the member and its metric is time-to-service. Miss the window and the job is gone before you have decided.

The caller is not the vehicle owner. The dispatcher has never seen the car. They are relaying what the member told them, which means the vehicle information is second-hand and sometimes wrong, and any question that requires the member's judgment has to be routed through a callback rather than answered on the line.

The data you need is different. On a retail call you are collecting the information required to quote. On a dispatch call you are collecting the information required to find a specific vehicle in a specific place and complete a job whose price is not in question.

Your performance is measured and scored. Retail customers judge you one job at a time. Networks maintain acceptance rates, on-time arrival, completion rates, and callback rates, and route future work accordingly. That scoring is the entire economics of the channel, which is the next section.

	Retail consumer call	Network or motor-club dispatch call
Who is calling	The vehicle owner, usually stressed and on scene	A dispatcher or an app, relaying second-hand details
What is being decided	Whether to hire you, at what price	Whether you accept a job at a rate already fixed
Time pressure	The caller will call competitors in minutes	A formal acceptance window, often a few minutes
Price	Quoted from your price book, negotiable in practice	Contracted, non-negotiable, lower than retail
Core data to capture	Vehicle, service, location, price agreement, name	Member or PO number, precise location, vehicle, key type, ETA commitment, dispatcher callback
What loses the job	Not answering, or a price the caller rejects	Missing the acceptance window, or a missed ETA
Consequence of failure	One lost job	A lower routing priority on every future job

The economics, honestly

Anyone selling you on network volume will tell you it fills your schedule. That is true. It is also incomplete.

Network rates are lower than retail. That is the deal. The network aggregates demand and takes a spread, and the provider trades margin per job for volume that arrives without marketing spend. Nobody should enroll expecting retail economics.

The value is dead time and truck density. Network work is worth taking when the alternative is a tech sitting still. A 10 AM Tuesday with nothing on the board is a bad hour at any rate above your marginal cost. Similarly, if a network job sits four minutes from a retail job already scheduled, the incremental cost of taking it is small and the effective hourly rate is fine. Two network jobs and a retail job in the same ZIP is a good afternoon. One network job forty minutes out, alone, usually is not.

Taking network work during your retail rush is how shops lose money. This is the failure that shows up on a P&L as "we're busier than ever and making less." A Friday evening when retail lockouts are stacking up is the worst possible time to send a truck on a contracted-rate job. The opportunity cost is not the network rate versus zero. It is the network rate versus the retail job you turned away, and that comparison is frequently ugly.

Which means the accept/decline decision cannot be made in isolation. It has to be made with the retail workload visible next to it. A shop that decides on network jobs one at a time, without seeing what else is on the board, is guessing.

The volume is real and it smooths. Network work does not care about your seasonality the way retail does, and it arrives at hours when retail is thin. Used as a filler and a density tool, it is a genuinely good channel. Used as a primary revenue line, it caps your margin permanently.

The failure that actually costs shops these accounts

Ask a network coordinator why a provider stopped getting work and the answer is almost never price or quality. It is availability.

Here is the sequence, and every shop that has done this work recognizes it.

A dispatcher calls at 2:40 on a Wednesday. Your tech is under a dash with a column apart, and he is the person the shop phone forwards to. The call rings out. The dispatcher does not leave a voicemail, because a voicemail is useless to someone with a member waiting — they hang up and call the next provider on the list. Thirty seconds, and you never knew the job existed.

That happens three times in a month. Your acceptance rate on the network's dashboard is now a number that puts you lower in the routing order. Lower in the routing order means you get offered the jobs the higher-ranked providers already declined, which are the far ones and the awkward ones. Those are harder to accept profitably, so you decline more, which lowers the score further.

Nobody sent you a warning. The account did not get cancelled. It just quietly stopped producing, and six months later somebody in the office says "we don't really get much from them anymore" and everyone assumes rates or competition.

The mechanism is simple and worth stating plainly: in this channel, not answering is not neutral. It is scored. A retail caller who gets voicemail is one lost job. A dispatcher who gets voicemail is one lost job plus a permanent adjustment to how much future work you are offered.

The corollary is the busy-signal problem, which is worse for network work than retail. A dispatcher calling while your line is occupied does not wait. The general shape of that problem, and why concurrency matters more than speed, is covered in simultaneous calls and the never-busy line.

What you must capture on a dispatch call

The capture list for a network job is short, specific, and different from retail. Missing any one of these costs a callback to the dispatcher, which costs time you do not have inside an acceptance window.

Member number, PO number, or job ID. This is the billing key. Without it you did a free lockout. Read it back and confirm digit by digit, because it is spoken over a headset in a call center.

Location, precise enough to find one car. This is the single most common failure and the most expensive one. "The Walmart on Cooper" is not a location. A mall lot, a hospital garage, an apartment complex, or a big-box parking field can absorb a tech for twenty minutes of driving in circles while the clock the network is measuring keeps running. What you need is the lot section or nearest cross street, the level and row if it is a garage, the entrance the vehicle is nearest to, and ideally a dropped pin passed through to the member. Then it has to reach the tech's phone as coordinates, not as a paragraph. That is exactly what GPS-aware dispatch is for — the routing is only as good as the point you feed it.

Vehicle year, make, model, and color. Color matters here in a way it never does on a retail call, because the tech is identifying a vehicle in a field of vehicles. Confirm the year against the model generation if the dispatcher sounds unsure, since the information is second-hand.

Service type: lockout, or key. A lockout is an entry job. A lost-key or all-keys-lost job requires programming equipment, possibly a key blank on the truck, and a different time estimate — and on many networks it is a different covered benefit or not covered at all. Establishing this before accepting prevents the worst outcome in this channel: arriving on a job you cannot complete. How key jobs get scoped by year, make, and model is worked through in how AI quotes car key replacement.

The ETA you are committing to. Not an optimistic one. The network measures arrival against what you said, and a chronically missed ETA damages standing faster than a decline does. Declining a job you cannot reach in time is a better outcome than accepting and arriving late.

Who to call back, and how. The dispatcher's direct line or the network's provider line, plus the member's own number where the network allows it. When the tech is on site and the member is not at the vehicle, this is what saves the job.

Six items. Every one of them is a data field, not a judgment. Which is precisely why this call is a good fit for automated intake — there is nothing to negotiate and nothing to persuade, only information to capture accurately and route fast.

The reverse case: a retail caller who mentions coverage

This one costs shops real money and almost nobody has a rule for it.

A retail customer calls directly. Mid-call, they say some version of: "Actually, I think my insurance covers this," or "I have roadside on my card, would that pay for it?"

There are three ways to handle it and only one is correct.

Wrong answer one: ignore it and quote retail. The customer books, then calls their coverage provider afterward, discovers it would have been covered, and now feels they were taken advantage of. That is a chargeback conversation, a bad review, or both.

Wrong answer two: apply the network rate on the spot. This is the expensive one. You have just discounted a retail job to contracted pricing with no contract, no PO, no member verification, and no network paying the difference. You are performing network work at network rates without the network's volume — the worst of both structures. Shops do this constantly because it feels like customer service.

Correct answer: separate the two transactions and let the customer choose. The framing is short and honest:

"You might have coverage — a lot of policies and card benefits include roadside. If you want to use it, call the number on your card or policy and have them dispatch it; whoever they send will be paid under your benefit. If you'd rather not wait on that call, I can have someone out to you at [your retail price] and you can submit for reimbursement if your policy allows it."

That is the whole answer. It respects the customer, does not pretend the benefit does not exist, and does not hand them a contracted rate they are not entitled to. Some customers hang up and go through their club. That is fine — if their club dispatches to you, you get the job at the network rate you already agreed to, and if it dispatches elsewhere, you never had a retail job at all. Many customers, facing a hold queue and a longer wait, take the retail price and go on with their evening.

The rule to write down: network pricing requires a network dispatch. No PO, no network rate. Everyone in the shop needs that sentence.

Fitting network work into a real week

Three operating rules keep this channel additive instead of corrosive.

Set a standing capacity rule, not a per-job feeling. Decide in advance: network jobs are accepted when fewer than X trucks are committed, or outside your retail peak window, or within Y miles of a job already on the board. A rule can be applied by whoever is answering. A feeling cannot, and a feeling at 6 PM on a Friday is always wrong.

Make the decline fast and clean. A prompt decline costs you nothing with most networks — what damages standing is silence, and then late arrivals. Declining inside the window is a normal, expected provider behavior. Ghosting is not.

Track network work separately in your books. Not blended into total revenue. Revenue per hour, drive time per job, and completion rate on network work should sit next to the same numbers for retail. Most shops that do this the first time are surprised in one direction or the other, and either way the number changes their capacity rule.

Where AI answering changes the mechanics

The specific thing that fails in this channel is that a dispatcher hits a phone that is busy, driving, or under a dash. Everything downstream — routing priority, offered volume, account health — flows from that one moment.

An AI receptionist changes the mechanics in four concrete ways.

The dispatcher never gets voicemail. Every call is answered live, on the first ring, including the three that arrive in the same two minutes during a storm or a holiday weekend. Concurrency is not a feature here, it is the entire point.

The dispatch call runs its own script. A caller identified as a dispatcher does not get the retail qualification and quoting flow. They get the six-field capture: member or PO number read back and confirmed, precise location, vehicle year/make/model/color, lockout versus key job, ETA, and callback line. Nothing about price, because there is nothing to price.

The job lands in the queue instantly, in writing. The details are attached to a job record and pushed to whoever makes the accept/decline call, rather than living in a tech's short-term memory until he gets out from under the dash. The location arrives as a point for routing, not a sentence to be interpreted.

The decision is made with the retail board visible. This is the part that protects margin. The accept/decline prompt sits next to what is already committed, so the Friday-evening decision is made against real capacity rather than optimism. That is the same discipline as the commercial and property-manager channel, worked through in commercial account calls from property managers, and it depends on the same underlying triage structure described in emergency versus scheduled call triage.

What it does not do is accept jobs on its own. Accept/decline is a business decision with margin consequences and it belongs to a human, with the information already gathered and the clock not yet expired. Shops currently on a traditional answering service will find the operational comparison in the AnswerForce alternative breakdown; the underlying capability set is at AI receptionist for locksmiths and automotive locksmith software.

The bottom line

Motor-club and roadside dispatch work is a genuinely useful channel used correctly and a margin trap used carelessly. It is not a retail call at a discount. The price is contracted, the decision is accept or decline inside a short window, the caller is a dispatcher relaying second-hand information, and what you need from the call is a member number, a location precise enough to find one car in a large lot, a vehicle description, the service type, an honest ETA, and a callback line. The economics work when network jobs fill dead hours and add density near work you already have, and they stop working the moment you send a truck on a contracted rate during your retail rush.

The failure that actually kills these accounts is not price and not quality. It is a dispatcher calling while your tech is under a dash, hanging up rather than leaving a voicemail, and your acceptance rate quietly dropping until the routing order buries you. That is a phone-coverage problem with a business consequence, and it is fixed by answering every call live, running a dispatch-specific capture script, and putting the accept/decline decision in front of a human who can see the retail board at the same time. Keep the rule that network pricing requires a network dispatch, and the retail caller who mentions their coverage stops being a discount you gave away for free.

Frequently asked questions

How is a motor-club dispatch call different from a retail locksmith call?

The price is already fixed by contract, so there is nothing to quote and nothing to negotiate. The caller is a dispatcher relaying second-hand details rather than the vehicle owner on scene, the decision is a simple accept or decline inside a short window, and the information you need is the member or PO number, an exact location, the vehicle description, and the service type. Running a retail qualifying and quoting script at a dispatcher wastes the window and signals that you do not do this work.

Why do locksmith shops lose motor-club accounts without being told?

Because unanswered calls are scored, not just lost. A dispatcher who reaches a busy line or voicemail hangs up and calls the next provider rather than leaving a message, your acceptance rate drops on the network's dashboard, and you get routed lower on future jobs. The account is never cancelled, it simply produces less every month until someone assumes the cause was rates or competition.

Is roadside network work worth taking at lower rates?

It is worth taking when it fills dead time or adds density near work you already have, and it stops being worth taking the moment it displaces retail. The comparison that matters is not the network rate against zero, it is the network rate against the retail job you turned away to run it. Set a written capacity rule in advance, track network revenue per hour separately from retail, and never make the accept decision without the retail board visible.

What information should be captured on a roadside dispatch call?

Six things: the member or PO number read back and confirmed, a location precise enough to identify one vehicle in a large lot, the vehicle year, make, model and color, whether it is a lockout or a key job, the ETA you are committing to, and a callback line for the dispatcher and where permitted the member. The location and the service type are the two that most often go wrong, and both produce the same result, which is a tech on site who cannot complete or cannot find the vehicle.

What should a shop do when a retail caller says they have roadside coverage?

Separate the two transactions and let the customer choose, rather than ignoring the coverage or quietly applying the network rate. Tell them plainly that if they want to use the benefit they should call the number on their card or policy and have it dispatched, and that if they would rather not wait you can be there now at your retail price. The rule to write down is that network pricing requires a network dispatch, because applying a contracted rate with no PO and no network behind it is the worst version of both business models.

How much does TheKeyBot cost for a locksmith shop handling dispatch calls?

TheKeyBot's Core plan is $500 per month with 500 AI minutes and 45 cents per minute overage, Pro is $750 per month with 1,000 minutes at 40 cents overage, and Elite is $1,200 per month with 2,500 minutes at 35 cents overage. Every plan includes bilingual 24/7 answering, quoting from your own price book, calendar booking, GPS-aware dispatch, payment links, and automated review requests, with no per-seat fees. Plan details are at https://www.thekeybot.com/pricing.

Sources

1. Associated Locksmiths of America - professional standards, training, and industry practice guidance for locksmith businesses: https://www.aloa.org/
2. Bureau of Labor Statistics - occupational and industry reference data for locksmiths and related service trades: https://www.bls.gov/
3. Federal Trade Commission - guidance on truthful pricing, advertising, and consumer protection for service providers: https://www.ftc.gov/