Configure Red Flags & Labels

​

What Are Red Flags?

A red flag is a structured signal that Tuner attaches to a call when one or more rule conditions are satisfied. Unlike evals — which score individual behaviors — red flags represent a composite judgment: a call is flagged when a combination of eval failures, voice metrics, and call classification outcomes cross a threshold you define. The same Rule Builder that creates red flags also creates labels — contextual tags that categorize calls without marking them as failures (e.g. long_agent_monologue, sluggish_conversation). Both types appear in the call logs and are surfaced in the Overview dashboard.

---

​

Where Red Flags and Labels Surface

​

Overview Dashboard

Red flags appear in the Recent Red Flags section of the Overview dashboard, giving you a prioritized queue of calls that need attention without requiring you to manually filter call logs. Each entry in the table exposes:

​

Call Logs

Both red flags and labels appear as color-coded tags on every call row in the call logs. This lets you filter and sort the full call history by the behavioral patterns you care about.

---

​

How Red Flags Are Triggered

Red flags and labels are defined in the Rule Builder inside Agent Settings → Evaluation Rules. Each rule is a named condition set. When all conditions in the set evaluate to true for a call, Tuner applies the corresponding tag to that call.

​

Adding a Rule

Click + Add Rule in the Evaluation Rules tab to open the rule builder. Each rule is configured with:

​

Available Condition Types

You can build conditions from any of the following signal sources: Combining condition types lets you express nuanced failure patterns. For example, a “Frustrated and Mishandled” flag might require Sentiment = Negative AND Missed Intent = FAIL AND Escalation Handling = FAIL — ensuring only calls with all three problems get flagged, not every slightly negative call.

---

​

Example Rules

​

Hallucination Detection

​

Compliance Breach

​

High-Risk Failed Call

​

Sluggish Conversation (Label)

---

​

Investigating a Red Flag

Clicking View on any entry in the Recent Red Flags table — or clicking a flagged call in the call logs — opens the Call Details view. From there:

• Transcript — Read the conversation verbatim to see exactly what was said at the point of failure.
• Events timeline — Trace the sequence of tool calls, transfers, and state transitions to find where the call went off track.
• Eval results panel — See all eval scores for the call in one view. A flag triggered by hallucination = FAIL will show exactly which eval tripped and at what point in the transcript.
• Voice metrics — Check for anomalies like extended silence, excessive crosstalk, or a large talk-time imbalance that correlate with the flag.

​

Investigating Patterns at Scale

When the same flag type recurs across many calls, investigating one at a time becomes impractical. The Tuner MCP Diagnose agent reads all calls sharing a flag type, clusters them by intent and outcome, surfaces the shared root cause, and can write a fix directly to your agent configuration.

---

​

Alerting on Red Flags

Red flags are silent by default — they surface in the dashboard and call logs but do not notify anyone. To get notified when a flag fires, create an alert in Agent Settings → Alerts. When creating an alert, you can select a specific red flag as the trigger field — either by individual flag name (e.g. hallucination_detected, negative_sentiment) or by Red Flag Count to fire when any flag exceeds a threshold within a time window. You can configure:

• Trigger field — a specific red flag, a data field, or Red Flag Count
• Operator and value — e.g. Equals FAIL, greater than 3
• Count vs Percentage — fire when N calls match, or when X% of calls match
• Time window — evaluate the condition over the last 1 hour, 24 hours, etc.

See How to Configure Real-Time Alerts for a full step-by-step guide.

---

​

Next Steps