Skip to main content
Understanding and optimizing the performance of Cevro is crucial to achieving the best results. This guide walks you through the key metrics, how to interpret them, and what actions to take based on what you see.

The Key Metrics

Your Analytics dashboard shows several metrics at a glance:
MetricWhat It MeasuresWhy It Matters
Automation RatePercentage of tickets resolved without human interventionYour primary success indicator
Total TicketsAll tickets processed by CevroVolume baseline
Automated TicketsTickets fully resolved by the AIDirect measure of AI effectiveness
Escalated TicketsTickets handed off to human agentsOpportunities for improvement
AICSATAI Customer Satisfaction score (1-10)Quality of automated resolutions
Resolution TimeAverage time to resolve a ticketSpeed of service
Time SavedHours of agent work automatedROI metric
Money SavedEstimated cost savings from automationROI metric
Each metric includes a Month-over-Month (MoM) comparison so you can track trends.

Automation Rate

The automation rate is the most important metric — it directly reflects how well Cevro is handling player support without human intervention:
Automation Rate = (Total Tickets - Escalated Tickets) / Total Tickets

What’s a Good Automation Rate?

There’s no universal target — it depends on your setup maturity and the complexity of your support operations. However:
  • First week: Expect lower rates as you’re still building AIPs and identifying gaps
  • After initial setup: 40-60% is typical for new deployments
  • Mature deployments: 70-85% is achievable with well-tuned AIPs and comprehensive knowledge base
The automation rate improves over time as you add more AI Procedures, fill knowledge gaps, and refine instructions based on real conversations.

How to Improve Your Metrics

1. Review Unresolved Topics

The Unresolved Tickets tab in Analytics shows exactly what players are asking about that Cevro can’t handle yet. Each topic is an opportunity:
  • High trigger count? → Create a new AIP or add a knowledge base article
  • Related to an existing AIP? → Your instructions may need updating
See Topic Monitoring for details on working with auto-generated topics.

2. Review Escalated Conversations

Check the Conversation Logs for escalated tickets. Common fixable causes:
Escalation ReasonFix
Knowledge gapAdd a KB article covering the topic
Missing AIPCreate an AIP for this ticket type
Incomplete instructionsUpdate the AIP’s SOPs with the missing scenario
Tool errorCheck tool configuration and back-office connectivity

3. Monitor AICSAT Scores

Low AICSAT scores on specific AIPs indicate quality issues. Review those conversations to understand whether the AI’s responses are accurate, helpful, and on-tone.

4. Use the Playground

Before deploying changes to live traffic, test them in the Playground. This lets you simulate player conversations and verify that your updates work as expected.

Filtering and Drill-Down

Use the filters at the top of the Analytics page to narrow your view:
  • Date range — Compare performance across time periods
  • Brand — See how individual brands perform
  • Category — Focus on specific AIP categories

Continuous Improvement Cycle

1

Review analytics weekly

Check automation rate trends, new unresolved topics, and AICSAT scores.
2

Prioritize by impact

Focus on the highest-volume unresolved topics first — they’ll have the biggest effect on your automation rate.
3

Make targeted improvements

Add or update AIPs and KB articles based on what you find.
4

Test before deploying

Use the Playground to validate changes, then activate.
5

Measure the results

Check if the changes improved the metrics in the following period.