.svg)
What an AI wiki is
An AI wiki is a company wiki that answers questions. Employees ask in their own words about a policy, a process or who looks after what, and an assistant replies from your pages and links the ones it used. Every page has a named owner behind it.
Your wiki, seen by someone who uses it every day
Picture Juniper Lane, a furniture retailer with 30 stores and about 450 people. Its handbook, store procedures, team pages and a directory of who owns what all live in one wiki. Amara has just started as manager of the Bristol store.
Monday, 7:45 am: a home page made for her
Amara signs in with her work account. Her wiki home shows the new starter checklist for store managers, the two procedures that changed this month for stores, and the regional team she reports to. She knows where to start before the doors open.
Monday, 11:20 am: the refund rule, in four lines
A customer wants a refund on a sofa delivered with a torn seam. Amara asks the wiki what to do with damaged deliveries over £500. The reply comes from the returns procedure: what she can approve herself, what needs her regional manager, and the form to use. The page is linked, and the customer has an answer in minutes.
Tuesday, 2:10 pm: sorted without a single email
Her store is short of dining chairs and Bristol's sister store has spares. The stock transfer page walks her through it and has the request form built in. She submits it, gets an instant confirmation, and logistics approves it.
Wednesday, 4:30 pm: a question no page covers
A customer asks to return a made-to-order table after six weeks. The wiki says plainly that no page covers it. Amara asks again in Microsoft Teams, where she already spends her day, and the question goes to Priya, who owns customer policies, with what Amara asked and the pages she read. Priya answers her there. Amara can see in the wiki that her question is answered and closed.
Thursday: she points out what's missing
Reading the holiday policy, Amara notices it never says how staff swap shifts. She marks the page as unclear and adds a line saying why. The note goes to the people team, who own the page, and the next manager who asks gets a proper answer.
Friday: head office looks at the gaps
The operations director opens the wiki's analytics and sees what people asked that nothing answered. Three are about the new stock count app, so its owner writes one short page and every store has it by Monday.
What each employee gets to do
Start with what matters to them
Each person's wiki is personalized to their team, role and location. A store manager sees store procedures first; finance sees expenses and purchasing.
Ask about how things work here
Policies, processes, benefits, office and store routines: people type a question in everyday words and get a short answer with the pages behind it linked.
Get it done from the page
Where a process ends in a request, the form sits on the page. People submit it, get a confirmation, and the right team approves it.
Reach the owner, wherever they work
The wiki has a named owner for every topic. When pages don't cover something, people ask in Slack, Microsoft Teams or the wiki, and the question lands with that owner with the context attached. They see its status without chasing.
Say when a page is wrong
Anyone can mark a page as unclear or out of date and say why. The note goes to the page's owner, so the fix comes from the person who knows.
What the teams who own the pages get
Each team keeps its own pages and sets who can edit them. Unanswered questions, page feedback and form requests all arrive in one inbox your teams share, with a queue per team and topic. An owner claims a question, leaves an internal note for whoever takes it next, and answers in whatever channel the employee picked. Analytics show what people search for, what went unanswered and which pages get flagged, so each team knows which page to add or fix.
What changes for the company
Questions about how things work stop bouncing around. An owner writes the answer once on a wiki page, and the assistant uses it for everyone who asks after that.
People get answers in the tools they already have open. The same pages answer in Slack, Microsoft Teams and the wiki, any hour of the day.
"Who owns this?" always has an answer. Every page and topic has a named owner, and unanswered questions route straight to them.
You see what your company doesn't know yet. Unanswered questions and flagged pages show each team exactly what to write or correct that week.
The assistant, and the owners behind it
The assistant answers only from your wiki pages, and only from pages the person asking is allowed to open. It links every page it used, so anyone can check. When nothing covers the question, it says so rather than guessing and passes the question to the owning team. It can open a request for that team if you allow it, and each such step is recorded.
How to build your AI wiki
- Bring in what you've written. Import pages from Notion, Confluence, Google Drive or SharePoint, or write new ones in place.
- Give every topic an owner. Organize pages by team and topic, and name who looks after each area.
- Set who sees what. Label pages by team, role and location so each person's wiki fits them.
- Add the forms. Put request forms on the process pages that need them, with approval steps where they apply.
- Connect the chat tools. Turn on the assistant in the wiki, Slack and Microsoft Teams, and choose where unanswered questions go.
- Invite your people. Switch on single sign-on so staff sign in with their work account, then roll it out one team at a time.
Works with your existing tools
Notion, Confluence, Google Drive, SharePoint, OneDrive and Dropbox for the pages and files your teams already keep, Slack and Microsoft Teams so people ask from where they already are, single sign-on and automatic account setup from your identity provider, with webhooks and an API to connect anything else, out of 30-plus sources.
Keep exploring
| AI wiki on MatrixFlows | The usual company wiki | |
|---|---|---|
| Where to start | A home page personalized to each person's team, role and location | The same front page for all, and a sidebar of spaces |
| Getting an answer | Ask in plain words, get a short answer with the pages linked | Search, open five pages, work it out yourself |
| Where people ask | The wiki, Slack or Microsoft Teams, answered from the same pages | Only inside the wiki, so questions end up in chat instead |
| Knowing who owns what | Every topic has a named owner, and gaps route to them | Pages that outlive their authors |
| Acting on a process | The request form sits on the page, with approval and status | A link to another tool, or an email to someone |
| Reporting a wrong page | Feedback goes straight to the page owner | A message in a channel that nobody follows up |
| Finding the gaps | Analytics on unanswered questions and flagged pages | Hearing about it when someone gets it wrong |
An AI wiki belongs to your employee operations, and MatrixFlows runs those alongside customer service and partner support on one platform.