u/DiscussionNo1778

Been using this setup for about a year so wanted to share something concrete rather than another generic AI chatbot post.

The problem we were trying to solve was not response speed. It was that 70% of our Zendesk queue had the same questions every week. Billing queries, plan comparisons, and integration troubleshooting with known fixes. Real people spending hours on work that had documented answers.

The Chatbase to Zendesk integration was the specific thing that made this viable rather than just interesting.

The handoff is what most setups get wrong.

When the AI agent cannot resolve something it creates a Zendesk ticket automatically with the full conversation history attached. The agent receiving it sees everything:

• What was already asked
• What the AI attempted
• How long the customer had been waiting
• ⁠What the sentiment looked like by the end

No cold starts. No repeated questions. That handoff quality is what kept CSAT from dropping the way it did when we tried a basic setup two years ago.

The tag system is worth knowing about.

Every ticket the agent touches gets tagged chatbase-involved. Anything it could not resolve gets tagged chatbase-routed-to-workspace. That makes reporting clean. You can see exactly what the AI handled versus what it escalated and track both separately without any custom setup.

What I check every week.

Low confidence responses in the logs almost always mean either a documentation gap or something in the product changed and the training data has not caught up. We auto retrain every 24 hours against our documentation site so product changes reflect by the next morning without anyone having to trigger it manually.

Four months in:

• ⁠58% of ticket volume handled without human involvement
• ⁠Average handle time on escalated tickets dropped from 23 mins to 11
• CSAT held rather than dropped because agents are not starting cold

Anyone else running Chatbase through Zendesk? Curious how others are handling the escalation threshold specifically, whether you are using confidence scores to trigger routing or something else.

Not writing this to bash Intercom. We still use Zendesk and the broader ecosystem works fine. This is specifically about the AI layer and why we moved.

Why we tried Fin first:

Already in the Intercom ecosystem. The promise of native AI that understood our existing conversations was compelling. Deployment was straightforward.

Where Fin fell short for our use case:

• Training data locked to Intercom content only. No way to pull from resolved Zendesk ticket history, PDFs, or custom Q&A pairs we had built over three years
• Confidence scoring not surfaced at the response level in a way we could act on operationally
• Escalation handoffs lost conversation context when routing outside the Intercom environment. Agents on Zendesk were starting cold
• Knowledge base gaps invisible until customers complained. No proactive signal for where the agent was uncertain
• Pricing at our interaction volume became a significant line item faster than expected

What we needed that Fin could not give us:

One agent trained on everything. Our help center, our ticket history, our internal SOPs, our Q&A pairs. All of it in one place, retraining automatically when anything changed, with confidence data surfaced so we could run a weekly maintenance process that actually kept quality high.

What changed after moving to Chatbase:

• Training now pulls from every source simultaneously. The agent sounds like our team instead of a generic help article
• Confidence score on every response used as a live routing signal. Below threshold it escalates instead of guessing
• Escalations to Zendesk carry full conversation history so agents never pick up cold
• Auto retrain every 24 hours means product changes reflect by the next morning
• Weekly log review on low confidence clusters tells us exactly where the knowledge base has gaps before customers find them

The numbers six months after switching:

• 71% resolution rate without human involvement
• Average handle time on escalated tickets dropped from 23 minutes to 11
• CSAT held rather than dropped because the handoff quality improved

Still running Intercom for live chat on certain channels. The AI agent layer is now Chatbase sitting on top of Zendesk for the support queue.

Anyone else moved away from a native AI layer toward a standalone agent? Curious whether the pattern holds across different ecosystems or whether this is specific to our setup.