Intercom Support Agent with OpenCode
An always-on chat agent is a per-conversation cost you pay all day, including for the conversations it correctly declines to answer. OpenCode is model-agnostic, so you set that cost yourself, and handovers are the cheap ones because the run stops after a note and a channel line. The Intercom operations it can call stay the same across models.
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.
Adding a teammate to the workspace
OpenSiobhan O'Rourke <siobhan@rathmoredesign.ie>
Hey, how do I get my colleague into our workspace? I only see my own name under members and we are on the Studio plan.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Intercom
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.
Support playbook
The answers you are happy to give without a human checking - your common questions, how-to steps, plan limits, and known issues, in your own words. The agent replies only when the answer is in here.
Escalation rules
The conversations a person must own - refunds, billing, account access, security, cancellations, angry customers, named accounts, whatever you decide. The agent acknowledges these and hands them over instead of answering.
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
Cost per conversation, chosen
Chat volume is not something you control, so controlling the model is the lever you actually hold.
Refusals are cheap
An escalation ends after two short writes with no reply drafting, which keeps the escalation-heavy days from being the expensive ones.
Before you fork
Does a smaller model handle other languages?
The instructions tell it to reply in the customer's language, and how well that lands varies more by model than by anything in the workflow. If you support customers in more than one language, stage a conversation in each and read the replies before going live. Switching the model afterwards does not touch your playbook or your escalation rules.
Run it with a different agent
Put Intercom Support Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.