Key Metrics
Deflection Rate
Percentage of conversations handled without human intervention.- Higher = more automation success
- Target varies by use case (typically 40-80%)
- Add more knowledge
- Improve agent configuration
- Fill knowledge gaps
Resolution Rate
Percentage of conversations successfully resolved (per your resolution rules).- Higher = better customer outcomes
- Depends on resolution rule definition
- Review resolution rules for accuracy
- Improve response quality
- Address common failure patterns
Escalation Rate
Percentage of conversations escalated to humans.- Lower is often better, but some escalation is healthy
- Too low might mean missing issues that need humans
- Tune escalation rules
- Add knowledge for common escalation topics
- Review if escalations are appropriate
Response Time
Time from customer message to agent response. Metrics:- P50 (Median) — Half of responses are faster
- P95 — 95% of responses are faster
- Average — Mean response time
Time to Resolution
Total time from first message to resolution. Metrics:- P50, P95, Average
- By category
- Trend over time
Viewing Metrics
1
Navigate to Performance
Go to Analyze → Performance.
2
Select Date Range
Choose the time period to analyze.
3
Filter by Deployment
Optionally filter by specific deployment.
4
Review Metrics
See metric cards with current values and trends.
Trend Charts
See how metrics change over time:- Daily, weekly, or monthly views
- Compare to previous periods
- Identify trends and anomalies
Filtering
By Date Range
- Last 7 days
- Last 30 days
- Last 90 days
- Custom range
By Deployment
View metrics for specific deployments:- All deployments
- Individual deployment
- Compare deployments
By Category
See performance per category:- Which categories resolve best?
- Where does escalation happen most?
Benchmarks
Comparing Periods
See change from previous period:- ↑ 5% Deflection rate improved
- ↓ 2% Escalation rate decreased
By Deployment
Compare deployments side-by-side:| Metric | Zendesk | Slack | Intercom |
|---|---|---|---|
| Deflection | 65% | 72% | 58% |
| Resolution | 82% | 85% | 78% |
| Response Time | 2.1s | 1.8s | 2.5s |
Taking Action
When Deflection is Low
Causes:- Missing knowledge
- Poor agent configuration
- Complex issues
- Review knowledge gaps
- Improve runbooks
- Add more documentation
When Escalation is High
Causes:- Overly sensitive guardrails
- Missing knowledge
- Complex customer base
- Tune escalation rules
- Add knowledge for escalation topics
- Review escalation patterns
When Response Time is High
Causes:- Complex processing
- Slow external APIs
- Large knowledge searches
- Optimize runbooks/workflows
- Check tool performance
- Review execution logs
Exporting Data
Export metrics for external analysis:- CSV download