Schedule overview
| Routine | Frequency | Time required | What to check |
|---|---|---|---|
| Daily check | Every day | 10-15 min | Dashboards, recent errors, handoff rate |
| Weekly review | Every week | 30-60 min | Trends, unhandled queries, sample calls, test sets |
| Monthly deep dive | Every month | 2-4 hours | Month-over-month metrics, knowledge audit, function optimization |
| Pre-deployment | Before each promotion | 20-30 min | Test sets, manual testing, integration checks |
| Post-deployment | After each promotion | 30 min | Live calls, key metrics, function logs |
Daily check
Spend 10-15 minutes each morning:- Review the Standard dashboard — check call volume, handoff rate, and latency against your baseline
- Scan recent errors in Analytics > Conversations filtered to last 24 hours
- Spot-check handoff reasons for new patterns — or ask Smart Analyst: “What are the top handoff reasons from the last 24 hours?”
- Verify integrations — look for API errors in function logs
Red flags
Stop and investigate if you see:- Handoff rate > 50% (or 20% above baseline)
- Average latency > 3 seconds
- Error rate > 5%
- Call volume drop > 30%
Weekly review
Spend 30-60 minutes each week:- Compare this week’s metrics to last week (call volume, containment, duration, latency)
- Review unhandled queries in dashboards — prioritize knowledge gaps
- Run a Smart Analyst deep sampling query to surface trends across hundreds of conversations at once — for example: “What are the top 5 reasons calls are handed off this week?” or “What knowledge gaps are causing containment failures?”
- Listen to 5-10 calls flagged by Smart Analyst (mix of successful and unsuccessful)
- Check test set results for regressions
- Plan improvements for the following week based on Smart Analyst insights and test results
Monthly deep dive
Spend 2-4 hours at month end:- Compare all key metrics month-over-month
- Use Smart Analyst deep sampling for a comprehensive analysis — sample up to 500 conversations to break down containment by handoff reason, identify recurring failure patterns, and surface sentiment trends. Try: “Analyze the top transfer reasons and containment blockers over the last 30 days with percentage breakdowns.”
- Audit all Managed Topics for outdated content — use Smart Analyst to identify knowledge gaps: “What questions are we not handling well?”
- Review function performance — optimize or refactor slow functions
- Maintain test sets — add new scenarios, remove obsolete ones
- Review version history — document major changes
Pre-deployment check
Before promoting any version to Pre-release or Live:- Run all test sets — investigate any failures before promoting
- Manually test critical user journeys and edge cases
- Test all external API integrations
- Check voice quality and pronunciations
- Compare to the current Live version using diffs
- Have a rollback plan ready (identify last known good version)
Post-deployment monitor
After promoting to Pre-release or Live: First 30 minutes:- Watch Conversation Review in real time
- Monitor latency, error rate, and handoff rate
- Verify function logs show no errors
- Be ready to rollback
- Check metrics every 2-4 hours against baseline
- Review handoff reasons for new patterns
- Analyze full week of data vs. pre-deployment baseline
- Document lessons learned
Rollback triggers
Rollback immediately if:- Error rate > 10%
- Handoff rate doubles
- Critical function failures
- Customer complaints spike
Tips
- Start small — if you can’t do everything, prioritize daily checks and pre-deployment checks (highest ROI)
- Let Smart Analyst do the heavy lifting — instead of manually reviewing calls, use Smart Analyst deep sampling to analyze hundreds of conversations in minutes. It’s especially effective for weekly and monthly reviews where you need to spot patterns across large volumes of data.
- Automate — use test sets for regression testing and the Alerts API for anomaly notifications
- Adjust frequency — high-volume or mission-critical agents need tighter monitoring; stable agents can relax the schedule

