Killed By Claude Report
← HomeCurrent verdict
Assessment
This is a real overlap case, but not an obituary.
Claude is marching toward agentic commerce, tool-using business agents, support plugins, and enterprise deployment infrastructure. That attacks the most generic part of Gorgias: AI answering customers, assisting reps, and handling routine workflows.
But Gorgias is still more than a model wrapper. It owns a purpose-built helpdesk surface, ecommerce-specific operational logic, and deep merchant context across 17,000 brands. Anthropic gives companies the engine to build pieces of this; Gorgias sells the finished machine.
So: meaningful blast radius, not instant substitution.
Biggest historical hit
The clearest shot across Gorgias's bow is "Claude is a space to think" (2026-04-11).
Anthropic explicitly says it wants to support commerce, including agentic commerce where Claude can help users find, compare, and buy products, connect with businesses, and complete transactions end to end.
That matters because Gorgias positions customer conversations as both support and sales. If Claude becomes a commerce-facing agent with tool access and business integrations, it starts eating into the conversational layer Gorgias uses to drive both ticket resolution and conversion.
What still protects them
Gorgias still has some actual defenses.
In short: Claude can power a rival or accelerate internal builds, but Gorgias still owns the application layer and merchant workflow packaging.
Signals
Why this is in the blast radius
Anthropic explicitly says Claude will support commerce and is interested in agentic commerce that can find, compare, buy, and connect with businesses. Gorgias sells conversational support plus commerce conversion for ecommerce brands, so this lands directly on its shopper-facing AI surface.
It does not replace Gorgias's helpdesk overnight, but it absolutely pressures the product recommendation, pre-purchase assistance, and automated conversation layer.
Opus 4.6 improves long-running agentic tasks, tool use, search, document handling, and autonomous work inside Cowork. Those capabilities are the raw ingredients for building support agents, agent-assist copilots, and back-office CX automations.
That threatens Gorgias on the intelligence substrate for ticket handling and agent productivity. It does not by itself replicate Gorgias's ecommerce workflows, UI, routing, or merchant-specific support operations.
This is less about a feature and more about distribution. A funded partner ecosystem makes it easier for agencies, integrators, and enterprise builders to assemble Claude-based customer support and commerce solutions.
That raises competitive pressure on Gorgias because merchants and larger retailers can buy custom or semi-custom Claude-powered CX stacks instead of defaulting to a vertical SaaS platform.
Support plugins are a direct signal. Gorgias depends on support workflows being specialized and sticky; Anthropic making support-oriented plugins easier to deploy lowers the cost of building internal support copilots and automations.
Still, plugins are components, not a full ecommerce helpdesk. So this is real overlap, but partial.
Rakuten is commerce-adjacent and the example shows Claude being used to stand up specialist business agents quickly. That is bad news for any vendor selling AI layers for commerce conversations, sales assistance, or customer operations.
However, the example is broader than customer support and does not show Anthropic owning the full agent desktop or omnichannel helpdesk that Gorgias provides.
This is useful enabling infrastructure, but only indirectly relevant. It helps developers build richer support workflows, yet it does not specifically address ecommerce support operations, ticket orchestration, or conversational commerce.
So yes, it contributes to Claude's general platform strength, but by itself it is not a major direct hit on Gorgias.