The same questions, every day
DNS propagation, SPF and DKIM records, renewals, nameserver changes: known answers, retyped every time, with technical values that drift from one agent to the next.
Most questions from a hosting customer are about their own account: a suspended service, an expiring domain, a pending invoice, a migration to schedule. 0seat reads this information in WHMCS, read-only, so the draft speaks to their actual situation. An agent reviews and sends.
DNS propagation, SPF and DKIM records, renewals, nameserver changes: known answers, retyped every time, with technical values that drift from one agent to the next.
Before answering, the agent opens WHMCS, finds the customer, checks the service, the expiry date and the invoice. Two minutes per conversation before writing a word.
The customer sends a screenshot of their panel or of an error message rather than describing the problem. The agent reads it, transcribes it, then searches.
The customer’s services, domains, invoices and orders are read in WHMCS at drafting time and summarised in the agent’s private note. The draft quotes the real expiry date, not a template.
Every night, resolved conversations produce question-and-answer entries. Nothing is used before an agent approves it: the wrong DNS values from old replies stop at review.
An image sent by the customer is read and taken into account in the draft, when attachment reading is enabled on the space.
Quoted prices come from your WHMCS catalogue, re-read every twelve hours, not from a page copied into the base and soon out of date.
0seat finds the WHMCS account from the contact’s e-mail address; with duplicates, no account is kept. Without a known address, the draft is written without account data.
Calls to WHMCS carry an identifiable user agent and are spaced out: no burst that would get the address banned by an application firewall.
No. Access to WHMCS goes through the official API with a closed list of read actions. No writes, and money always goes to an agent.
No. You create a read-only API role and dedicated credentials; 0seat calls the official API. No third-party module, no encoded code on your server.
Services, domains, invoices, orders and ticket subjects. Password, postal address and phone fields are stripped in code before any model call.
No. The e-mail address stated in the conversation proves nothing; that is why the agent reviews the drafts, and why autopilot is refused on a WHMCS space until visitor identity is verified by the widget.
It stays in draft mode: the server refuses autopilot on a payments inbox, whether declared or detected from its name. The page “For the billing team” explains how this works.
Connect an inbox, approve the suggested knowledge base, and get your first prepared replies.
Services, domains, invoices and orders read through a closed list of API actions. Minimal role, sensitive fields filtered, account summary by e-mail.
Images sent by the customer are described by the model and taken into account in the draft. Enabled per space; PDFs are never read.
Renewals, transfers, expiry dates, invoices: read in WHMCS at drafting time. The draft talks about the customer’s domain, not a generic case.