Deploying and running open-source business tools on your own infrastructure — Chatwoot, automation platforms, and the operational work that keeps them healthy.
Comparing monthly prices is the wrong comparison – the three options charge for different things. Per seat, per outcome, or infrastructure plus ownership, and how to model your own numbers.
Reply freely for 24 hours after a customer messages you; after that, approved templates only. It is the rule that quietly invalidates support plans built around following up tomorrow.
Connecting your WhatsApp number through a technology provider is one button and a few screens. You keep the account, Meta bills you directly, and three things are worth having ready first.
Buy a new business SIM from a real carrier and register that. The only real trap is the number your customers already message – registering it deletes its WhatsApp history permanently.
A template can pass review and still damage your account, because review judges the wording while your quality rating judges the reaction. What counts as opt-in, where to collect it, and what to store.
Running Chatwoot for several clients forces a choice between one shared account and an account per client. One of them stops working as you grow, and migrating out of it is painful.
Three products share the name. The free app is enough more often than vendors admit – and the API gives you no inbox at all. A plain comparison, plus the number migration that has no undo.
Template rejection is what usually misses the launch date. Six causes account for almost all of them, and the category mismatch is the one people fix last.
Self-hosting Chatwoot is cheaper, but not free – it trades a subscription for infrastructure plus your own time. Four reasons it holds up, three reasons to stay hosted.
Connecting WhatsApp to Chatwoot takes an afternoon. Choosing whose account the traffic runs under decides whether you ship. A comparison of the three paths, and the three things that actually hold up launches.
