Knowledge Knowledge Gaps
Question not answered.Don't just stay in the chat record.
Repeatedly asked by visitors, sentences that are rejected or poorly answered by the knowledge base contribute to the knowledge gap. Checking permissions can be seen in the list, promoting the problem to a draft FAQ, and then following clearance.
Source
The gap comes from real conversation, not from product managers.
There is a "knowledge gap" in the back office knowledge group. Deposition by site: original sentence, cause, source list. The noise can be removed in bulk. When you have write permissions, the first key generates the FAQ draft, and you are still waiting for the release to avoid unreading the content immediately.
- This page needs to be examined / live.qa permissions
- The desk also has a knowledge gap view that allows agenting to be marked.
- The issue title can be changed when promoted and the target knowledge pool selected
- Retrieving test hit rate; gap pages follow sentences that are not answered.
Closed
After promotion, check with the sandbox
Once the draft has been released and the vector has been re-established, a search assessment is used to see if the rejection rate has come down, and the original sentence is run again in a sandbox. Don't write down the agenting habits in FAQ; that's about the jargon. FAQ External, speech to man.
Next