Microsoft Teams Support Agent with OpenCode
Watching one busy channel is cheap and watching every channel in the company is not, which makes the model behind the harness a budget decision. OpenCode is model-agnostic, so you can cast a wide net on something modest and reserve a stronger model for the channel that faces customers. The Notion access and the Teams reply tool are identical either way.
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.
Folder level permissions on the Standard plan
Sanne de Vries
Can a customer on Standard restrict one folder to a single department, or is that Enterprise only? I am on a renewal call in ten minutes and I do not want to promise the wrong thing.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect Microsoft Teams
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Notion
One sign-in. The agent acts through your account, scoped to what this template uses.
Product context
What you build, the internal names your colleagues use for its parts, and which Notion pages count as documentation rather than someone's notes. Put the links you want people sent to in here.
Escalation rules
The questions that are not the agent's to answer, and the named owner each one goes to. Cover outages, billing, security, and anything that ends up in front of a customer.
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
Wide net, modest model
Being able to set the model is what turns watching six channels from an expense into a rounding error.
Open tooling, internal use
In an engineering org, an open harness answering the team's own questions is usually an easier conversation than a closed one.
Before you fork
What happens when the docs do not settle the question?
One line saying so is the entire reply, and then it hands the question to whoever your escalation rules name. That behaviour is instructed rather than enforced, and a weaker model is likelier to reach for a plausible answer instead. Stage your roadmap question and confirm it declines before you widen the channels.
Run it with a different agent
Put Microsoft Teams Support Agent to work on OpenCode
Free to start. Guided setup, a test run against staged conversations, and it's live.