DocsCore ConceptsIssue Reporting
Issue Reporting
QualityIssue Reports capture the problems your AI could not solve and forward them to you, instead of letting them disappear.
How an issue is created
- The AI detects the problem is still unresolved after a number of messages
- The visitor clicks “Report Issue” and submits details
- The visitor asks the AI to forward the issue — for example “forward my issue”
What happens next
- 1
The issue appears on your Issue Reports page
- 2
It stays linked to the conversation that created it
- 3
You open it and read the full context
- 4
You act on it manually and mark it resolved
What you can see
- The visitor’s description in their own words
- The complete transcript around the failure
- Which agent and channel it came from
- Exactly where the AI lost the thread
Notifications
- The issue shows up in your dashboard immediately
- Email notification if enabled
- The count is visible on your Overview so nothing sits unnoticed
Issue Reports vs Support Tickets
| Issue Reports | Support Tickets | |
|---|---|---|
| Created by | AI failure or visitor report inside chat | A formal request with subject and contact details |
| Best for | Finding AI knowledge gaps | Tracking a customer problem to resolution |
| Lives in | Issue Reports | Support Tickets, with claim and status |
Tip
Read your issue reports weekly and train the gaps. It is the fastest way to make the AI measurably better.