A channel carried by your inbox
0seat does not connect to WhatsApp: it reads your instance’s WhatsApp channel, like any other inbox.
Your inbox’s WhatsApp channel gets the same prepared replies as the others. Autopilot is refused outright outside the official WhatsApp Business API: never on an unofficial connector.
0seat does not connect to WhatsApp: it reads your instance’s WhatsApp channel, like any other inbox.
Same path as e-mail or chat: approved base, sources, enforced handoff.
The server refuses autopilot outright on a WhatsApp channel that is not the official API, and on any inbox whose name says so.
With WHMCS connected, the customer’s account is found from the contact’s e-mail address; without a known address, the draft is written without account data.
Through the official API, in your instance. 0seat is not involved at this step.
The channel appears as an inbox of the space, with its mode.
Off to begin with: switch the channel to draft mode. Autopilot is refused outright outside the official API.
Because a number that answers on its own through an unofficial connector risks being banned, and because those connectors do not guarantee delivery. In draft mode, an agent sends from the usual tool.
They are short and concrete, as for the other channels. The agent adapts them before sending.
The draft is written without account data, and topics that require the account go to a human.
Connect an inbox, approve the suggested knowledge base, and get your first prepared replies.