Skip to content

AI service manual assistant for dealers and technicians

An AI assistant could find model-specific procedures in service manuals and bulletins, cite the source page and link parts for dealer review.

Use case: an example of what we build, not a client project

E-commerce4 min read

Technician reading a tablet at his workbench in a busy workshop
Industry
E-commerce
Platforms
Web dealer portal, Android, iOS
  1. The challenge

    An equipment maker's knowledge sits in service manuals, service bulletins and parts lists that differ by model, serial range and year. Dealer technicians in the field call the factory help desk for answers that are already written down, and order the wrong part when the parts list for their serial range is hard to find.

  2. What we would build

    We would index your manuals, bulletins and parts lists with the model and serial range attached to every passage, and give dealers an assistant inside the dealer portal. It answers with the procedure and the page cited, puts newer bulletins ahead of older manual text, and links each part number to ordering.

  3. What it would change

    Your dealer technicians could find the right procedure and part for the exact machine in front of them, your help desk would see fewer repeat calls, and the questions it does get would arrive with the context already attached. This is an example of what we build, not a delivered project.

What the system would do.

The parts of the system and the job each one would do for your team.

  • Answers for this exact machine

    The technician enters the model and serial number, and every answer comes only from documents that apply to that serial range.

  • Bulletins before old text

    When a service bulletin changes a procedure, the assistant shows the bulletin first and marks the manual text it replaces.

  • Page and figure cited

    Each step names the manual or bulletin, the page and the figure, and opens the original diagram in one tap.

  • Part numbers linked to ordering

    Parts named in an answer link to your dealer parts portal with live stock and dealer price from your ERP.

  • Access by dealer tier

    Authorized service dealers see warranty and repair procedures; sales-only dealers see operator-level content.

  • Escalation with context

    If the documents don't solve it, the technician raises a case that reaches factory support with the machine details and the passages already tried.

Built with

The tools behind it, layer by layer.

  1. Database

    • Vector database (model filters)
  2. AI

    • Embedding model
    • LLM API
  3. Integrations

    • Parser for manuals and parts tables
    • Dealer single sign-on
    • Parts catalog and ERP connector

The use case in full

The problem

An AI assistant for service manuals addresses a problem every equipment maker with a dealer network knows. A technician is at a customer's site with a machine that will not start. The fix is documented somewhere: in the service manual for that model, in a bulletin issued last spring, or in the parts list for that serial range.

Finding it is the hard part. Manuals run to hundreds of pages, bulletins pile up in a separate folder, and parts lists change between production runs. So the technician calls your help desk, and your engineers answer the same questions they answered last week.

Wrong parts are the other cost. Order a part from the parts list for the wrong serial range and the machine stays down until the right one arrives.

What we would build: an AI assistant for service manuals in your dealer portal

We would add an assistant to your dealer portal that answers only from your technical documents. It relies on retrieval-augmented generation, or RAG:

  • Split. Manuals, bulletins and parts lists are broken into passages. Each keeps its document, page, figure, model and serial range.

  • Index. The passages go into a search index that matches by meaning, so "engine cranks but won't fire" finds the no-start troubleshooting table.

  • Search, then answer. For each question, the system retrieves passages for that machine only. A language model then writes the steps from those passages and cites where each one came from.

If the documents do not cover the question, the assistant says so plainly and offers to open a support case.

How it works

The technician signs in to the dealer portal on a phone or tablet and enters the model and serial number, or scans the plate. Then they describe the fault in their own words.

The assistant replies with the likely checks and the repair steps, each citing its manual page or bulletin number.

If a bulletin has changed a step, the bulletin comes first and the old text is marked as replaced. Every part named in the answer shows its part number for that serial range, linked to the parts portal with stock and dealer price.

When the fault is not covered, the technician raises a case from the same screen. Factory support receives the machine details, the question and the passages already tried. Their answer can then feed a new bulletin, and the next technician finds it.

What the AI does, and what your team decides

The AI matches a described fault to the right passages, puts bulletins and manual text in the right order, writes cited steps and pulls the correct part numbers. It also groups unanswered questions by model.

Your people stay in charge. Technical publications decide which documents go in and when. Support engineers own every answer the documents cannot give. Dealers decide whether a repair goes ahead and what the end customer is charged. Warranty claims follow your existing approval process.

What the research says

  • Finding answers costs real time. A survey of 12,000 knowledge workers and 200 executives by software maker Atlassian found that leaders and teams lose 25% of their time just searching for answers (Atlassian, State of Teams 2025). A technician hunting through manuals and bulletins on site pays the same tax, so the assistant brings the right passage to them.

  • Retrieval makes answers more specific. The 2020 paper that introduced retrieval-augmented generation found RAG models produced more specific, diverse and factual language than a model answering from its training alone. It also named giving provenance for answers as an open problem (Lewis et al., NeurIPS 2020).

  • Grounding still needs checking. A preregistered 2024 evaluation of commercial RAG-based legal research tools found each still hallucinated between 17% and 33% of the time (Magesh et al.). In repair work, that means every step should show its source page.

Guardrails

  • Data access. Dealer tier, region and role decide which documents a person can search. Search results respect the same rules as the document library.

  • Human approval. Safety warnings are quoted exactly from the manual. Warranty work, field fixes outside the documents and part substitutions need approval from your support team.

  • Logging. Each question, the machine, the passages used and the answer are logged, which helps with warranty reviews and shows where documents need work.

  • Versioning. When a manual or bulletin is reissued, the old passages leave the index the same day.

Is this right for you?

  1. Are your manuals and bulletins digital, and is each tied to models and serial ranges?

  2. How many help desk calls are questions the documents already answer?

  3. Do dealers already order parts online, and could answers link to it?

  4. Which procedures should only authorized service dealers see?

How does the assistant stay inside your manuals? Our explainer on retrieval-augmented generation walks through it. For the build, see our AI agent development and custom software development pages, or explore our ecommerce and B2B commerce work.

Common questions

How does an AI assistant for service manuals work?

It uses retrieval-augmented generation. Your manuals, service bulletins and parts lists are split into passages, each tagged with model and serial range, and indexed. A question first retrieves the closest passages for that machine; a language model then writes the answer from those passages only and cites the page.

What if a service bulletin changes a procedure in the manual?

Bulletins carry their issue date and the models they cover. When one applies, the assistant shows it ahead of the older manual text and notes what it replaces, so a technician does not follow a superseded step.

Can it read exploded diagrams and parts tables?

It indexes the text, captions and part tables around each diagram and links back to the original page image, so the technician always sees the real drawing. We would test this on your hardest manuals before rollout.

Can dealers order parts from the answer?

Yes, if you want it. Part numbers in an answer can link to your existing dealer parts portal, showing stock and dealer price from your ERP. Ordering still goes through the portal's normal checkout and approval.

Does this replace factory technical support?

No. It handles questions the documents already answer and hands the rest to your support engineers with the machine details and the passages tried, so they start further along.

More AI use cases.

Other examples of what we build. None of them is a client project.

See all AI use cases

Free project estimate

Talk through a project like these.

Thirty minutes with a founder, not a salesperson. Bring the problem; leave knowing what we'd build first and what it would cost.

What you get back

  • An indicative budget range
  • A realistic timeline
  • What moves the cost up or down
  • A reply within 4 business hours
  • Answered by a founder
  • NDA on request, before you share details

Tell us what you need

A few lines is plenty. You get a number before any call.

Fields marked * are required.