Guides and glossary
Four guides written from the console as it exists, step by step, and a glossary of the words we use. Each guide also says what 0seat doesn’t do yet.
Connect your inbox
Administrator token, account ID, connection test, card, then per-inbox modes: the console’s actual steps, in order.
Review your knowledge base
Where entries come from, which order to work in, what approve, reject, merge and back to review do. Nothing is used before your approval.
Turn on autopilot for an inbox
What the server refuses outright, how 0seat measures each category, and how to open autopilot or force it on an inbox.
Create a read-only WHMCS API role
The exact ten actions 0seat uses, the role to create in WHMCS, the credentials, then the test from the console. No write action.
Glossary
RAG, similarity threshold, private note, handoff, approved base, cost per call, retention, space: the words 0seat uses, defined in a sentence or two.
Frequently asked questions
Do the guides match the current console?
Yes. Every step is taken from the console screens and the code behind them, and every guide carries its update date. When the console changes, the guide changes.
Which guide should we start with?
“Connect your inbox”, then “Review your knowledge base”. The other two matter once the first drafts arrive.
Where do we ask a question the guides don’t cover?
Through the contact form or the site chat. Recurring questions make their way into the guides.
Your team stays in charge. 0seat does the groundwork.
Connect an inbox, approve the suggested knowledge base, and get your first prepared replies.