Content quality
How Fibly automatically assesses knowledge base articles and what each status means.
After you save an article, Fibly analyzes it for usefulness to the bot and assigns it one of the statuses shown in the Quality column of the article list and under Quality for RAG next to the editor. This helps you quickly spot material that needs improvement.
The status is a guide for you. It doesn't decide which articles the bot reads: the bot searches all articles in active knowledge bases, whatever their status. A weak article simply leads to weaker answers.
Statuses shown in the panel
Ready
The article scored 70 or more out of 100. It is the right length, stays on topic, and contains content that specifically answers real questions.
Needs improvement
The article scored between 40 and 69. The content is technically correct, but it has problems:
- it's written very generally, with no specifics,
- it repeats information from other articles,
- it mixes several topics into one entry,
- it uses jargon the customer probably won't understand.
The bot still uses such an article, but the answer quality will be lower. Expand Scoring details next to the editor to see the score for Clarity, Structure, Completeness, Actionability, and RAG readiness, plus a summary with specific suggestions.
Not ready
The article scored below 40, so it is a poor source for answers. The most common reasons:
- it consists mainly of visual elements (images, tables with no description),
- it's empty or contains only headings with no content,
- it's so inconsistent in topic that the model can't extract any useful information from it.
Answers built on such an article are unreliable. Open the entry and add content, or delete it.
Too short
The article has fewer than 150 characters, so Fibly doesn't score it. That is too little text for the bot to make sensible use of. Expand the content, or merge the article with another related one.
When the status changes
The status is calculated when you save an article. After you edit the content, it goes through the analysis again. If you change many articles at once (e.g. after a large import), updating the statuses may take a moment.
What to do with low-quality articles
- Sort the list by status and deal with Not ready entries first.
- Merge related entries into one, more detailed article.
- Add specifics: dates, amounts, the steps of a procedure.
- Remove duplicates; the bot doesn't need three versions of the same piece of information.
What's next
Once the base is in good shape, take a look at the best practices. It's a collection of tips that help you keep quality high over the long term.