Docs
Get started

Day-to-day work happens inside a sub-account

Sub-accounts are isolated workspaces under your admin panel. One sub-account per client, or per team, or per use case. Everything that touches a specific WhatsApp number lives here: pairing, agents, integrations, anti-ban rules.

Overview

Think of a sub-account as a single company's instance of Wazzap. It has its own WhatsApp lines, its own agent roster, its own CRM connection, its own Spintax pool. Nothing leaks between sub-accounts unless you wire it that way at the admin level.

The admin panel creates and quotas these workspaces. The sub-account panel is where you actually scan QRs, write messages, hook integrations, and manage day-to-day operations.

If you only have one business and one team, you'll likely live entirely in one sub-account. Agencies use one sub-account per client to keep data, billing visibility and access clean.

Accessing a sub-account

  1. From the admin panel, click the sub-account name in your workspace list.
  2. Or use the sub-account's dedicated login URL (if you've shared it with a client who shouldn't see other sub-accounts).
  3. Either way, you land on the sub-account dashboard with that sub-account's numbers, conversations, and settings.

Manage WhatsApp numbers

The number tiles on the dashboard are where pairing happens. Each tile shows the number's current state and quick actions.

  • Connect a number: click the empty tile, scan the QR with WhatsApp on your phone (Settings → Linked Devices → Link a Device). The tile flips to Online in seconds.
  • Disconnect a number: stops Wazzap from acting as the linked device. Useful when transferring a line to a new sub-account or retiring it.
  • Re-scan: when a number falls offline (for example, the phone went offline for 14+ days), the tile shows a fresh QR to re-pair.
  • Number warming: new lines need ramp-up before bulk activity. Follow the warming process.
  • Banned numbers: if Meta banned the line, Wazzap shows it offline. Recovery is outside our reach, see reconnect after a ban.
Sub-account "Acme Sales"
├── Number 1: +52 55 ••••• 4422  (Online,  2 agents)
├── Number 2: +52 55 ••••• 5511  (Online,  1 agent)
└── Number 3: empty slot           (waiting for QR)

Agents & permissions

Agents are the human users who log into the sub-account. Each agent has their own login and inbox view.

  • Add agent: invite by email. The agent receives the dashboard login link and creates their password.
  • Assign agents to numbers: an agent only sees inboxes for the WhatsApp numbers they own. Useful when multiple teams share a sub-account.
  • Remove agent: revokes access immediately. Open conversations stay in the inbox of the remaining agents on that number.

Integrations

Most workflows in Wazzap involve hooking the sub-account to an external tool. The most common ones:

  • HighLevel CRM: native bidirectional sync. Every chat lands in GHL's conversation tab.
  • OpenAI and ElevenLabs: AI replies and voice notes.
  • n8n: build automations on top of inbound and outbound events.
  • Webhooks: receive every message event in your own stack.

Settings inside a sub-account

The sub-account's settings menu covers everything that affects only this workspace:

  • Profile: display name and WhatsApp profile metadata for each connected number.
  • Spintax: the 6 global Spintax slots. See the Spintax guide.
  • Delay message: default delays for outbound sends, configurable per number.
  • Triggers: tag triggers, staff triggers, lead tag, no-WhatsApp tag.
  • Tabs (SMS → QR): change which tab in your CRM holds the WhatsApp QR. See this guide.
  • API key: generate the key used for webhooks and direct API calls.
!

Settings inside a sub-account only affect that sub-account. Brand, custom domain, and subscription live in the admin panel.

Power workflow: pair the sub-account to HighLevel, set Spintax slots for your common greetings, enable Delay Message, and you have a production-grade outbound stack in 15 minutes.

Was this page helpful?