Spaces

Your first week of answering technical messages with an AI agent

This is a first-week checklist for makers of engines, gears and drives who want an AI agent to answer customer messages. It covers the product facts to write down, who to brief and what to check each day.

Runs in your browser. Nothing you enter is sent anywhere or saved.

Before you start

Starting small is the safest way to bring an AI agent into a technical business. In week one you are not aiming for perfection. You are checking that part matching is right, that engineers know a chat may reach them, and that nothing risky is answered by a guess.

Work down the list in order, ideally starting early in the week when the workshop and parts desk are not rushed. Cross items off as you go. If one does not fit how you work, swap it for something that does and keep checking in daily.

Tick each one as you go. 0 of 10 done.

[ ] Write down your product range with ratings exactly as published.
[ ] Build a cross-reference list of old, superseded and competitor codes.
[ ] Gather data sheets, drawings and installation guides in one place.
[ ] Write a short guide for each common request: what to ask and send.
[ ] List your regional distributors and the parts you only sell through them.
[ ] Name the engineer, parts desk contact and service lead for hand-overs.
[ ] Brief the parts desk, sales and workshop teams.
[ ] Test with five real questions using old plate photos.
[ ] Read every chat at the end of days one to three.
[ ] Review the week and fix the two weakest answers.

What a good first week looks like

Most makers find week one is about discovering gaps. A customer asks for a coupling code from 1998, or whether you rebuild a unit, and nobody ever wrote the answer down. That is useful. Add it to the list and carry on.

Keep the agent narrow at first. Let it match parts, send files and take spares requests, and let people handle everything else until you trust the pattern.

Easy mistakes in the first days

Watch for these as you read the early chats.

  • A cross-reference that is close but not exact.
  • A data sheet for the wrong revision of a unit.
  • A lead time that was true last year.

FAQ

How much product data do we need before we begin?

Start with your top fifty parts and units by enquiry, plus the cross-references people ask about most. You can add more each week as the chats show you what is missing.

Should the whole team see the chats from day one?

Yes, at least the parts desk and one engineer. They will spot wrong matches quickly, and they need to know what the customer has already been told when a hand-over arrives.

What if the agent matches the wrong part in week one?

Correct the cross-reference, tell the customer promptly and kindly, and note it for your weekly review. Early errors are how the list gets better, as long as nothing was shipped on a wrong match.

More free tools for engine, gearbox and drive makers

Read the guide: Answer messages for engine, gearbox and drive component makers.