Test your knowledge base
Ask a realistic customer question and review the answer, evidence, and readiness signals before relying on your knowledge.
Updated
Use Test knowledge to check whether your published Knowledge contains a safe, supported answer before teammates or AI rely on it during customer conversations.
Run a test
- Open Knowledge.
- Select Test knowledge.
- Enter a realistic customer question.
- Select Test answer.
- Review the answer preview and readiness badges.
Nothing from a test is sent to a customer or added to customer-facing activity.
Review the result
Check more than the generated wording:
- Answer preview shows the response that the available knowledge supports.
- Why Protodesk answered this way explains the interpreted intent and decision.
- Sources used lists the content supporting the answer.
- Retrieved evidence shows the ranked passages inspected during the test.
A fluent answer is not enough. Confirm that the cited source is current, directly supports the claim, and applies to the customer's situation.
Improve a weak result
If Protodesk cannot produce a supported answer:
- Identify the missing or contradictory fact.
- Update the relevant Knowledge article or source.
- Publish the corrected content.
- Run the same question again.
- Try a few alternative phrasings customers are likely to use.
Test high-impact subjects regularly, especially billing, account access, security, refunds, and anything that could cause an irreversible customer action.
Related articles
- Use Protodesk AssistConfigure Assist and review grounded reply suggestions, writing tools, translations, follow-ups, and ticket context.
- Add knowledge to ProtodeskCreate or import trusted knowledge that your team and Protodesk AI can use when answering customers.
- Configure AI automationCreate a versioned workflow, review its scope and credit budget, and activate it deliberately.
- Understand AI creditsReview your shared workspace balance, see where credits were used, and keep AI usage predictable.
- Review Knowledge coverage gapsFind customer questions that could not be grounded safely and turn repeated gaps into better knowledge.