In short

Customers ask the same product questions every day: will this fit, does it work with that, what does this setting do. The answers are usually in a manual, a specification sheet or an old email, but finding them takes time. The improved process searches your own documentation, drafts an answer with the source attached, and leaves a person to check it before it goes out.

Answers come only from your own approved documents. If the documents don't cover the question, the system says so instead of guessing.

  • Sector Product businesses
  • Role Customer service team
  • Job Answering product and technical questions

The job today

A customer emails or uses the website form with a question. Whoever picks it up searches the shared drive for the right manual, asks a colleague who knows the product, or answers from memory. Technical questions wait for the one person who knows the range best, and the same questions are answered again next week.

Where it breaks

  • Answers depend on who picks up the question and what they remember.
  • Manuals and spec sheets are spread across folders, and old versions are still in use.
  • Technical questions queue for one expert.
  • A wrong answer about fit or compatibility leads to returns and complaints.

The improved process, step by step

  1. Gather the approved documentsCurrent manuals, specification sheets and approved answers are collected into one library, with old versions marked as replaced.
  2. Read the question AI preparesThe system reads the customer's question and works out which product and which kind of question it is.
  3. Find the answer in your documents AI preparesIt searches only your approved library for the passages that answer the question, and records exactly where each one came from.
  4. Draft a sourced reply AI preparesAn assistant drafts a short reply in your tone with the source document named. If nothing in the library answers it, the draft says the question needs an expert.
  5. A person approves the reply A person approvesA member of the team checks the draft against the source, edits it and approves it. Nothing is sent without that approval.
  6. Fill the gapsQuestions the library couldn't answer are listed each week, so an expert can write an approved answer once and add it to the library.
Answering product questions from your own documentation: process diagramSteps: 1. Gather the approved documents; 2. Read the question (AI prepares); 3. Find the answer in your documents (AI prepares); 4. Draft a sourced reply (AI prepares); 5. A person approves the reply (a person approves); 6. Fill the gaps 01 Gather the approved documents 02 AI PREPARES Read the question 03 AI PREPARES Find the answer in your documents 04 AI PREPARES Draft a sourced reply 05 A PERSON APPROVES A person approves the reply 06 Fill the gaps
The process at a glance. Teal steps are prepared with AI help; the amber step is where a person approves.

Where a person must approve

A person approves

Every reply is checked and approved by a person before it is sent. Anything that sends, changes or cannot be undone waits for that approval.

Questions about safety, warranties or anything legal are always answered by a named person, not drafted.

The data boundary

  • The system searches only your approved documents. It does not use the open web to answer product questions.
  • It can read the question and the customer's order where needed. It cannot change orders, issue returns or make promises about stock or delivery.
  • Every answer shows the document it came from, so it can be checked.
  • Drafts, edits and sends are logged.

Checklist before you start

  • We have current manuals and specification sheets in a form we can share with the system.
  • We know which documents are out of date.
  • We know which questions must always go to an expert.
  • We know where product questions arrive today.
  • Someone owns keeping the library up to date.
  • We have a named person to approve replies, with cover.

This is an illustrative walkthrough of a common pattern. It is not a client case study, and the details will differ in your organisation.