Slack Support Agent with Hermes
Hermes runs on Nous Research's open models, which is the whole point for teams with a policy about where internal threads get processed. What it does here is closer to classification than recall: deciding whether a mention is a question, a bug report, or a restatement of something already filed. NoClick runs the harness and hands it your Slack and Linear operations as tools.
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.
Contractor access without billing visibility
Marta Nowak
@support how do I give a contractor access to one project only, without them seeing billing? A client asked this morning and I could not find it anywhere in the docs.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Linear
One sign-in. The agent acts through your account, scoped to what this template uses.
Product context
What your product does, the words your team uses for its parts, and where the real documentation lives. Paste the links you want people sent to.
Escalation rules
What the agent must not answer alone and who takes it instead. Name the person or channel for billing, security, outages, and anything a customer will see.
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
Internal threads, open stack
Engineering channels hold some of the most sensitive text a company writes. This harness keeps the reasoning over them on an open foundation you picked.
Classifying beats retrieving
The hardest call in this template is working out what kind of message just arrived. General reasoning is the strength Hermes brings before any tool is called at all.
Before you fork
Can we start on Hermes and move later if it does not work out?
Yes, and none of your setup is harness-specific. Product context, escalation rules, the connected Slack and Linear accounts, and the staged test threads all stay exactly where they are. Moving to a different harness is a field change rather than a rebuild.
Run it with a different agent
Put Slack Support Agent to work on Hermes
Free to start. Guided setup, a test run against staged conversations, and it's live.