Where these 14 reports land
Build it0
Scope it10
Keep it4
Category report
Customer Support
14 products ranked by how much of their useful core an AI coding agent can reproduce: 0 strong builds, 10 scoped builds, and 4 weak replacements.
How the score breaks down here
- Interface
- 44
- Core workflow
- 43
- Data access
- 43
- Operations
- 18
- Trust & safety
- 43
43/100 average buildability
Why people keep paying here
- scale infra14 of 14 reports
Reliability at the vendor's scale is an operations problem, not a prompt.
- integrations13 of 14 reports
Connectors, OAuth flows, and vendor API changes require constant upkeep.
- execution polish9 of 14 reports
The last 20 percent is sync, migration fidelity, speed, and edge cases.
The typical achievable core in this category: triage a shared inbox, draft replies from stored context, and track resolution state.
Scope it
Eloqra
The first half is a one-sitting build and the second half isn't. A script tag that injects a chat panel, a websocket, and a bot that forwards messages so your native Telegram reply reaches the visitor · that works by dinner, and the prompt below builds it. The gap is the operator side. Replying inside a bot chat is fine for one conversation a week; the moment you have several going you want a real inbox, and in Telegram that means a Mini App, which is a second application with its own platform rules: auth is HMAC-validating initData against your bot token, the webview lies about its own height so you size from viewportStableHeight instead of dvh, fullscreen hides content under the status bar until you combine two different safe-area insets, and it disables text selection outright, so even copying a message means hand-rolling a long-press with a clipboard fallback. None of that is hard. All of it is discovered the slow way, on a phone, after the prompt has finished.
Scope it
Chatwoot Cloud
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Chatwoot Cloud, use a managed shared inbox and website widget instead of operating Chatwoot yourself. The hard boundary is managed upgrades, backups, delivery infrastructure, support, and integrations, plus channel integrations and support operations.
Scope it
Crisp
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Crisp, combine website chat and a shared inbox for one small support team. The hard boundary is multi-channel inbox, chat delivery, knowledge base, campaigns, and workspace pricing, plus channel integrations and support operations.
Scope it
LiveChat
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For LiveChat, provide reliable website chat with routing, transcripts, and canned replies. The hard boundary is global chat delivery, mobile apps, staffing tools, integrations, and support, plus channel integrations and support operations.
Scope it
Chatbase
A useful web version is a serious build, not magic: crawl or upload sources, retrieve tenant-scoped passages, stream cited answers, run one guarded business action, and hand uncertain requests to a person. Rebuilding Chatbase itself is a different project. Its paid surface combines source management and retraining, procedures and custom UI actions, a polished widget, helpdesk, identity, analytics, voice, email, social and CRM channels, plus the reliability and security work that keeps an agent safe in front of customers.
Scope it
Help Scout
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Help Scout, manage a shared email inbox and compact help center for a small team. The hard boundary is email threading, customer context, docs, workflows, reporting, and support polish, plus channel integrations and support operations.
Scope it
Freshdesk
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Freshdesk, manage tickets from email and a web form with priorities, owners, and a help center. The hard boundary is omnichannel features, automations, marketplace, reporting, and freshworks ecosystem, plus channel integrations and support operations.
Scope it
MagicChat
A retrieval chatbot over your own docs is one of the most one-shottable products there is: crawl the site, chunk and embed it, answer from the top matches with an LLM, drop in a widget. What you don't get for free is the boring operational layer, scheduled re-crawls, analytics, lead capture and human handoff, multi-source connectors, and a hosted widget that stays up. Buildable in a focused implementation, real gaps after that.
Scope it
Tidio
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Tidio, run website chat, canned replies, and a simple support inbox. The hard boundary is hosted chat network, bots, ai agent, email, analytics, and ecommerce integrations, plus channel integrations and support operations.
Scope it
Groove
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Groove, turn one support mailbox into an assigned team inbox with a knowledge base. The hard boundary is email reliability, reporting, rules, integrations, and mature simplicity, plus channel integrations and support operations.
Keep it
Intercom
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Intercom, run a small website inbox and knowledge base without recreating Intercom's AI or channel network. The hard boundary is messaging infrastructure, ai resolution, product tours, integrations, and enterprise operations, plus channel integrations and support operations.
Keep it
Zendesk
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Zendesk, operate a small email and web support inbox with tickets and an audit trail. The hard boundary is omnichannel routing, marketplace, workforce tools, reporting, compliance, and support, plus channel integrations and support operations.
Keep it
Front
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Front, operate a shared mailbox with assignments, comments, and simple rules. The hard boundary is email infrastructure, many channels, workflow automation, crm context, and enterprise governance, plus channel integrations and support operations.
Keep it
Gorgias
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For Gorgias, build a small ecommerce support inbox from email and store webhooks. The hard boundary is deep commerce integrations, order actions, automation, ai, and high-volume support operations, plus channel integrations and support operations.