Zendesk CSAT Follow-up Agent with Hermes
Most of what arrives is not a problem. A rating your rules count as good is checked and dropped in a step or two, so a happy week costs a fraction of a rough one. Hermes runs on open Hermes models and suits work that never leaves your own systems, since the note lands on the ticket and the summary lands in your channel.
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.
CSAT 1/5 on ticket #48213
OpenYuki Tanabe <#48213>
Three different people asked me to send the same screenshot, and the third one asked me to explain the whole problem again from the beginning. Eleven days to change one setting. I have no confidence it would go any better next time.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Zendesk
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.
Followup rules
Which scores you want worked and what should happen to them: the threshold that counts as low, who gets the Slack line, the accounts or plans that always matter, and what a reasonable recovery step looks like at your company.
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.
Why Hermes for this agent
Good weeks are cheap weeks
The score check happens before any reading, so those runs are short. Cost tracks the ratings you chose to work rather than your survey response rate.
Nothing here reaches a customer
Everything this agent produces is read by your own team, which is the gentlest place to start with an open model. A clumsy sentence costs you a raised eyebrow.
Before you fork
These notes get read in one to ones. Is an open model steady enough for that?
The protection is structural rather than model dependent: it quotes the thread instead of characterising anyone, and it is told never to blame a named agent for something the ticket does not show. Read a week of notes before you lean on them in a review, and if the wording drifts, tighten the follow-up rules rather than hoping a larger model fixes it.
Run it with a different agent
Put Zendesk CSAT Follow-up Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.