Zendesk
Category
Customer support
Vendor AI agents
Use cases
Disputes & support cases
Zendesk holds the conversation. Forest holds the case, role, data, and audit trail, right in the ticket.
The Forest app puts your operational data inside the Zendesk ticket sidebar: KYC status, plan, transactions, without leaving the ticket. Every agent connects with their own Forest account: same role, same permissions, same audit trail as the back-office. Runs on top of your Forest MCP Server; Smart Actions trigger from the sidebar, logged like any other action. Forest never stores the customer data passing through.
The ticket doesn't need a new tab. It needs your data.
Zendesk holds the conversation. Forest holds the case: the record, the KYC status, the transaction, the Smart Action. The app puts that inside the ticket sidebar instead of sending the agent to a second screen.
Zendesk shows the ticket. Forest decides what the agent can do with it.
Every field an agent sees and every action they trigger from the sidebar passes through their Forest role first. No separate permission model to build inside Zendesk. The same role, the same audit trail, applied automatically on every ticket.
One login. One role. Two surfaces.
An agent signs in once, with their own Forest account. Whatever their Forest role allows in the back-office is exactly what they get in the ticket sidebar — no Zendesk-specific permission model to configure and let drift out of sync.
Same rules for the sidebar and the back-office.
Every action triggered from the sidebar logs to the same audit trail as the rest of Forest. Nothing Zendesk-specific to reconcile at audit time.
The channel changes. The record of what happened doesn't.
Resources & install
The Forest app puts your operational data inside the Zendesk ticket sidebar: KYC status, plan, transactions, without leaving the ticket. Every agent connects with their own Forest account: same role, same permissions, same audit trail as the back-office. Runs on top of your Forest MCP Server; Smart Actions trigger from the sidebar, logged like any other action. Forest never stores the customer data passing through.
Frequently asked questions
Where do I install the Forest app?
From the Zendesk Marketplace. Install, enter your Zendesk URL, then your Forest MCP Server URL in the Admin Center. Full steps in our documentation.
What do I need before installing?
A Forest project with the MCP Server already enabled, and its URL. No MCP Server yet? Set that up first, it's the one prerequisite before the app can read or write anything.
How does an agent connect their Forest account?
In the sidebar: Connect with Forest, sign in with Forest credentials, pick Organization, Project, Environment, Team. Each agent connects under their own identity, not a shared login.
What can an agent see and do through the app?
Only what their Forest role allows. The app matches the ticket to a record, shows the fields you configured, lets the agent search your collections, and triggers Smart Actions, every action logged, same as in Forest itself.
Does Forest store the customer data shown in the ticket?
No. Customer data passes through Forest's servers in transit, to surface inside the ticket. Nothing is written to disk or kept after the request completes.
Can I test this without touching production data?
Yes. Each Forest environment has its own MCP Server URL. Point the app at your staging URL to test, at production to go live; same app, different environment.
Does the app run full Workflows, not just actions?
Not yet. The app triggers Smart Actions manually from the sidebar, one at a time. Full Workflows support inside Zendesk isn't live; that's a roadmap item, not a shipped capability.
Do you have more questions?
Book time with a Forest expert.
