Skip to content

Lithium Marketing field guide

Turn equipment manuals into custom AI search for field techs.

Your techs ask a question on their phone in plain language and get the answer from your own manuals, with the page it came from.

By Kurt Schell Co-Founder, Lithium Marketing Published · Updated
  • How AI manual search works
  • What to load
  • Keeping answers accurate
HVAC technician consulting a tablet beside rooftop equipment

Watch the guide · 03:12

Help field staff find the right manual passage

Help a field technician find the right passage in the right equipment manual. See a sample search and a small test to try first.

Read the video transcript

Your technician is scrolling, not working.

Your technician is on site, scrolling through PDFs while the job waits. They need one piece of information, but first they have to find the right file and section. Let's use an illustrative fictional manual to show how custom search could shorten that hunt without inventing equipment instructions.

You shouldn't need to know the section name

The technician asks, where is the maintenance schedule for Model A? They know the equipment and what they're looking for, but not the section title. A useful search takes that question and looks through the selected documents, rather than requiring someone to guess which PDF to open first.

Model A manual → Maintenance → Schedule

In our fictional example, the result identifies the Model A service manual and its Maintenance, Schedule section. The answer points to that passage with a source reference. That's the visible improvement: a relevant starting point the technician can open, rather than another list of files to work through.

Open the passage instead of trusting a sentence

The technician follows the reference and opens the original passage. Now they can read the actual material in context and see which equipment and edition it applies to. The response helps locate the information; the original document remains available for the instructions the team needs to use.

Find relevant text, then prepare the response

Behind that result, search retrieves material and gives it to a model as context for the response. This is called retrieval-augmented generation, or RAG. It doesn't require retraining on your manuals. The useful idea is answering from a chosen collection, with a way back to the source.

A similar model isn't the same equipment

Here's a mistake worth catching: the answer points to Model B, or the wrong edition, because the wording looks similar. A convincing reference isn't enough. Checking the document identity and the actual passage keeps the search result tied to the equipment the technician is working with on site.

Search can't read information it doesn't have

The collection determines what search can find. Scanned pages may need conversion, and the right manuals and bulletins need to be available with clear versions. Start with equipment the team handles often. That focuses preparation on questions that interrupt work, rather than digitizing every file at once.

Show the gap instead of inventing guidance

If someone asks about Model C and its manual isn't in the collection, the proposed system should expose that missing source. The technician can take the unresolved question to staff who can help. That exception also shows which document would make the collection more useful for future searches.

Can someone reach the useful passage sooner?

Try familiar questions on the devices your team actually uses. Compare the path to the useful passage with today's PDF search, including the time spent opening and checking the source. A fast answer that leaves the technician unable to read the document hasn't solved the on-site problem.

Which question sends staff searching again?

Ask technicians which information they struggle to locate, then start with those manuals and questions. Lithium scopes custom document processing, AI search workflows and integrations after a free discovery call. The aim is a route to source information on the job, with less time spent hunting through files.

Talk with Lithium

Let's talk about your document search. Visit Lithium S E O dot com and tell us about your business.

What it is

A search box that knows your manuals.

You turn equipment manuals into custom AI search by converting your manuals, service bulletins and wiring diagrams into searchable text, loading them into a private search system and letting techs ask questions in plain language from a phone or tablet. The system finds the right pages and the AI writes a short answer from them, with a link to the source page.

Think about how your techs find information today. They scroll a 120-page PDF on a phone screen. They dig through a binder in the truck that may or may not have the right revision. They search the manufacturer’s site from a rooftop. Or they call the office, or the one senior tech who knows that unit, and wait for a callback while the customer watches.

A custom search system cuts that to a question and an answer. The tech types or says what they need, reads the answer and taps through to the page in the manual to confirm. It’s a better way to look things up, built on the documents you already own.

What techs ask

The questions it answers best.

Manual search works best on questions that have one right answer sitting somewhere in a document. These are illustrative examples of the kind of thing techs ask:

  • What does a flashing error code mean on this model?
  • What is the gas valve outlet pressure spec?
  • What is the torque spec for this fitting?
  • Which replacement part number fits this serial range?
  • What is the startup sequence after a board swap?
  • What does the latest service bulletin say about this issue?
  • Where is the reset switch on this unit?
  • What does our own install checklist require here?

It is weaker on questions that need judgment on site: why a system keeps short-cycling when the specs all check out, or whether a repair is worth doing on a twenty-year-old unit. The manual can inform those calls, but your tech still makes them.

How it works

Search first, then answer.

The method behind manual search is called retrieval-augmented generation, or RAG. Instead of relying on what an AI model learned in general, the system searches your documents for the pages that match the question and hands those pages to the model, which writes its answer from them. You don’t retrain the model on your manuals, so adding a new manual is as easy as adding a file. Read AWS’s RAG explanation

  1. 1

    Collect

    Gather the manuals, bulletins and diagrams for the equipment you service most.

  2. 2

    Convert

    Turn PDFs and scans into clean text, with text recognition for scanned pages.

  3. 3

    Index

    Split documents into sections and tag each with brand, model and revision.

  4. 4

    Ask

    A tech asks a question in plain words from a phone or tablet.

  5. 5

    Find

    The system pulls the sections that best match the question and the model.

  6. 6

    Answer

    The AI writes a short answer from those sections and links the source page.

