Objective
Make the promise-to-pay path a test Ananya has to pass, and get an email when her calls start failing.The scenario
Three transcripts you can read; three thousand you can’t. Evals scores every completed call and replays one conversation path as a simulated call; Alerts watch a metric on a schedule. Ringg turns Evals on per agent: if the page says “No agents have evals enabled.”, write to admin@ringg.ai with the agent ID and do the alert first.Hands-on
Reviewing an agent's evals
1
Open Ananya's evals
Open Monitor → Evals and pick EMI reminder - Hindi. Metrics shows an average score per metric for the last 30 days, for the metrics enabled on the agent, such as Factual accuracy, Instruction following, Knowledge coverage and Tool accuracy. Issues groups the failures, each with Add as test case.
2
Write the test case
Click Create a test case, choose Voice, and on Write a prompt fill in:
- Name:
Promise to pay on 15 October - Conversation path:
The customer is Rahul Verma. He confirms it is him, listens to the amount, says he will pay on 15 October, then asks whether there is a late fee if he misses that date. - Success criteria:
The agent states the due amount and due date, confirms 15 October as the payment date, answers the late-fee question from the EMI policy, and ends the call politely.
3
Run it
Click Run tests. The case moves from Queued to Running, then to Passed, Failed or Not evaluated. Open it for the verdict, a reason per criterion, which version ran, and the simulated conversation. Not evaluated means the simulation never reached the situation; make the Conversation path more specific and Run again.
4
Create the alert
Creating an alert with email and webhook notifications
EMI reminder call failures and Scope to Agent, then pick EMI reminder - Hindi. Build the Trigger: check every 15 min for the last 1 hour, when Call failure rate is above 20 (rate thresholds are percentages). Under Notify via, expand Email, type your address and click Add. Click Save.Checkpoint
“Alert created”, and on the Agents tab of Alerts the rule sits under EMI reminder - Hindi with its condition, scope and channel, switch on. In Evals, the case shows Passed, or Failed with the criteria it missed.
Exercise
On the Workspace tab, under Recommended, click the pencil icon on Disconnection rate spike rather than Enable, add your email under Notify via and save. Expected result: the alert is on with your address as its recipient, firing when the disconnection rate is above 25% over the last 30 minutes. Enable alone adds no recipients.What you learned
- Evals scores every completed call; a test case is one conversation path plus success criteria, simulated against the published version.
- Not evaluated is neither a pass nor a failure: the simulation never reached the situation under test.
- An alert is a sentence: check every interval for the last window, when metric condition threshold. It needs at least one email, Slack or webhook target.