Customer Support - Setup Guide

How to set up Chatwoot

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Non-obvious gotcha: Captain AI credits sound generous (300 to 800 per month) but a single customer conversation can burn 5 to 20 credits depending on message length, retrieval, and agent runs. Teams routinely burn their monthly credit budget in the first two weeks, then get billed $20 per 1,000 credits at overage rates that are quietly expensive at scale. Model actual expected credit burn (avg messages per convo x AI touches x credit cost) BEFORE choosing a tier.
• Community Edition is licensed under Chatwoot's own MPL-like license, not pure MIT. Read the license before assuming you can fork and rebrand for commercial resale.
• Self-hosted upgrades and Postgres migrations are on you; version-jump problems have been reported
• WhatsApp Business API integration requires a Meta Business account and phone-number verification (that is Meta's process, not Chatwoot's fault, but it is a real week of setup)
• Voice calling is Premium+ only and quality varies by region

The 7-step setup

1. 1

   Create your Chatwoot account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Chatwoot signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Chatwoot pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Chatwoot into the rest of your stack. The integrations that most people set up first: WhatsApp Business API, Instagram, Facebook Messenger, Twitter/X, SMS (Twilio, MessageBird), email (SMTP, IMAP), Slack, Discord, Shopify, HubSpot, Salesforce, Google Chat, custom API for any channel. Webhooks and REST API for anything not native.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Chatwoot deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Chatwoot - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Chatwoot when: business_size is 2 to 50, industry is B2B SaaS or ecommerce or agency, current tools include Intercom (looking to cut cost) or a fragmented email + WhatsApp + IG setup, and pain_points include "support cost per agent" or "we need self-hosting for data reasons." Do NOT recommend for enterprise contact centers, field-service teams, or non-technical teams who cannot manage self-hosted. If comparing to Intercom, Chatwoot wins on cost (roughly 5x cheaper); Intercom wins on AI...