Verify before you commit
Use this page to sanity-check Chatwoot quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.
Evidence
Assessed
Docs reviewed · Mar 20, 2026
Freshness
Updated 2026-03-20T20:37:29.659173+00:00
Mar 20, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 7.2 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 6.7 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 7.0 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
Docs-backed Built from public docs and product materials.
Test-backed Backed by guided testing or evaluator-run checks.
Runtime-verified Verified from authenticated runtime evidence.
The API covers conversations, messages, contacts, agents, teams, labels, and canned responses. The conversation management surface covers the full support lifecycle — creating conversations, sending messages, assigning agents, updating status, and labeling for categorization. The automation rules engine handles some routing logic internally; agents can supplement with more complex logic through the API.
Reliability for self-hosted Chatwoot is the team's operational responsibility. Chatwoot Cloud provides managed reliability for teams that prefer vendor-managed infrastructure. The platform has a growing community and active development that has improved reliability over its early versions. Teams building production customer support automation on self-hosted Chatwoot should implement appropriate monitoring and backup.
Chatwoot is an open-source customer support and engagement platform, positioned as a self-hostable alternative to Intercom and Zendesk. It covers shared inbox, live chat, email, and social channel support with an API for automation. For agents in customer support contexts where data privacy or vendor independence drives infrastructure choices, Chatwoot provides comparable automation capabilities to commercial platforms on self-controlled infrastructure.
Authentication uses API access tokens at the user level. Self-hosted deployments manage their own auth infrastructure. The token model is straightforward for server-side automation. Teams should create dedicated agent accounts in Chatwoot for automation rather than using individual support agent credentials.
Documentation covers the REST API adequately. The API reference documents available endpoints and parameters. Teams familiar with other customer support API patterns will find Chatwoot's concepts recognizable. Being open-source, teams can supplement official documentation with source code exploration when documentation gaps arise.
Trust shortcuts
This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.
Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.
Overall tier
7.0 / 10.0
No alternatives captured yet.