Locksmith Technician Account: The Tech Closes the Job, Takes a Signature, and Never Sees Your Margin
A technician account in JobBase is a separate field-tech subaccount in the Dispatching section: the tech closes the job on-site, builds an itemized invoice from your service catalog, and takes a mandatory client signature before the job can close. He sees client prices and his own cut; your profit, the company's share, and the net margin never appear on his screen. That closes two common leaks at once: bills lowered out of kindness, and chargebacks lost to unsigned receipts. What's left for you is reviewing finished work instead of doing it yourself.
01Cashier, lawyer, dispatcher: sound familiar?
Three or four techs in the field, trucks rolling, clients happy, and the phone is still yours. A tech calls from a driveway to ask what to charge for extracting a broken key from a door lock. A harder pattern costs more: a good tech sometimes can't bring himself to quote the full catalog price to a person standing in a doorway, and quietly names a lower number out of kindness. A call you paid a lead, gas, and his rate for closes on a ticket that leaves you almost nothing. And if the receipt was a scribble or nothing at all, a chargeback two weeks later finds you with no signature, no list of work, and no note that the price was agreed beforehand: the bank defaults to the cardholder, and you eat the loss. None of it is about the tech's character; the price, the signature, and the close all happen where you aren't, and nothing gets recorded.
02What is a technician account?
A technician account is a separate subaccount for your field specialist inside your dashboard, under Dispatching. You create it yourself; the login and password stay in your hands, the same as with a dispatcher account, so access stays with you if he leaves.
The tech closes his own job on-site: he opens it on his phone, builds an itemized invoice from your service catalog with each line priced from your list, hands the phone to the client to review and sign, and the job flips to "completed." The signature is mandatory; without it the job won't close. What used to be your evening ritual of entering amounts and reconciling now takes him a minute at the truck, and it reaches you already filled out and signed, so you go from entering every job to just checking finished ones. You set the catalog once; from then on he only picks line items, and the price comes from your list rather than his read of the client.
03How a signed invoice protects you from chargebacks
A signed itemized invoice with disclaimers is your main document in a bank dispute. The client signs two blocks. The ownership block records that he has the right to authorize the work, that it's his car, his home, his lock, and that the price was disclosed and agreed before work started. The liability waiver block has him accept the ordinary risks of the work, with one line in bold: paying confirms the service was satisfactory and waives claims about functionality, pricing, or damages.
He signs this on the screen before paying. When a dispute lands, you're not walking into the bank empty-handed: you have a signed list of work, an agreed price, and his name under a statement that it's done and accepted. In our experience, a document like that heads off the large majority of claims and chargebacks before they go anywhere, since people think twice before disputing something they signed. It's not a legal guarantee and no tool gives one-hundred-percent protection, but the gap between a nod-and-pay and a signed, itemized agreement is usually what decides the outcome.
04What the tech can (and can't) see
The visibility line is drawn exactly where you need it. The tech sees the client price of each service; he couldn't build the invoice otherwise. He also sees his own cut on the job, which is fair, since he should know what he earns. Beyond that: company profit, the owner's share, and net margin never appear on any of his screens. He knows what he gets, not what the job left for you.
| Area | Sees | Doesn't see |
|---|---|---|
| Invoice | client prices from the catalog | your margin and the item's cost basis |
| Earnings | his cut on the job | company profit, the owner's share, net margin |
| Client | contact details for the current job | phone and address after the PII window |
He needs the client's phone and address to get there and do the work, so those stay visible on a fresh job. After a number of days you set, that contact info gets masked by a PII window, so he can't scroll an archive of your clients and walk off with a calling list if he's fired. He gets exactly what he needs to work honestly on-site: the price and his own pay, and nothing that shows him how the business itself makes money.
05Why the average ticket moves toward fair
An official invoice removes the tech's need to name a price out loud, and that alone is why tickets stop getting lowered. Across our own crew in the US and Canada, the pattern repeats: a tech closing on catalog prices pulls the average ticket up toward a fair level. We won't promise a percentage; try it on your own crew instead.
Naming a high number face to face and haggling on a doorstep is uncomfortable; opening a catalog and pointing at a line item isn't. The price becomes a fact from a list rather than a number the tech has to defend, so there's nothing left to negotiate. This helps new hires most, and anyone with a soft spot for a hard-luck story at the door: instead of spending weeks learning to "hold the price" and losing you money on every other call, they just show the number.
This only works if the catalog itself is priced fairly. It's a tool for confident presentation, not for padding the bill; an inflated catalog price comes back as disputes and lost clients.
06Owner control and the dispatcher link
Letting the tech close jobs doesn't mean losing visibility. Every job is tagged with who created it, so with several techs on staff you can tell at a glance whose call it was. Lead sources that need your review land in one queue instead of getting buried in the general feed, and a new tech is productive from day one: no week of shadowing you to learn how jobs get entered.
The technician account is half the setup. The other half is the dispatcher account: whoever answers the phone can quote a client a price from your catalog and assign the job to a tech, but can't reopen a saved order to see its total, see anyone's margin, or see what an ad channel actually returns; that route is blocked outright, not just hidden from a menu. In his own numbers, a dispatcher sees only his own volume and rate, nothing company-wide, and you choose which lead sources, partners, and techs are even visible to him. The tech closes what the dispatcher assigned, and you review the finished result; how the two roles add up to a shop that runs without you on the phone or on the calls, we cover in a separate guide: the dispatch team in JobBase.
We built this running our own crew of locksmiths, and needed it ourselves before selling it to anyone else.
07FAQ
Can my technician see my profit or margin?
How do the signature and disclaimers actually help with a chargeback?
Can the tech close a job without a signature?
Won't the tech end up with my client list?
Tired of being the cashier and the lawyer on every single call?
Set up technician accounts in Dispatching and let the close go where it belongs: to the client, on site. The tech builds an official invoice, takes a signature under the disclaimers, and closes the job himself, while never seeing your margin. You can see how it works in the demo, no sign-up required.