Inbox Triage Agent with Claude Code
Triage looks trivial until you watch somebody do it: half the mail fits two categories and the tiebreak is whoever has to act. Claude Code reads the whole email, the quoted thread and the sender's domain before it commits to a label, and it is comfortable saying it could not classify something rather than forcing a route. On a shared inbox an honest fallback beats a confident wrong forward every time.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
All 34 stores offline since 09:40
Our tills stopped syncing at 09:40 this morning and all 34 stores are taking cash only. We restarted the local gateway in two stores with no change, so it looks like the problem is on your side. Saturday is our busiest day and we are losing roughly 40,000 kroner an hour. Please call my mobile, I am reachable all day.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Gmail
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Routing rules
Your categories, the exact Gmail label for each one, who owns it, and the fallback label and owner for mail that fits nothing. The agent never invents a label or sends to anyone outside this list.
Urgent criteria
What genuinely cannot wait, such as the senders, deadlines, amounts, or phrases that should interrupt someone, plus the channel that has to hear about it. Everything else is labeled and forwarded without a Slack ping.
Runs on Claude Code
Preselected for this page — connect your Claude Code account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why Claude Code for this agent
Careful on the ambiguous ones
Routine mail sorts itself. The value shows on the email that fits two categories, where reading properly before choosing keeps it off the wrong person's desk.
Respects the boundary
This agent may only label and forward, never reply, delete or archive. A harness that plans before acting is less inclined to improvise its way around a limit like that.
Before you fork
Does all that careful reading make it expensive on a busy inbox?
It costs more per email than a fast harness, because it reads more before deciding. At a few hundred emails a day that gap is small next to one misrouted contract, and at tens of thousands it is worth benchmarking against Codex on the same staged emails. Switching harness later leaves your routing rules untouched.
Run it with a different agent
Put Inbox Triage Agent to work on Claude Code
Free to start. Guided setup, a test run against staged conversations, and it's live.