When an IT team wrote to us, the problem was not outages but IT how-to questions. Their team was three people with a queue of tickets, and most of the tickets were the same handful of requests: how do I connect to the office Wi-Fi, how do I set up the VPN on a new laptop, why does the printer on level three keep asking for a code. Each took two minutes. Together they took the morning, and the work that needed an engineer waited.
What they told us
Every one of those questions already had a written answer, in a wiki or a setup guide. Nobody could find the right page at the moment they needed it, so they opened a ticket, sent a chat, or walked over to a desk. For the person asking, the question was urgent: they could not work until it was answered. For the team, it was the same instructions recited again.
They asked whether their own guides could answer for them, with no assistant improvising technical advice the team had never written.
How we approached it
IT instructions are unforgiving. A step out of order, or a setting that belongs to a different operating system, costs someone an afternoon. So we worked through what an internal assistant must and must not do before anything else:
- It answers from the team's own guides, step by step, using the instructions the team wrote.
- When the guides do not cover a problem, it says so rather than guessing a fix.
- A problem it cannot solve reaches the team with the conversation attached, so nobody is asked to start again.
- The team can see which guide an answer came from before staff rely on it.
How it works
The team uploads the setup documents and FAQs it already maintains to a knowledge base. Staff ask in their own words — "VPN on Mac", "printer code level three", "new phone email" — and the assistant answers from those instructions.
It stays inside your guides. A question beyond them gets an honest "I don't have that information", not an invented procedure.
It hands over with the history. When a person is needed, the conversation can go to the team through a connected help desk, with what has already been said attached.
You can check it first. The test page and its debug view show which guide each answer came from. A wrong answer usually means a guide is out of date, and updating the guide updates the answer.
Where it leaves the team
Tickets still arrive. The routine ones are answered in seconds, including in the evening when the team has gone home, and what reaches the queue is the work that needs an engineer. The assistant is not an engineer and does not try to be one. It gives staff faster access to what the engineers already wrote down.
Frequently asked questions
Can a chatbot answer IT how-to questions from our internal guides?
Yes. Upload your setup guides and FAQs to a knowledge base, and the assistant answers staff questions from them in plain words.
What happens when the assistant cannot solve the problem?
It says it does not have that information, and the conversation can be handed to your team through your help desk integration with the history attached.
How do we check the answers before staff rely on them?
Use the test page and its debug view, which shows which document each answer came from.