There is a version of your company that exists only in two or three heads. It knows which breaker feeds the walk-in cooler at the steakhouse on 82nd, why a particular rooftop unit trips every August when caliche dust cakes the condenser, and which supply house in town actually stocks the odd fan motor. When those heads are on vacation, on a ladder, or gone to a competitor, that version of the company is unreachable.
The questions that interrupt your best people
Listen to the radio traffic or the group text in any service company for a day and most of it is the same event repeating: someone in the field asking someone more experienced a question that has been answered before. Which side of the building the disconnect is on at a certain strip center. Whether a manufacturer honors a warranty claim without the original register receipt. What the property manager at a certain complex requires before she approves an invoice.
Every one of those answers is delivered by phone, once, to one person, and then it evaporates. The senior tech who holds them spends a growing share of each day as a switchboard, and the calls do not stop because he happens to be elbow-deep in a condenser.
This is not an onboarding problem, and this page is not about onboarding. New hires eventually learn where the truck stock lives. The questions that never stop are the judgment ones — the fixes, the exceptions, the customer particulars that accumulate over twenty years and were never written anywhere, because nobody in the history of the trades has had a free afternoon to write them.
Nobody writes documentation. Everybody talks.
Asking a working tech to sit down and type procedures fails every time it is tried. It is the wrong tool for how field knowledge actually lives.
Recording works. The senior tech props a phone against a toolbox and narrates the job he was going to do anyway: here's why I check head pressure before touching the board, here's the bolt that strips if you rush it, here's what this model does when the board is failing versus when it's just a sensor. Twenty minutes of talking — talking he already does when an apprentice rides along — gets transcribed and cleaned into a titled, dated document tied to an equipment model or a customer.
That is the capture method. Not a documentation project; a recording habit. One walkthrough a week becomes fifty documents a year, in the voice of the person who actually knows, at a cost of propping up a phone.
The customer file that helps at 7 a.m.
The other half of the knowledge base is not technical at all. It is the particulars of the people you serve: the gate code on the north entrance, the panel behind the dryer in the laundry room, the dog that has to be inside before anyone opens the side yard, the account that pays at sixty days no matter what the invoice says, the property manager who wants photos before she approves anything.
Right now those details live in old text threads, on a clipboard behind the seat, and in the owner's memory. Put them in a per-customer note that surfaces when anyone searches the address, and the 7 a.m. arrival changes: the tech reads three lines in the driveway and walks up already knowing what the last visit found and which gate actually opens.
Answers that show their work
When someone asks the assistant a question, the answer arrives with its sources attached: the document name, the section, the date it was last touched. "Per the March 2026 walkthrough on the RTU-8 series, check the pressure switch before condemning the board" — with the transcript itself one tap away.
The citation does three jobs. It lets a skeptical tech verify before acting, which is exactly the habit you want in the field. It teaches people where knowledge lives, so the system makes your crew more oriented instead of more dependent. And when an answer turns out wrong, the citation points to the document that needs fixing — the error becomes repairable at its source instead of mysterious.
An answer without a citation trains people to trust a machine on faith. That is the wrong habit to build in anyone who works around voltage, and it is why citations here are the design, not a feature.
Built to say "not found"
A general-purpose chatbot fills silence with plausible guesses, which is disqualifying for this use. An assistant serving your company's documents has to be built with the opposite instinct: when no source answers the question, it says so. The gap is useful information in its own right — it tells you which walkthrough to record next.
The documents themselves stay on infrastructure you control. Customer addresses, gate codes, and billing quirks are not material to hand to a third-party chat service that keeps its own copies.
What it will not do
It cannot capture what nobody records. The first month is deliberate work — recording, transcribing, loading the customer notes — and if that work stalls, what you own is an empty filing cabinet with a very good search bar.
It serves documents; it does not have judgment. A question outside its sources should come back "not found," never as a confident guess, and building it to behave that way is a choice someone has to make on purpose.
Stale documents get served as confidently as fresh ones. Someone has to own review, because when the manufacturer changes a spec, the walkthrough that taught the old fastener pattern becomes a liability with a citation attached.
And some things do not belong in it at all. Gate codes and alarm codes are security-sensitive. Decide who can retrieve what before anything is loaded, and leave out anything a departing employee should not be able to carry off in a search history.
Where to start
Write down the last ten questions your most experienced person answered by phone. That list is your table of contents. Then record one walkthrough this week — a job that was getting done anyway — and you have your first document by Friday.