Triage goes wrong when it is confident about a cause. A CSV export showing eight percent tax where the web view shows ten is a strong hint, and a template that let the agent name a root cause would produce a queue of plausible fiction. The rule here is to cite the words from the case that support the suspicion, and Hermes reasons well enough to find those words without going past them.
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.
Yuki Tanaka
Invoices exported with the wrong tax rate since Friday
Emaily.tanaka@murakami-denki.co.jp
NoteCase opened from the web form. Account Murakami Denki KK, Business plan, contact Yuki Tanaka, Finance Systems Lead, priority set by the customer to Medium, product field Billing, version 5.2. Description: since the update on Friday every invoice we export as CSV shows 8 percent consumption tax instead of 10 percent, while the same invoice in the web view is correct. It affects all 1,200 invoices we exported this morning for the July close and our accounting team has stopped the run. Nothing changed on our side apart from installing the update.
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Salesforce
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.
Triage rules
How you sort cases - your categories and what each one means, which queue or owner takes it, and the exact fields the agent may set at triage with the values it may use. Anything not written here is left for a human.
Escalation criteria
The cases that need a person immediately and a Slack ping - the severity, account tier, product areas, or wording that qualifies, and who should see them.
Runs on Hermes
Preselected for this page — connect your Hermes 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.
The suspected cause has to be supported by wording from the case itself, which turns a guess into a citation.
A customer mentioning contract review or a security report bypasses the normal flow. Recognising that inside a phone summary is a reading task.
That is the Angry Enterprise Case run, where a third failed export arrives alongside a renewal decision and a request for an account executive. Correct output keeps the comment to what the case says, skips the standard questions, and posts a Slack line saying a human owns it. Read that one before anything else on this template.
Free to start. Guided setup, a test run against staged conversations, and it's live.