What to load

Start with the documents techs reach for most.

Don’t upload every file you own on day one. Ask your techs which equipment they service most and which documents they hunt for, and start there. A smaller, clean collection gives better answers than a big, messy one.

Installation and service manuals

The core collection, for the brands and models you install and repair most.

Service bulletins

Manufacturer updates that change a procedure or flag a known fault.

Wiring diagrams and parts lists

Linked as images where text conversion would lose the detail.

Your own procedures

Install checklists, startup steps and company rules your techs follow.

Warranty terms

What is covered, for how long, and what voids it.

Fixes your team has found

Notes from senior techs on problems the manual doesn’t cover well.

Keep revisions straight. Manufacturers update manuals, and two versions of the same document can disagree. Tag each file with its revision, retire the old version when a new one arrives, and decide who on your team owns the collection.

The hard parts

Where manual search gets tricky.

1

Scanned and faded pages

Text recognition handles clean scans well. Faded copies, handwriting and stamps need a person to check the converted text.

2

Tables and diagrams

Spec tables can scramble during conversion, and diagrams don’t turn into text at all. Both need special handling, often linking the original page image.

3

Similar models

Two furnaces from one brand can share most of a manual and differ on one critical spec. Tagging by model and serial range keeps answers on the right unit.

4

Spotty signal

Basements, crawlspaces and rural sites lose connection. Plan for it before rollout, not after the first complaint.

Keep it accurate

Every answer shows its source.

The rule that makes manual search safe is simple: every answer links the manual and page it came from. If the system can’t find an answer in your documents, it says so and doesn’t guess. Techs learn to read the answer, tap the source and confirm, the same way they’d check a spec with a coworker.

Be strict on safety-critical work. Gas pressures, electrical clearances, refrigerant handling and anything covered by code should always be confirmed against the manual page itself, not only the summary. The search tool finds the page faster; it doesn’t replace reading it.

Log the questions the system couldn’t answer. That list tells you which documents are missing, which ones converted badly and what your techs need to know that no manual covers. It’s often the most telling report the system produces.

Before rolling out to the whole team, run a pilot. Pick one equipment line, have your senior techs write twenty or thirty real questions they already know the answers to, and check each answer and its source. Fix what comes back wrong, then hand it to a few techs in the field for two weeks and ask them what they’d change.

What it costs

How Lithium builds it.

Lithium builds manual search systems as custom AI systems . Each one is scoped after a free discovery call and quoted before the build starts; most custom builds take one to two weeks. The price depends on how many documents you have, what shape they’re in, who needs access and where your techs will use it.

Bring a sample of your manuals, a list of questions your techs ask every week and a sense of which devices they carry. The discovery call covers whether manual search is the right fit or whether a simpler fix, like a cleaned-up shared folder, gets you most of the way.

Manual search pairs well with other field workflows. Techs who look up a spec on site can also turn their job notes into paperwork; see how voice notes become estimates and invoices . For terms like RAG and text recognition, the marketing glossary has short definitions.

FAQ

Questions about AI manual search.

DJ Van Zanten

Still curious?

Call (503) 766-5964 or email [email protected].

Does the AI make up answers that aren’t in the manual?

A well-built system is set up to answer only from your documents and to say so when it can’t find an answer. Every answer shows the manual and page it came from, so the tech can check the source before acting on it.

Can it read scanned PDFs and old paper manuals?

Yes, after conversion. Scanned pages go through text recognition first. Clean scans convert well; faded copies, handwriting and complex wiring diagrams need checking, and some diagrams are better linked as images than converted to text.

Will it work in a basement with no signal?

Most systems need a connection, because the search runs on a server. If your techs often work without signal, raise it on the discovery call; options include saving key documents to the device or searching before heading into the crawlspace.

Do we need to retrain an AI model on our manuals?

No. The system searches your documents and hands the relevant pages to the AI with each question. Adding or replacing a manual means updating the document collection, not retraining anything.

How much does a custom manual search system cost?

It is scoped after a free discovery call and quoted before the build, based on how many documents you have, what shape they are in and where techs need to use it. Most custom builds take one to two weeks.

Free action plan

Which manuals do your techs dig through most?

Let’s have a real conversation about your business. No fluff, no high-pressure sales pitch. In a 1:1 strategy call, we’ll review your goals, your website, and your current marketing efforts. You’ll leave with a prioritized plan outlining quick wins and a clear path toward long-term, sustainable growth.

What we’ll cover

  • What’s working (and what isn’t) in your current marketing
  • Site and funnel gaps that are costing you leads
  • Local SEO and paid traffic opportunities
  • Simple tracking and KPIs to measure success

Get my free action plan

Tell us a little about your business. Response within 24 hours.

  • 100% free, no obligation
  • Custom plan for your business
  • Response within 24 hours
Call now Free action plan