For IT service desks
The answer you already wrote, found by the next person
Your technicians write the knowledge base every day, one reply at a time. Forward that reply to SecondBrain 365, an AI agent with its own email address inside your Microsoft 365, and it becomes a page — there is no article to write afterwards.
See how SecondBrain 365 supports IT service desks, without asking technicians to write documentation twice.
You do not have a knowledge base problem. You have a writing problem.
Most service desks already have the tool, and it already works: four tickets in ten are closed with an article. What does not happen is the part where somebody turns today's solution into tomorrow's article.
40%
of tickets are already resolved using a knowledge base article — the median across 405 support organisations.
HDI, Knowledge Management in Technical Support
49%
name reluctance to use the knowledge base as an obstacle; 48% say content quality, 47% say it cannot be searched.
HDI, same study
57%
train their people to put content into the knowledge base. Two thirds train them to search it.
HDI, same study
The gap is not knowledge and it is not software. It is the twenty minutes after the ticket closes, which never exist.
The whole workflow
Forward the email. That is the documentation step.
No template, no editor, no “write it up when you have a minute”. The reply you already sent becomes a page the next person finds — and it keeps the link back to the ticket it came from.
Nobody writes a second time
The explanation your technician wrote for one colleague was already the article. It just went to one inbox instead of the knowledge base.
Each page says where it came from
Version numbers, paths and workarounds age badly. A page that carries its ticket and its date can be judged — and “this is from two years ago” is useful information.
And it flags the contradictions
When a new procedure disagrees with one already in the knowledge base, the agent says so instead of quietly stacking a second answer next to the first.
RE: VPN keeps dropping on the new laptops
From: service desk · 14 Sep
Hi Marco — this one is the split tunnelling setting.
On the new ThinkPads the VPN client installs with IPv6 enabled,
and the tunnel drops whenever the laptop changes network.
Disable IPv6 on the VPN adapter and it holds.
If it still drops, the firmware needs the October update.
Pick a record to see where it came from.
One forwarded reply, three entries the next technician will find. Press one to see the line of the email it came from.
Viva Topics could only surface what someone had already written up. Microsoft retired it in 2025 — what is left of it, and what replaces it.
What goes in, what comes out
The sources are the ones your desk already runs on. Nothing new to adopt, and nobody has to leave the tool they answer tickets from.
In
The reply you just sent, forwarded
The support channel, where the tricky ones get solved
Runbooks and procedures you already have
Vendor instructions, migration notes
Out
- How-to pages, in the words that actually worked
- The cause, not just the fix
- Troubleshooting steps with the resolution attached
- A FAQ built from what people really ask
- Alerts when two procedures contradict each other
You decide the structure in the context file: one folder per service, a page per recurring issue, or whatever your desk already calls things.
A concrete case
The procedure that changed in March
Last year — A page explains how to reset the MFA token: contact the service desk, identity check by phone.
March — Security changes the process — self-service through the portal, phone resets no longer allowed. The new instruction goes out in a Teams message.
Right after — The agent had read both, and it flags the pair: the knowledge base still tells people to call, and someone is still doing it. It asks which one holds — it does not silently overwrite a security procedure.
An out-of-date procedure in a technical knowledge base is worse than a missing one: somebody follows it. More on why internal knowledge bases drift, and how to keep one true.
What it changes beyond the queue
The new technician
Reads how your estate actually behaves, not the vendor's documentation for a generic one.
Answers where people already ask
The pages sit in SharePoint, so Copilot can answer from them — including for the colleague who would have opened a ticket.
The expertise stays
The person who knows why that printer queue breaks will not always be here. What they know can be.
FAQ
Questions service desk managers ask
Because the gap is not the knowledge base, it is what reaches it. Four tickets in ten are already closed with an article, and most desks have the tool — but in the same research half the people name reluctance to use it and poor content quality as the obstacles, and fewer are trained to write into it than to search it. This removes the writing step: the reply your technician already sent becomes the page, by forwarding it.
They forward an email. That is the whole change, and it is an action they already perform dozens of times a day. No template, no form, no separate editor, and nothing to learn. They keep answering tickets in whatever tool they answer tickets in.
You can require approval, so nothing appears until someone signs it off — sensible for a desk where a wrong procedure gets executed. Without approval it still never overwrites silently: when a new answer disagrees with one already there, it flags the pair and asks. And the pages are ordinary SharePoint pages you edit by hand.
The support Teams channel works the same way — add the agent and the conversations where the tricky ones get solved reach the knowledge base too. What it does not do is plug into your ticketing tool and read the queue: it sees what your people share with it, which is also why nothing enters that a human did not decide to pass on.
In your own Microsoft 365 tenant: a SharePoint site under the desk's Teams group. Your existing permissions and retention rules apply, because it is not a separate system — which matters more here than elsewhere, since an internal IT knowledge base describes your estate. The detail is on the how it works page.
Need it for something else?
Same agent, same mechanism. What changes is the rules you write in the context file.
Project management
Stop chasing people for updates: the agent asks, and the plan stays current
Product management
Why the product is the way it is — written down while you decide it
HR
The answer your team already wrote, found by the next person who asks
ISO audit
Evidence recorded as it happens, not reconstructed the month before
RFP & bids
The tender's deadlines pulled out of the pack, and the chasing done for you
Onboarding & offboarding
What leaves with a person becomes smaller — and it is honest about the rest