Guide · 14 minute read
How to build a customer support agent for your business
Channel choice, knowledge setup, escalation design, and honest pricing for SaaS vs custom builds.
Benjam Indrenius
Founder of localbot
Published 2026-04-26 · Updated 2026-05-23
The short answer
The good support agents in 2026 are not autonomous bots. They combine four things: a knowledge base, controlled workflows, some ability to act in external systems, and a clean human handoff. Think of it as a service operations project with AI in the middle, not an AI project that happens to touch support. Make the AI boring before you make it ambitious.
Support stack
A reliable support agent has four layers
The model is only one layer. The operating design around it determines whether customers trust it.
Knowledge
Grounded
Answers should come from current help content, not the model memory.
Workflow
Controlled
Refunds, billing, routing, and policy exceptions need explicit rules.
Handoff
Clean
Escalate with transcript, classification, and a suggested next step.
Pick the channel, then build the agent
| Channel | Setup effort | Good for | Start here? |
|---|---|---|---|
| Website chat | Low. Embed install + knowledge source. | Instant answers, routing, scheduling. | Yes. Start here. |
| Email triage | Medium. Needs existing ticketing. | Classification, draft replies, routing. | Second, if email volume is high. |
| SMS | High. Business account, webhooks, compliance. | Customers who already live in messaging. | Only if customers use it already. |
| Phone automation | Highest. Telephony, STT/TTS, interruption handling. | High-touch, complex queries. | Last. Prove the logic in text first. |
SaaS tools with real pricing
For most small teams, SaaS wins on time to value. The useful part is the full operating layer around the AI reply: ticketing, routing, analytics, and handoff.
Intercom
$29/seat + $0.99/Fin outcomeAI-first support. Fin answers across chat, email, and phone. Deep workflow control. Outcome-based pricing feels elegant at low volume, expensive at scale if you let Fin touch everything.
Zendesk
From $19/agent/mo, AI add-ons via salesTicket-first, email-heavy, omnichannel. Strong if you already use Zendesk. Setup is more involved than the homepage suggests: optimize help center content first, then configure the AI layer.
Tidio Lyro
From $32.50/mo for 50 AI conversationsSMB-friendly, chat-first. Straightforward setup: paste URLs, add Q&A, set handoff rules. Best for repetitive top-of-funnel support. Not deep enough for complex multi-team operations.
Predictable workspace pricing, no per-seat fees. Hugo conversations average $0.05-$0.10 each. Strength is the AI Data Hub. Weakness: if you don't curate it, quality degrades fast.
Omnichannel with a dedicated Email AI Agent. 500 free AI sessions to test on Pro/Enterprise. More serious about AI than most buyers realize. Watch the session/pack billing complexity.
Setting up the knowledge base (the real product)
One article, one question
Long catch-all docs increase cost and reduce accuracy. Break them up. Each article answers one thing a customer asks.
Product docs separate from policy docs
"How does feature X work?" and "What is the refund policy?" need different sources, different update cadences, and different escalation behavior.
Mark ownership and freshness
Every article has an owner and a last-reviewed date. Stale sources are the #1 cause of bad answers. The AI isn't "making things up" when it gives a wrong answer. It's working off bad retrieval or outdated docs.
Add tools when docs aren't enough
Checking orders, resetting subscriptions, verifying identity: these need tool integrations, not more articles. Docs answer "how does this work?" Tools answer "what is the status of my specific thing?"
When to escalate to a human
Escalate immediately
- Refunds and billing disputes
- Security issues
- Legal or policy exceptions
- Outage reports
- Explicit frustration
AI can handle
- Product FAQs from the knowledge base
- Status checks (with tool access)
- Routing and classification
- Scheduling and simple confirmations
- One or two clarifying questions before handoff
Hand over with the transcript, classification, and a draft next step. Don't hide the "talk to a human" option. Don't auto-close before the customer confirms resolution.
What deflection rate should you expect?
| Vendor | Claim | What they measure |
|---|---|---|
| Crisp | 30-50% | Repetitive question deflection |
| Tidio Lyro | Up to 67% | Lyro use (first response, 15-min inactivity close) |
| Freshdesk | Up to 80% | Sessions (24-hour window) |
| Zendesk | 80%+ | Complex issue resolution |
| Intercom Fin | 80% | Outcomes (escalations not billed) |
These numbers use different definitions. You can't compare them directly.
Plan in stages. First: can the agent safely absorb repetitive questions without creating cleanup work? Second: add actions and better handoff. Third: chase higher numbers. The aggressive stats come after knowledge cleanup and workflow tuning, not before.
Should you build a custom support agent or buy SaaS?
Build custom when you need non-standard workflows, proprietary data access, or tool use across internal systems. For everything else, SaaS already solved ticketing, agent assignment, analytics, CSAT, channel connectors, and audit trails. Model pricing alone is a misleading way to compare.
If you do build custom, the strongest stacks right now:
- OpenAI Responses API + Agents SDK (Assistants API deprecated, shuts down Aug 2026). GPT-4o-mini at $0.75/$4.50 per MTok.
- Claude Agent SDK with MCP connections. Sonnet 4.6 at $3/$15 per MTok, Haiku at $1/$5.
- LangGraph for stateful workflows with human-in-the-loop. LangSmith Plus at $39/seat/mo.
- Rasa CALM for deterministic dialog with LLM flexibility. Free Developer Edition: 1 bot, 1,000 conversations/mo.
Mistakes everyone makes
Launching with messy docs
The knowledge base is the product. If the docs are bad, the agent is bad.
Automating high-risk flows first
Start with boring repetitive questions. Refunds and billing come later.
Hiding the human escape hatch
If people can't reach a human easily, they leave. Then they write a bad review.
Starting with phone automation
Phone automation is the hardest channel and the most fragile. Prove the logic in text first.
Skipping transcript review
You won't know what's breaking until you read real conversations.
Buying a channel because it feels modern
Deploy where customers already are, not where the demo looked cool.
Related
Explore by intent
Core product pagesLearn what localbot does and how it works.+-
Lead response use casesPages for the problems localbot is built to solve.+-
Guides with search demandStart with the pages already earning impressions.+-
Website builders and platformsInstall guides for common builders, WordPress, and AI-made sites.+-
ComparisonsUse these when you are choosing between tools.+-
Docs for AI agentsAgent-facing references for choosing and installing localbot.+-
Frequently asked questions
What is a customer support agent?
A system that combines a knowledge base, controlled workflows, tool access, and human handoff to handle customer support. In practice it is usually a chat widget, email triage bot, or messaging agent that answers common questions and escalates when it can't.
What deflection rate should I expect from an AI support agent?
Vendor claims range from 30% to 80%, but those numbers use different definitions (outcomes vs sessions vs conversations). Plan conservatively: if you can safely absorb the repetitive tier of support without creating more cleanup work, that is a win. Aggressive numbers come later, after knowledge cleanup and workflow tuning.
Which channel should I deploy a support agent on first?
Website chat. It is the easiest to constrain and the fastest to instrument. Then email triage if your volume is there. Phone automation last. Each channel adds complexity in setup, state management, and handoff design.
Should I build a custom support agent or use a SaaS tool?
Use SaaS for most small teams. Intercom, Zendesk, Tidio, and Freshdesk already solved ticketing, routing, analytics, and handoff. Build custom only when you need non-standard workflows, proprietary data access, or tool use across internal systems that SaaS can't reach.
How do I set up a knowledge base for a support agent?
Each article should answer one customer question. Keep product docs separate from policy docs. Mark ownership and freshness. Most AI failures come from bad retrieval, stale sources, or over-broad documents, not from the model being dumb.
When should a support agent escalate to a human?
Immediately for refunds, billing disputes, security issues, legal exceptions, outages, and explicit frustration. Let the AI ask one or two clarifying questions when that improves routing. Hand over with the transcript, classification, and a draft next step.