HubSpot Ticket Triage Agent with OpenCode
Classification is the entire risk here, since priority and category feed saved views, SLA timers and every service report you run. OpenCode leaves the model choice open, so you can start on something modest, read a fortnight of notes against your own rules, and move up only where the categories are drifting.
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.
Pieter Coetzee
No payout has reached our bank since the account migration on Monday
EmailSupport Pipeline, email inbox
NoteWe were migrated to the new merchant account on Monday and nothing has settled to our bank since. Your dashboard shows three settlement runs as complete, references SR-88412, SR-88530 and SR-88604, and our bank has received none of them. We pay 46 drivers on Friday and the chat widget quoted 48 hours for a reply. Our account manager is on leave until the 19th.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect HubSpot
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 tickets get sorted here - your categories, the priority each one earns, which pipeline or teammate owns it, the exact properties the agent may set with the values it may use, and where a ticket goes when it fits none of them. Nothing outside this is a judgement the agent gets to make.
Runs on OpenCode
Preselected for this page — connect your OpenCode 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 OpenCode for this agent
The fallback has to be used
A ticket matching nothing takes the fallback your rules name plus a sentence saying it matched nothing. Inventing a category to avoid an awkward answer is the drift to watch for.
A queue is good comparison ground
Support work arrives in comparable pieces every day, which makes it unusually fair ground for judging one engine against another over a week.
Before you fork
We run two support pipelines for two brands. One workflow or two?
Two, in most cases. The triage rules are where categories, priorities and owners live, and two brands rarely share all three, so a fork per pipeline keeps each rulebook readable. Connections and the Slack channel can differ per copy as well, which is usually what a second brand wants anyway.
Run it with a different agent
Put HubSpot Ticket Triage Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.