Connect your inbox to 0seat
What to prepare, the three steps of the creation wizard, payment, then inbox settings. You declare no webhook: 0seat creates its own agent bot in your instance.
Before you start
You need a 0seat account (sign-in by e-mailed code or Google, no password), administrator access to your Chatwoot instance and a payment card: it is requested before the first space, with no free trial.
From your instance, two pieces of information: the access token of an administrator (Profile, then “Access token”) and the account ID, that is the number after “/accounts/” in the application’s address. The token must belong to an administrator: 0seat uses it to create the agent bot and connect it, which an ordinary agent cannot do.
Create the space in three steps
In the console, open “Spaces” then “New space”. The wizard has three steps: the space’s identity, the connection, the assistant’s profile.
- Identity: a name (for example “Customer support”) and an identifier in lowercase letters, digits and hyphens. The identifier is part of the webhook address and cannot change afterwards.
- Connection: your instance’s address, the account ID and the administrator token. Click “Test the connection”: the console confirms the number of inboxes found. Without a successful test, the next step stays closed. The token is encrypted on save and will never be shown again.
- Profile: the “Web host (WHMCS)” or “Generic” template, which sets the base’s categories; the brand the assistant gives your company; a sentence about your business; the knowledge base language.
- “Create the space”: the console creates the space and opens payment; the preparation of its database and the connection follow its confirmation.
Payment, then connection
Payment comes before preparation: a space whose payment is not confirmed stays awaiting payment, and the console offers “Pay and activate”. Payment goes through Stripe. Once confirmed, 0seat prepares the space’s own database, then creates the agent bot in your instance and registers its webhook address there, which carries the space identifier and a secret.
If a step fails (instance unreachable, token revoked), the space stays in a consistent state and the console shows the remaining step with a “Resume setup” button. Nothing has to be redone from the start.
Set up the inboxes
Once the space is connected, the “Inboxes” section lists the account’s inboxes. Each inbox has a kind (standard, payments, unofficial WhatsApp) and a mode. A kind detected from your instance cannot be changed: an inbox whose name mentions payment or billing is a payments inbox, a WhatsApp channel outside the official API is flagged as such.
The default mode is “Off”: 0seat leaves the inbox alone. Switch to “Draft (private note)” the inboxes where you want proposed replies. The “Automatic” mode sends replies directly, in the categories that pass the measurement; the server refuses it outright on payments inboxes, on unofficial WhatsApp and, when WHMCS is active, until visitor identity is verified by the widget.
What happens next
The history backfill starts in batches as soon as the space is served, outside the nightly window. Extraction of resolved conversations then runs every night, in the space’s window (by default from two to six in the morning, in the space’s time zone). You can trigger either one from “Health”, with the “Run now” button.
The first entries land in the knowledge base as candidates. Nothing is used before your approval: that is the subject of the next guide. Drafts begin as soon as approved entries exist and an inbox is in draft mode.
To replace the administrator token later, or to rotate the webhook secret, the space page has a section for each: the new token is tested before being saved, and a new secret reconnects the same bot.