/dashboard/issues, under Quality & Testing)
collects problems detected across your calls and groups repeat
occurrences into patterns, so fifty instances of “agent quoted the
wrong hours” show up as one row with a trend line — not fifty separate
reports.
Where issues come from
- System — raised automatically by ThunderPhone’s call analysis when it detects something going wrong on a call.
- User — raised by people: reported from a call’s detail page or filed via the issue reports API.
Triage
Every pattern row shows its severity, an occurrence trend sparkline, the number of affected calls, its status, and when it was last seen. Statuses:
Change a pattern’s status inline from its status control, or select
several rows (including “all matching”) and update them in bulk.
Filter pills mirror the columns: Status (defaults to Open),
Severity, Source, free-text Search (title, trace, or call
ID), and a Date range — plus Reset filters.
Dig into a pattern
Click a row to open the detail panel: the pattern’s description, its occurrence history, and the affected calls, each linking to the full transcript in call history so you can see the failure in context.Fix with AI
From the detail panel, Fix with AI starts an investigation: the AI studies the affected calls, forms hypotheses about the root cause, and drafts targeted prompt fixes for the agent — shown as redline diffs you review before anything is applied. Leave and come back anytime; the button becomes Resume fix while an investigation is in progress.Next steps
Alerts
Get notified when quality metrics slip, before issues pile up.
Simulations
Turn a fixed issue into a regression test scenario.