TL;DR

Verdict: Hybrid (buy for routing/knowledge + build AI agent layer). If you have a support queue larger than 50 tickets/day, buy a mature ticketing system (Zendesk, Kustomer, or self-host Chatwoot); wire Claude or OpenAI agents on top via API to automate triage, first-response, and escalation. Pure OSS is viable for <20 people teams; vendors dominate at scale.

---

What "build" looks like for this category in 2026

In 2026, "building" an AI customer support agent is not forking Chatwoot or running Zammad on a server you manage. It's composing three layers:

1. Ticketing backbone: Either buy (Zendesk, Kustomer) or self-host an open-source ticket system (Chatwoot, Zammad, FreeScout). This handles queue, routing, SLA, and audit trails—things you don't want to rewrite.

2. AI agent layer: Claude Agent SDK or OpenAI Agents connected to your tickets via REST API. ~200-400 lines of Python orchestrate triage rules, knowledge retrieval (via your own vector DB or RAG), and escalation logic.

3. Integration plumbing: n8n or Make workflows to sync customer data (CRM, billing, product usage) into agent context. MCP servers let you connect Claude directly to Slack, Postgres, or custom APIs.

The honest path: you are not building a customer support platform. You are building a thin automation layer that runs on top of existing infrastructure (bought or self-hosted). If you try to build the ticketing layer from scratch, you will fail—Chatwoot took 6+ years to reach feature parity with Zendesk.

---

OSS alternatives

• Chatwoot (28,985★, MIT-style): Live chat, email, omni-channel ticketing. Explicit Intercom alternative. Suitable for self-hosting at <50 team members. https://github.com/chatwoot/chatwoot
• Zammad (5,572★, AGPL-3.0): Web-based helpdesk with multi-channel support. Lighter footprint than Chatwoot; better for internal IT/HR support. https://github.com/zammad/zammad
• FreeScout (4,230★, AGPL-3.0): Help desk and shared mailbox. Minimal feature set; backup option for teams rejecting Zendesk SaaS. https://github.com/freescout-help-desk/freescout

No open-source AI agent exists for customer support. Chaskiq (3,517★) is an old Intercom clone that ships no AI. The AI layer must be wired separately via commercial agent SDKs.

---

Build with agent platforms

Claude Agent SDK (~$20–$500/mo, typically $150/mo for 5k–10k tickets/month): Wire Claude to your Zendesk or Chatwoot API. Use MCP servers to read tickets, fetch customer history from your CRM, and generate first responses. ~300 lines of Python + prompt engineering. Cost scales on input tokens; a $50k/year SaaS with 200 support requests/week runs ~$120–$200/mo in API calls. Fastest to first-agent-in-production (1–2 weeks).

OpenAI Agents SDK (~$20–$500/mo, token-based pricing): Functionally equivalent to Claude; slight cost difference depending on ticket volume and context window needs. GPT-4o is cheaper per token but requires more aggressive pruning of conversation history. Choose this if your team is GPT-native.

n8n ($0–$50/mo self-hosted, visual builder): Lower code bar for ops teams. Build workflows: Zendesk webhook → LLM node (Claude/OpenAI) → Slack alert if escalation needed. Not suitable alone (n8n is orchestration, not a full agent); pair it with Claude Agent SDK as the "brain" and n8n as the plumbing. Good for teams that want no custom Python.

---

Buy market

• Zendesk AI (AI Visibility: Medium, API-accessible): $140–$199/agent/month; includes AI-generated summaries, suggested replies, and ticket classification. Market-leading; used by 15k+ support orgs. Mature Series B+ vendor (IPO 2020).

• Kustomer (AI Visibility: Medium, API-accessible): ~$40–$99/user/month for core + $5k–$15k/month for AI add-ons. Emphasis on CRM integration; AI is bolted on. Series B+ (acquired by RingCentral, 2021).

• Sierra (AI Visibility: Medium, API-accessible): AI-native competitor to Zendesk; ~$5k–$20k/month for multi-channel agents. Younger vendor (Series B funding); no public SLA/reliability data yet.

• Forethought (AI Visibility: Medium): Purpose-built AI triage and resolution. ~$10k–$30k/month. Integrates with Zendesk/Intercom/Freshdesk. Early-stage (Series A/B).

• Yellow.ai (AI Visibility: Low, Series C, $102M): Platform for building conversational agents; ~$3k–$10k/month. Heavy enterprise sales; weak brand in US SMB.

Typical price band: $2k–$5k/month for teams under 100k support volume; $15k–$50k/month for large-scale deployments. Market dominated by Zendesk (Series B+ maturity); newer entrants (Forethought, Sierra) are unproven at scale.

---

Verdict

Build on top of Chatwoot if you have < 15 people and want zero vendor lock-in; buy Zendesk if you have a dedicated support org or need enterprise SLA. Mid-market teams (20–100 people) should self-host Chatwoot + wire Claude Agent SDK for first-response triage. Cost: $200/month (Chatwoot infra) + $150/month (Claude API for 10k tickets/month) = $350/month total, vs. $3k–$5k/month for Zendesk + Forethought.

The inflection point is ~50 support staff or >500 tickets/day. Beyond that, Zendesk's multi-queue, knowledge base, and AI features become cheaper than the engineering time to maintain self-hosted Chatwoot and custom agent glue. At 100+ support agents, Zendesk Enterprise ($199/agent + add-ons) is non-negotiable—the compliance, audit, and SLA machinery alone justifies the cost.

Do not attempt to build a ticketing system from scratch. Do build the AI agent layer (everyone should; it takes 2–4 weeks). Separate the two.