The shared inbox is the thing I have open on a second monitor from the moment I sit down. Every channel we run funnels into one list: the website chat widget, support email, a WhatsApp number, a Telegram bot, and the Instagram and Facebook DMs that the marketing side fields. Before this, each of those lived in its own app with its own login, and a customer who started on chat and replied by email turned into two disconnected threads that nobody owned. Chatwoot keeps the whole exchange as a single conversation. The detail that earns the most goodwill is conversation continuity. When someone leaves an email address in the chat widget and then closes the tab, my reply goes out as an email under the agent's name, and when they answer it lands back in the same thread instead of opening a fresh ticket. That one behavior removed an entire category of "where did this conversation go" confusion that used to eat a few minutes of every shift.
Self-hosting under the MIT license is the reason the tool is here at all, and it is worth being plain about why. The community edition runs on our own infrastructure with no seat cap, so adding a fourth or a fifth agent does not move what we pay. For a small support team that grows in fits and starts, that changes the whole calculation. We are paying for a server we already understand how to run rather than a line item that scales with headcount. The codebase being source-available matters in a quieter way too. When something behaves oddly I can read the actual code path instead of filing a ticket and waiting, and that has saved me more than once when a webhook was not firing the way I expected.
Internal collaboration is handled the way I wish more tools handled it. Private notes and @mentions let me pull a teammate into a thread without the customer ever seeing it, so a tricky billing question gets a second opinion inline rather than copied into Slack and back. Conversation labels are how we impose our own structure on the queue, tagging threads by product area or by whether they need engineering, and the auto assignment quietly hands new conversations to whoever has capacity instead of letting them pile up unowned. None of these are headline features. They are the small machinery that decides whether a busy queue stays sane, and Chatwoot got them right.
Canned responses are unglamorous and I use them constantly. We have a couple of dozen saved replies for the questions that come in every single day, and being able to drop one in and edit a line before sending is the difference between a two minute reply and a thirty second one. The chat widget SDK is in the same bucket of dependable rather than exciting. We pass in the logged-in user's details so an agent opens a conversation already knowing who they are talking to and what plan they are on, which means we are not asking people to repeat account information they already gave us at signup.
The API and webhooks are more capable than I expected from an open-source project, and they are where Chatwoot stopped being a support inbox and started being part of our stack. We fire webhooks on conversation events into our own internal tooling, and we push data the other way through the API to create contacts and attach custom attributes from our database. The custom attributes piece is the part I lean on most, because it lets me store the things our team actually needs to see on a contact, the account ID and the subscription state, rather than whatever a generic CRM decided was important. It took longer than I would like to admit to wire all of this up, honestly, but once it was in place it has run without me thinking about it.
Captain, the AI layer, I will give qualified credit to rather than a rave. The co-pilot that drafts replies and translates messages for agents is the part that has actually changed how a shift feels, because it gets a draft onto the screen that I edit down rather than starting from a blank box, and the translation has let us answer a few non-English customers we would otherwise have fumbled. The assistant that handles first-line questions off our help center is solid for the repetitive stuff and noticeably weaker on anything with nuance, which is roughly where I expected a feature this young to land. It is closing the gap with the more established AI agents in this space rather than matching them, and for what we pay that trade is fine.
The last thing worth naming is that the entry tier does not nickel and dime you on channels. Every messaging channel we care about, including WhatsApp and the social inboxes, is available without being pushed up into an expensive plan, which is the opposite of how most tools in this category gate things. Combined with pricing that is published in plain numbers rather than hidden behind a sales call, it makes the cost easy to reason about, and for a team that watches its software spend that predictability is its own feature. Review collected by and hosted on G2.com.
SAML SSO only on Enterpise plan - Dedicated account manager only for subscriptions with 20+ agents Review collected by and hosted on G2.com.