Skip to content
← Back to blog
Company BrainArticle

Unanswered questions: what knowledge to add

After a company assistant launches, some questions still go to experts. A label saying “unanswered” gives the person developing the library little to work with. They need to know what the employee could not accomplish and whether the gap calls for a shared explanation or information about one particular case. That determines what is worth adding.

Author

Syntalith

Published Updated 3 min read

Syntalith can build a view of recurring questions into a Company Brain project and connect it with the work of the people developing your knowledge. The proposed scope includes questions and feedback the company permits for review, related needs grouped together, and the material the team wants to improve. Managers get a basis for choosing the next content priorities. Experts decide what can become guidance for everyone.

Different questions can reveal the same gap

Suppose employees ask what to hand over before vacation, where to describe open work, and how to name a backup. The assistant finds a general organizational page that does not explain how to prepare a handover. The questions look different, but experts keep explaining much the same thing.

In the proposed view, a knowledge editor can see those questions together and decide that the team needs a handover guide. They develop it with team leads. A question about the state of a particular case still belongs with that case's records. It does not become part of a shared guide simply because it appeared in the same conversation.

This gives editors evidence for a decision. Repetition matters, but so does the work held up by a missing explanation. An uncommon question may concern a task that is difficult to hand over. A popular topic may already be well documented, with employees struggling to reach the page. Better navigation may then be more useful than another article.

From feedback to useful guidance

Keep a short explanation of what the user could not do after reading the answer. “I could not find the backup contact” says more than a negative rating alone. The reviewer can distinguish missing content from an explanation that was hard to follow.

The shared view should contain the information needed to improve the library. Your company decides who may read conversations and which details should be left out. An expert does not need a user's entire history to write a general handover guide. The person reporting a problem should also know where to see whether it has been explained or addressed in the materials.

After adding a page, the editor returns to the questions that prompted it. With users, they check whether people can now find the information and complete the task. Publication alone does not show that the recurring request has been answered.

Your platform may already expose the questions

Microsoft describes reviewing questions, responses, cited sources, and user reactions in Copilot Studio. Access requires the appropriate role. This can provide material for a knowledge-gap review; the team still decides what content to produce.

If you already maintain content requests and an editor regularly reviews them, connecting that work with available reporting may be enough. A custom application makes more sense when questions are scattered across the assistant, chat, and internal support, leaving editors to reconstruct what people need. Syntalith can connect those materials within an agreed scope and help turn a question into an editorial task.

Start with a topic your experts keep explaining. We can discuss which questions to bring together and who will judge whether new content helps. Ask about Company Brain, or see Syntalith's pricing page.

Syntalith is a member of Claude Partner Network, Anthropic's partner program.

Denotes membership in Anthropic's partner program for Claude. Not an endorsement of Syntalith's services by Anthropic.

Make company knowledge easier to use

Tell us what employees need to find and where the information lives. We will discuss Company Brain’s scope, source access and how it would fit the team’s work.

Explore Company Brain
Discuss Company Brain