Chatwoot vs Voiceflow
Side-by-side trajectory, velocity, and editorial themes.
Chatwoot's Captain grows tools, mobile reach, and translation as the AI-native helpdesk story tightens.
Chatwoot is shipping at a fast biweekly cadence and the through-line is Captain — its in-product AI layer. Captain now calls external tools mid-conversation, translates articles, lands on mobile via AI Assist, and gets a paired narrative move on the reader side with an 'Open in LLM' option on every help-center article. Around the AI surface, the team is also rebuilding operational primitives: capacity-aware Assignment Policies, a Participating view, an expanded chatlist, and webhook signing.
Chatwoot is positioning to be the AI-native open-source helpdesk: Captain is no longer a suggestion sidebar but a tool-calling agent the customer can talk to, and the documentation/help-center experience is being rebuilt to flow into external LLMs rather than fence them out. The operational work (policies, webhook signing, mobile parity) shores up the scale-up surface so the AI surface has room to grow without breaking what serves bigger teams.
Expect Captain tools to expand from one-off webhook calls into multi-step workflows, plus inbound LLM connectivity (an MCP server) to match the outbound 'Open in LLM' move. Mobile should keep closing the gap with web; Assignment Policies will likely grow skill-based routing on top of the new policy engine.
Voiceflow doubles down on agentic primitives — Shopify tools, fail paths, skip-turn behavior.
Voiceflow is filling in the missing primitives for production conversational agents — a one-click Shopify integration that unlocks live commerce data, native failure paths on Function and API steps, a skip-turn tool for natural conversational pacing, and Flux STT now spanning 10 languages. Evaluation and analytics surfaces are getting parallel polish: preview cards, default transcript properties, workflow usage in analytics.
The product is maturing from build-a-bot toward operate-an-agent-stack-in-production. Recent shipping reads as a checklist of what serious teams need: error semantics, integration depth (Shopify, MCP), behavioral nuance (skip-turn), and observability at the workflow level. Global tools and Shopify together suggest Voiceflow wants the agent to act on real systems out of the box.
Expect deeper vertical-pack integrations beyond Shopify (likely Salesforce, Zendesk, or scheduling platforms), and expect the failure-path primitive to extend into agent-level retry policies. Multilingual Flux looks like the start of broader voice-native localization tooling.
See more alternatives to Chatwoot →
See more alternatives to Voiceflow →