Question 1

Why can AI now handle most support tickets, and should it?

Accepted Answer

LLM agents can now read your help docs, past conversations, and backend data, which is why Intercom's Fin resolves around 56% of conversations on average and Decagon deployments at companies like Bilt report 75% resolution. The 'should' is more nuanced: Klarna famously replaced the work of 700 agents with AI, then publicly rehired humans in 2025 after quality complaints. The emerging consensus is to let AI own the repetitive tier while guaranteeing customers a real human path for complex or emotional cases.

Question 2

How do startups set up AI support (Intercom Fin, Decagon, custom bots) in a week?

Accepted Answer

The fastest path is buying, not building: point Fin or Chatbase at your help centre (Fin needs at least 10 public articles), write plain-language guidance and escalation rules, test it against real past conversations, then go live on chat first. Your knowledge base quality is the ceiling on resolution rate, so most of the week goes into fixing docs, not configuring software. If you build custom with Claude or an n8n workflow you get control and lower per-ticket cost, but budget more than a week.

Question 3

How do founders use support conversations as product research with AI?

Accepted Answer

Every ticket is a free user interview, and AI finally makes the whole corpus readable: founders pipe exports into Claude Code or tools like Enterpret to cluster complaints, surface feature gaps, and quantify which bugs actually cost revenue. Even your support bot's failures are research, an unresolved-questions report is effectively a ranked list of where your docs and product confuse people. The one discipline that matters is verification, forcing the AI to quote exact customer words so you act on real patterns instead of plausible slop.

Question 4

What does AI support actually cost, and how should a founder think about the ROI?

Accepted Answer

Two pricing models dominate: per-resolution (Fin's $0.99, you pay only when the AI actually solves a ticket) and platform or usage pricing, with enterprise players like Decagon tying contracts to outcomes. The honest math compares it to your fully loaded cost per human-handled ticket (typically $5-10), but read the fine print: 'assumed resolutions', handoff fees, and volume minimums make bills less predictable than the headline price. Klarna's $40M savings claim and subsequent walk-back is the reminder that ROI includes retention, not just deflected tickets.

Question 5

How do you stop an AI support agent from hallucinating and breaking customer trust?

Accepted Answer

Ground the agent in your real docs, explicitly bound what it may make claims about, label it clearly as AI, and give it a fast exit to a human. The failure cases are instructive: a court made Air Canada honour a refund policy its chatbot invented, and Cursor's support bot fabricated a login policy that triggered public cancellations. Before launch, test against hundreds of real past conversations, then monitor accuracy and hallucination rate (aim under 2%) as an ongoing operations job, not a one-time setup.

Question 6

When do customers still need a human, and how do you design the AI-to-human handoff?

Accepted Answer

Klarna's reversal settled the debate: AI keeps the volume, but customers must always be able to reach a person, especially for emotional, high-stakes, or account-critical issues. Good escalation fires on explicit requests, detected frustration, and risky keywords like refund or legal, and it transfers the full conversation context so the customer never repeats themselves. The team changes too: instead of a ticket queue, small startups end up with humans running AI operations, knowledge, and the hard 30% of conversations.

How founders use AI for Customer Support