Service Guide · Version 3.2
2.1 · Receiving a request
“For every service request concerning product line A, record the serial number, the exact product variant and a short description of the fault.”
AI search for internal documents
A customer asks a question. The product details are in a wiki, the instructions are in a PDF, and the service team has its own notes. Which source has the answer?
I build AI assistants that search the documents each person is allowed to read. Staff get an answer with a link to the passage behind it, so they can check it for themselves.
Ask a few colleagues what they looked up this week. Their questions are a good starting point.
I use those questions to choose the sources, design the answers, and decide how to test them.
With retrieval-augmented generation (RAG), the application looks up relevant passages and gives them to a language model as the basis for its answer.
I prepare and index the documents, check which ones each user can access, and test whether the cited passage actually answers the question.
Your team can ask questions in a standalone assistant or inside the application they already use.
Integrate a knowledge assistant into a Java applicationA service rep asks two questions. The first answer draws on two approved documents. For the second question, the service team needs a different source. Follow each citation to check what it supports.
Sample questions
Record the serial number, the exact product variant and a short description of the fault. Service guide, Section 2.1
For variant A2, also record the error code on the device. If there isn’t one, say so in the ticket. Variant sheet A2, Section 1.3
Neither approved document specifies a replacement deadline. To give the customer a date, the team needs the service agreement that applies to this order.
Fictional documents · Available to customer service
Service Guide · Version 3.2
“For every service request concerning product line A, record the serial number, the exact product variant and a short description of the fault.”
Variant sheet A2 · Version 1.1
“For variant A2, also record the error code shown on the device. If no code is displayed, record that in the service case.”
If a detail affects the answer, the assistant can ask for it. Here, the exact product variant determines whether the team needs an error code.
The application searches the service documents and product information the user is authorized to read.
You decide which document versions count as authoritative for each question.
Staff see an answer tailored to their question, with the documents and sections used so they can check the original wording.
Depending on the source, the answer can also show the document version or when it was last updated.
I work with your team to decide what the assistant should do when the documents don’t support an answer. The assistant might ask a follow-up question, show a relevant passage or hand the case to the right person.
I test what the assistant does in those cases, too.
A knowledge system can use product documentation, internal instructions, approved knowledge articles and selected records from business applications.
Three decisions shape a pilot: which documents are authoritative and who maintains them, who may read them, and which real questions the answers need to stand up to. Start with one team and the sources it uses for a specific job.
A few decisions matter early on.
That gives the people who maintain the documents a way to keep the assistant current.
An internal assistant must respect what each person is allowed to read.
The application checks access before it retrieves a passage or includes it in an answer. Each group can search only the sources it has permission to read.
For each integration I check whether permissions can be inherited from the wiki, document management system or other source. Role changes and revoked access are part of the update process.
More about APIs and system integrationI check whether the assistant finds the information it needs and whether that information supports its answer.
I collect questions from your team, write down what a good answer would contain, and test the assistant against them.
I check the answer and its citations together. A link is useful only if the passage supports what the assistant says.
You can run the same questions again after changing the documents, the search, or the model.
Microsoft Learn on evaluating retrieval and answer quality in RAG
A first release works best when it’s clear who will use it, what they’ll ask, and which documents they trust.
For example, the service team could start with the approved documents for one product group. Together we choose the questions the assistant should answer and how to evaluate its responses.
The first release includes
Once people have tried it, you can decide which documents to add or which team to bring in next.
Plan a pilot with your documentsThe amount of work depends on the source systems, document formats, access rules, and the standard the answers need to meet.
To estimate operating costs, I consider the volume of content, how often it changes, expected usage and the services involved.
I can measure response times, answer quality, and processing costs on real tasks in the first release. I’ll also help you identify who will keep the content up to date and who will provide technical support.
Before I start building, I check your rules for data storage, transfers, and the services allowed to process it.
Plan architecture and operations togetherI’m Marcus Biel, a software architect and developer. I’ve been building software with Java since 2001.
I’ll work with the people who answer these questions today, design the assistant, and help write the code. I can join your developers or bring in specialists when needed.
Together we’ll decide where staff should be able to ask a question and how they’ll get back to the original document.
More about working with Marcus
Send me a couple of typical questions, who asks them, and where people look for the answers today.
We can use those examples to pick a useful starting point for a pilot.
Prefer to talk first? Call +49 171 1151013 or message me on LinkedIn.