Overview
The operator defines how accounts share (or don't) auxiliary services. A central example is the WhatsApp Web gateway (ZuckZapGo), which hosts the paired sessions used by WhatsApp Web inboxes.
Prerequisites
- A provisioned gateway service reachable by the platform.
- The gateway admin token (kept backend-only, never exposed).
Step by step
- Define the tenancy model: a single gateway shared by the operator, or a gateway per account.
- Configure the gateway URL and admin token in the installation.
- When a WhatsApp Web inbox is created, the platform auto-provisions a user on the gateway.
- Monitor session state (connected, pairing, disconnected).
Settings & options
- Tenancy mode: shared (operator) or per-account.
- Credentials: admin token and gateway URL (encrypted/secured).
- Webhooks: the gateway notifies the platform about session and message events.
Use cases
- Operate a single gateway for all accounts (self-hosted).
- Let each account point to its own external gateway.
Tips, limits & best practices
- Never expose the gateway admin token in API responses or logs.
- Monitor gateway health and the validity of paired sessions.
Troubleshooting
- Inbox won't pair: check connectivity to the gateway and the token.
- Session drops often: check device/source stability and the webhooks.