Chatwoot is a Ruby-based, open-source, self-hosted customer support platform that consolidates live chat, email, and social messaging into one omnichannel inbox, positioned as an open alternative to Intercom, Twilio, Zendesk, and Salesforce Service Cloud.

What it is

Chatwoot is the modern, open-source, self-hosted customer support platform, built for scale and flexibility. It gives businesses full control over their customer data while providing tools to manage conversations across channels: live chat on a website, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line, and SMS. It ships with Captain, Chatwoot's AI agent for support, which answers common queries automatically so that agents can concentrate on complex conversations.

The concrete problem it solves is ownership of the support stack. Teams that would otherwise run Intercom, Twilio, Zendesk, or Salesforce Service Cloud must hand customer conversation data to a vendor and accept that vendor's pricing and roadmap. Chatwoot replaces that SaaS support desk with software the operator hosts and controls, keeping the inbox, automation, help content, and reporting on infrastructure the operator owns. The project lives in the Ruby ecosystem, and its topic list names ActionCable for realtime delivery, a chat widget, a dashboard, JavaScript, Docker and Docker images, and Heroku as a deployment target.

Key capabilities

• A single omnichannel inbox that centralizes live chat, email, Facebook, Instagram, Twitter, WhatsApp, Telegram, Line, and SMS conversations.
• Captain, the built-in AI agent that automates responses to common queries and reduces agent workload.
• A Help Center Portal for publishing help articles, FAQs, and guides so customers can self-serve.
• Collaboration tooling including private notes, @mentions, labels, canned responses, keyboard shortcuts, a Command Bar, auto-assignment, business hours and auto-responders, and agent capacity management.
• Contact management with profiles, interaction history, segments, notes, campaigns, custom attributes, and pre-chat forms.
• Integrations with Slack, Dialogflow, Dashboard Apps, Shopify, Google Translate, and Linear tickets.
• Reporting that includes Live View, conversation, agent, inbox, label and team reports, CSAT reports, and downloadable reports.

Who uses it and how

• Support teams that consolidate website live chat, email, and messaging channels such as WhatsApp, Telegram, Line, and SMS into one inbox rather than several tools.
• Teams that keep conversations inside Slack using the Slack integration, and teams that resolve Shopify order questions without leaving the support desk.
• Multi-lingual support organizations using multi-lingual support and Google Translate for realtime translation of incoming customer messages.
• Small teams that deploy through the Heroku one-click button, and operators who prefer a Docker or Docker image based self-hosted install.
• Support managers who need operational visibility through Live View, CSAT, and downloadable reports.

Getting started

The README documents Heroku one-click deploy through a template button, followed by configuration of the environment variables described at chatwoot.com/docs/environment-variables. Detailed documentation lives at chatwoot.com/help-center, and repository topics also list docker and docker-image for self-hosted installs.

How it compares

Against Intercom, Twilio, Zendesk, and Salesforce Service Cloud, Chatwoot is the open-source, self-hosted option: the operator runs the software and retains control of customer data rather than renting a closed platform. That changes the cost model from per-seat or per-conversation vendor pricing to infrastructure and operational effort the team absorbs itself. The trade is that licensing terms, upgrades, and uptime become the operator's responsibility instead of the vendor's.

When to use it — and when not to

A self-hoster must set the environment variables correctly, and the README itself warns that breakages can occur when they are wrong; stable deployments should use master or v1.x.x tags rather than the develop branch, which is the git-flow base branch. The repository reports a NOASSERTION licence, so the exact terms need checking in the repository before commercial use, and a large open issue count means self-hosters should expect to track upstream fixes. Teams that want a fully managed service with vendor support, or that require a clearly stated standard open-source licence, should look elsewhere first.