All loops
SupportMedium 9 min· claude-opus-4-1
Reply-time SLO watcher
Reply-time SLO watcher powered by Claude over your help desk.
Read the full Support build guide →NOT DEPLOYEDNOT DEPLOYED
0155ms
Trigger
POST https://hooks.claudeloops.run/reply-time-slo-watcher · event=linear.issue.updated
02935ms
Agent
claude-opus-4-1 · in 1235 tok · out 396 tok
03205ms
Tools
fetch-mcp/anthropic:messages.create → 200 OK · 175ms
0445ms
Verify
schema check · pydantic v2 passed
0575ms
Output
ticket #4821 triaged · macro suggested
0635ms
Notify
audit log written · runbook link attached
SUCCESS
0%
0 runs
P50
0ms
median
P95
0ms
tail
AVG COST
—
per run
LAST OK
never
—
LAST FAIL
never
none
Latency · last 30 runs0 samples
no runs yet
Latest output · what your users see
Zendesk #5255P3
Cannot revoke API key from dashboard
macro applied: escalate:billing/no-vat-line
// press Test to run once · Watch live to keep streaming · Deploy to make it real
The problem
Support volume scales faster than headcount.
The outcome
Claude takes the first pass; humans focus on judgement calls.
Ingredients & skills
Secrets
- ANTHROPIC_API_KEY
- ZENDESK_TOKEN
Providers
- Anthropic
- Zendesk
MCP servers
- fetch-mcp
#support#cx#helpdesk
How it works
Reply-time SLO watcher powered by Claude over your help desk.
Step 1
1 — Trigger on ticket
Webhook from Zendesk fires the agent.
Step 2
2 — Act
Tag, draft, route — never close without human review.
Step 3
3 — Log
Every action is logged in the audit trail for QA.
One-line deploy
The button above runs the same command with your saved config. This is the raw CLI form.
bash
npx claudeloops deploy reply-time-slo-watcher https://hooks.claudeloops.run/reply-time-slo-watcher