Chatwoot Cloud?

KINDAYou can build the valuable core, but the established product has meaningful operational complexity. Pick one narrow promise for v1.

BUILD FIRST

One specific customer type and one primary use case
A vertical slice that completes the main job without manual workarounds
Visible limits, review steps, and a fallback when an external dependency fails

LEAVE FOR LATER

Broad third-party integrations
High-scale collaboration, syncing, and permissions
Automation that can cause harm without human review

RESEARCH NOTES

What this tool actually does.

Checked 2026-09-06

Chatwoot Cloud is the managed SaaS version of Chatwoot, an open-source, AI-powered omnichannel customer support platform positioned as an Intercom/Zendesk alternative. It unifies live chat, email, WhatsApp, and social messages into a single shared inbox with automatic routing, assignment, and SLA-escalation rules. Built-in 'Captain AI' drafts replies, summarizes threads, and suggests knowledge-base responses. Includes customizable help center/knowledge base with AI search, unified contact profiles with custom attributes and segmentation, automation rules, canned responses, keyboard shortcuts, bulk actions, real-time dashboards, live view, 50+ languages, native integrations/APIs, role-based access, audit logs, SSO/SAML, and SOC 2 Type II compliance. Deployment choice: fully managed cloud (hosting, updates, security handled by vendor) or self-hosted via Docker/Kubernetes for complete data

SOURCES

RESEARCHED BUILD PROMPT

Give this to your coding agent.

Build a focused replacement for Chatwoot Cloud's core workflow: an omnichannel shared inbox web app where support agents handle customer conversations from email, a live chat widget, and a WhatsApp-style channel in one unified queue. Workflow: incoming messages create conversations assigned to inboxes; agents reply, use canned responses, assign/transfer to teams, add private notes, apply labels, and resolve when done; automated rules route or escalate; basic customer profiles accumulate conversation history; managers see live queue and per-agent resolution counts. User-facing requirements: inbox list with filters (status, assignee, inbox, label), split conversation pane with thread and reply composer, customer detail sidebar, canned-response picker, rule builder for auto-assignment/escalation, simple dashboard with open/conversations/resolution metrics, agent settings. Technical requirements: Node/TypeScript backend, React frontend, PostgreSQL with JSONB for contact attributes, WebSocket for live updates, message channel adapters abstracted behind a provider interface; seeded demo data for email and chat; role-based auth (admin/agent). Implementation approaches: Docker Compose for local dev, Socket.IO or SSE for real-time, S3-compatible storage for attachments, a small rule engine evaluating conversation/contact fields, Tailwind for original minimal UI. Do not copy Chatwoot's brand, logo, marketing copy, or exact visual design; do not reuse its open-source code. Explicit out-of-scope: no mobile apps, no native WhatsApp/Facebook API integration (simulate via adapter), no AI copilot, no help-center/knowledge-base authoring, no SLA timers, no multi-language i18n, no SOC 2/SSO/audit logs, no self-hosted distribution packaging. Deliver source plus README covering setup, seeded accounts, rule syntax, provider adapter interface, and known limitations (e.g., simulated channels only, no production security hardening).

Visit the official product page