When Muninnbase doesn't know: thumbs down and feedback

A knowledge base is only as good as the documents inside it, and no set of documents is ever complete on day one. The thumbs-down button is how you tell your admins where the gaps are. Thirty seconds of feedback from you saves the next five people the same frustration.

Two situations call for thumbs down

Situation one: the system says it doesn't have an answer. You see the message "I don't have an answer to that in the available documents." and no source pills below it. The question is real, but the answer isn't anywhere in your company's uploaded files.

Situation two: the system gives an answer that is wrong, incomplete, or out of date. Maybe the policy it cited was replaced last year. Maybe the answer covered the rule but missed the exception that actually applies to you. Maybe the SOP it returned is for the old expense system.

Both are worth flagging. The thumbs-down button below the answer is how you do it.

What happens when you click thumbs down

The button fires immediately. The icon fills in red and a quiet "Thanks for your feedback." line appears under the answer to confirm the click.

If your admin has turned on comments, a small text box appears next to the buttons with Send and Skip. You can use it to leave a one-line note explaining what was wrong or what you actually expected. The note is optional. Skip is a perfectly fine choice if you just want to flag the answer and move on. If comments are off in your tenant, the thumbs-down submits on click and there's no box at all.

Where the flag lands

Every thumbs-down lands in the admin's Unanswered Events queue with your question (and your comment, if you left one) attached. The admins who run your knowledge base review that queue and use it as their documentation backlog. A question with five thumbs-downs is a louder signal than one with a single thumbs-down, and the queue surfaces the patterns.

You will not get a notification when something gets fixed. The next time you ask the same question, you'll either get a real answer (which means a document was added or updated) or the same no-answer message (which means it's still on the list).

Why it's worth doing

The knowledge base only gets better when someone tells it where it's wrong. If you saw a bad answer and shrugged, the next person to ask the same question is going to see the same bad answer. The thumbs-down button is the difference between a system that improves over time and one that doesn't.

This is also why the chat is more useful at month three than at month one. The thumbs-down signal compounds. Every flag pulls another gap into the open.

What about thumbs up?

Use it. The positive signal is just as useful, because it tells your admins which answers are landing cleanly and which documents are doing the heavy lifting. There's no comment box for thumbs up; the click is the whole gesture, and it takes about a second.

What to do next

The best way to reduce how often you'd reach for the thumbs-down button is to ask sharper questions in the first place. How to ask a good question covers the small habits that make the answers better without changing anything about the documents.