AgentClash

Use case

Evaluate customer support agents on real resolutions

Support agents must resolve tickets safely, use the right tools, and leave an audit trail. AgentClash evaluates full support trajectories and keeps replay evidence when tone, policy, or resolution quality regresses.

live eval
gate: pass

Candidate

92correct patch, low cost

Baseline

88stable reference run

Control

73missed edge case

replay timeline

1loaded task inputs and tool policy
2ran sandbox actions and captured artifacts
3scored trajectory and validator evidence
4attached scorecard and release verdict

ci verdict

Candidate clears release gate

Correctness improved, latency within budget, and required artifacts were preserved for review.

agentclash run create --follow

Support eval signals

Built for reviewable agent decisions

Score resolution correctness, policy adherence, tool usage, escalation behavior, and customer-facing artifact quality.

OpenTelemetry-compatible trace import

Pinned datasets and golden test cases

Baseline versus candidate regression checks

Replay trails for tool calls, outputs, and artifacts

Scorecards for correctness, cost, latency, and evidence

CI gates for prompt, model, RAG, and tool changes

Workflow

Support eval workflow

Import the evidence

Start from OpenTelemetry traces, curated datasets, support transcripts, or a real failure your team already saw.

Pin the baseline

Record the current accepted behavior so every prompt, model, RAG, or tool change has a fair comparison point.

Replay the evidence

Inspect tool calls, outputs, artifacts, latency, cost, and judge evidence when a candidate gets worse.

Gate the release

Compare candidate and baseline runs, then fail CI before a regression reaches users.

FAQ

Support agent evaluation FAQ

Can AgentClash evaluate multi-turn support flows?

Yes. Multi-turn challenge packs support scripted, simulated, and human phases for realistic support conversations.

How do teams measure policy adherence?

Challenge packs encode required actions, forbidden tool use, and validator checks so scorecards reflect policy—not just friendly language.

Can support evals gate releases?

Yes. Compare candidate and baseline scorecards in CI before deploying a new support agent or model route.