Dispatching a small locksmith team: getting jobs out of one person's head
A one-van locksmith does not dispatch. The phone rings, you look at your day, you go. The trouble starts with the second technician. Now someone has to know where two people are, what each can do, which van has the right parts, and what the customer was promised. In most growing shops that someone is the owner, the system is the owner's head, and it stops working the day the owner is under a dashboard with a phone ringing in a pocket.
This guide describes a dispatch setup for shops with two to five technicians. It is about roles and rules first. Software comes last, because software only speeds up a process you already have.
Who takes the call?
Decide this before anything else, and write it down. There are three workable answers:
| Setup | Works when | Breaks when |
|---|---|---|
| Owner takes every call | Two technicians, owner mostly at the shop | The owner is on a job. Calls go to voicemail, and an emergency customer calls the next number |
| One technician is "on phones" each day, by rota | Three or more, no office person | The on-phones technician is given complex jobs anyway |
| A dispatcher at the shop or at home | Four or more, or a busy counter | Nobody covers lunch, evenings and sick days |
Whichever you choose, the rule is the same: at any moment, exactly one named person owns the phone. Two people half-owning it is how calls get lost.
What must be captured on every call?
An emergency customer will not repeat themselves, and the technician who gets the job should not have to call back to ask basics. Capture the same six things every time:
- Name and a phone number that the customer will answer.
- Exact location, with a landmark. "The car park behind the pharmacy" beats a street name.
- The vehicle: make, model, year, and the number plate if they can read it.
- The problem in the customer's words: all keys lost, key locked inside, remote dead, key broken in the lock.
- What was quoted, or the range, and whether the call-out fee was stated.
- The promised time window.
Points 5 and 6 are the ones that cause arguments at the car. If the person on the phone quotes and the technician never sees the quote, the customer ends up with two prices. The quote has to travel with the job.
How should jobs be assigned?
Pick by rule, not by habit. A sensible order of questions:
- Who can do it? Not every technician programs every system. Keep a short list of who is cleared for which job types.
- Whose van has the parts? This is the question shops skip, and it produces the wasted trip. It needs stock you can trust.
- Who is closest, in time, not in distance? A technician ten minutes away but forty minutes from finishing is further than one twenty-five minutes away and free.
- Whose day is lighter? Use this only as the tie-breaker. Fairness matters, but not more than the customer's wait.
Then tell the technician in one place, the same place every time. A job that arrives half by phone call, half by chat message, with the address in a third place, will go wrong sooner or later.
What should the customer be told?
A locked-out customer measures you by one thing: whether you arrive when you said. So say less, and keep it:
- Give a window you can keep, not the one they want to hear. "Between 40 and 60 minutes" kept is better than "20 minutes" missed.
- Tell them who is coming. A first name and a van description removes most of the anxiety, and it separates you from the anonymous operators behind fake listings.
- If the time slips, tell them before they call you. One message saves the job; silence loses it.
An arrival link helps here: the customer can check the job status and the arrival time without calling the office.
What should you measure?
Four numbers, reviewed once a month, are enough for a small team:
| Number | What it tells you |
|---|---|
| Time from call to arrival | Whether your promised windows are honest |
| Jobs per technician per day | Whether work is spread sensibly |
| Second visits | Wrong part, wrong technician or wrong diagnosis on the phone |
| Quoted price versus charged price | Whether phone quotes and roadside reality match |
Second visits are the expensive one. Each one costs a trip, a slot and some of the customer's trust, and most of them trace back to a question that was not asked on the call.
Where does software help?
Once the roles and rules exist, software removes the retyping and the guessing. In Nyrano the setup above looks like this:
- The person on the phone creates the job with the customer, vehicle, problem and quote in one record, so the quote travels with the job.
- The dispatch board shows every open job by status, which technicians are free, and where each van is. A job can be assigned or reassigned at any time from the office.
- The dispatcher sees each van on the map while its technician is on shift. The technician sees the job in the Android app and taps "Head out", and the customer can be sent a link with the job status and the arrival time.
- Parts on the job come off stock when the job starts, so the stock count is one you can trust. With vans set up, they come off the van of the technician doing the job, so "whose van has the parts?" has an answer on the screen.
- The owner decides what each role sees. A technician works their own jobs without seeing revenue or costs.
One honest limit: the phone app runs on Android only for now, so a dispatcher with an iPhone uses the web app in a browser. Your van kit list still decides what each van should carry.
If you are at the two-van stage and the system is still your own head, start with the first two sections of this guide this week. They cost nothing, and they are the part that software cannot do for you.