Notifications
Clear all
Topic starter
07/06/2026 8:24 pm
TL;DR: Intercom says its AI agent Fin can resolve 86% of customer conversations in some deployments, with 50% to 70% resolution rates common, showing that LLM-based support can now handle end-to-end customer interaction at scale, according to WorkOS. The governance shift is no longer about chatbots assisting humans, but about who owns identity, oversight, and accountability when software closes the conversation on its own.
NHIMG editorial — based on content published by WorkOS: Intercom went from skeptics to believers on AI
By the numbers:
- Today, Intercom's AI agent, Fin, handles 86% of customer conversations in some deployments.
- The typical deployment sees lower numbers, but 50-70% AI resolution is common.
Questions worth separating out
Q: How should security teams govern AI support agents that resolve customer conversations end to end?
A: Security teams should govern AI support agents as non-human identities with explicit ownership, scoped access, and defined closure authority.
Q: What breaks when an AI support agent is treated like a normal chatbot?
A: What breaks is accountability.
Q: Why do AI support agents change identity governance in customer service?
A: They change identity governance because the system is no longer just processing data in the background.
Practitioner guidance
- Classify the support agent as a governed NHI Assign an owner, define its business purpose, and record which customer data, knowledge sources, and workflow actions it may use.
- Set closure boundaries for AI-led conversations Document which issue types the agent may resolve without human review, which cases must escalate, and what signals trigger handoff before the conversation is marked complete.
- Log every answer path and escalation decision Capture the knowledge articles retrieved, the response class chosen, and the reason a case closed or escalated.
What's in the full article
WorkOS's full interview covers the operational detail this post intentionally leaves for the source:
- Brian Scanlan's first-hand explanation of why Intercom shifted from AI scepticism to deployment.
- The support use case characteristics that made GPT-based response generation work in practice.
- The operating model behind 86% resolution, including when humans still handle exceptions.
- The product and team reorganisation choices that followed the shift to AI-led support.
👉 Read WorkOS's interview on Intercom's AI support agent and 86% resolution →
AI support agents in customer service: what governance teams need to know?
Explore further
07/06/2026 10:17 pm
AI support resolution creates an identity governance problem, not just a service efficiency gain. When a system can close 86% of conversations without a human, it is acting as a delegated operator inside a customer process, not as a passive assistant. That shifts attention from response quality alone to authority, auditability, and accountability for outcomes. The practitioner conclusion is simple: if the AI can end the conversation, it must also be governed as part of the identity plane.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- Only 44% of developers are reported to follow security best practices for secrets management, exposing a significant developer behaviour gap.
A question worth separating out:
Q: How can organisations tell whether support automation is still under human control?
A: Look for clear escalation rules, human approval points for sensitive cases, and logs that show when the agent made a decision versus when a person intervened. If the workflow closes cases without a visible human checkpoint, the system has already crossed from assistance into delegated operational authority.
👉 Read our full editorial: AI support agents are changing customer service governance
