Use case

A support triage agent that clears the queue before your team opens it

Triage is the most automatable part of support and the least interesting to do by hand. Describe your categories, priorities and escalation rules once, and the agent applies them to every incoming request.

  • Every run logged
  • Revoke access instantly
  • Cancel any time
4 decisions

Category, priority, owner, first reply

Approval-gated

Nothing customer-facing sends unreviewed

Full log

Every triage decision is reconstructable

What the agent does on each request

It reads the request, decides what kind of issue it is, how urgent it is, and who should own it — then either drafts a reply or hands it straight to a human with its reasoning attached.

  • Classify by topic: billing, bug, how-to, access, churn risk
  • Set priority from your own rules, not a generic model guess
  • Route to the right queue, owner or channel
  • Draft a first reply grounded in your help docs and policies

The brief you'd actually write

"You triage inbound support requests for a B2B SaaS team. Classify each as billing, bug, how-to, or access. Anything mentioning data loss, a security concern, or a cancellation is priority one and goes to a human immediately with a summary. For how-to questions, draft a reply using our help docs and cite the article. Never promise a refund, a timeline, or a fix date."

Guardrails that make it safe to leave on

Triage decisions are cheap to reverse; customer-facing replies are not. Keep drafting automatic and sending gated until you trust the pattern.

  • Approval queue for anything sent outside the company
  • Hard escalation rules that bypass the agent entirely
  • Full activity log: what came in, what it decided, what it sent

Paste the brief on this page

It's a working triage brief. Adjust the categories to yours and run it against real requests.

Try the triage brief

What to measure in the first month

Track the share of requests classified correctly, how often a human overrides the priority, and how much of the first reply survives editing. Those three numbers tell you whether to widen the agent's remit or tighten the brief.

Where it plugs in

Google Workspace is connected today, so email-based triage works now. Slack, Zendesk and Jira triage arrive with those integrations — you can register interest on each app page and we'll tell you when it's live.

Common questions

How accurate is automated triage?

Accuracy depends on how specific your categories and escalation rules are, not on the model alone. Start with four or five clear categories, review the activity log for the first week, and tighten the brief where you disagree with it.

Can it reply to customers directly?

It can draft immediately and send only if you allow it. Most teams keep sending behind the approval queue until the drafts stop needing edits.

What happens to urgent issues?

Escalation rules in the brief take precedence over everything else. Anything matching them — data loss, security, cancellation — goes to a human with a summary instead of being handled by the agent.

Which channels does triage work in today?

Email-based triage works now through the live Google Workspace integration. Slack, Zendesk and Jira triage ship with those integrations, which are in build.

Describe your first agent today

Free to start. No credit card, no setup calls, no engineering ticket.

Get started free