Killed By Claude Report
← HomeCurrent verdict
Assessment
Tidio is in a very real blast radius because Anthropic is moving beyond being just a model provider and toward being an agent platform that can operate tools, integrate with business software, and support commerce workflows.
That said, Claude does not equal Tidio out of the box today. Tidio still bundles channel UI, help desk workflow, ecommerce integrations, deployment polish, and SMB-friendly packaging. Anthropic threatens the intelligence layer and increasingly the orchestration layer, but not the whole packaged support product.
So: not dead, but absolutely exposed. If buyers decide they want Claude-native support agents plugged into their existing stack, Tidio gets squeezed hard.
Biggest historical hit
The clearest hit is Anthropic's acquisition of Vercept to advance Claude's computer use capabilities.
That matters because customer support automation is no longer limited to answering FAQs. With computer use, Claude can potentially:
- operate backend tools,
- navigate support consoles,
- complete multi-step service tasks, and
- act across live applications the way a support agent does.
That pushes Claude closer to the actual workflow layer Tidio is selling, not just the language model underneath it.
What still protects them
Tidio still has some real insulation.
But let's not romanticize it: most of this is execution moat, not deep technical moat. If Claude-powered vendors or platforms package support well enough, that protection erodes fast.
Signals
Why this is in the blast radius
This lands squarely in Tidio's territory.
Tidio sells automation for support conversations and related service actions. Vercept-style computer use means Claude can move from merely drafting replies to actually operating support workflows inside live apps.
That makes Claude a more credible substitute for the agentic layer Tidio monetizes.
The commerce signal is direct.
Anthropic explicitly says Claude will support agentic commerce, help users connect with businesses, and expand integrations with third-party tools. Tidio is built around support and sales conversations for ecommerce brands.
If Claude becomes a user-facing commerce and business interaction layer, that overlaps with Tidio's chat-led conversion and service workflows.
This is a go-to-market threat more than a pure feature threat.
Tidio wins partly by packaging AI support for businesses. Anthropic funding partners to implement Claude for enterprises increases the odds that agencies, integrators, and software vendors deliver Claude-native support solutions without Tidio in the loop.
It does not replace Tidio directly by itself, but it expands the ecosystem attacking the same budget.
Support is explicitly named.
Tidio's product depends on being the place where support conversations and automations happen. Open plugins for support lower the barrier for Claude-based workflows to plug into business systems and perform customer-service tasks.
This does not recreate Tidio's full UI and help desk product, but it chips away at the need for a separate dedicated support AI layer.
This is mostly an indirect threat.
A stronger general model helps any support agent become better at reasoning, context handling, and response quality, which matters to Tidio's Lyro positioning.
But the evidence here is centered on cybersecurity and platform controls, not a customer support product release. So it raises baseline competitive pressure without being a direct category strike.