> ## Documentation Index
> Fetch the complete documentation index at: https://docs.zavu.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# WhatsApp Alternative Overview

> Link a WhatsApp number by scanning a QR code — no Meta Business Account or embedded signup required.

WhatsApp Alternative lets you connect a WhatsApp number by **scanning a QR code**, the same way WhatsApp Web links a device. There is no Meta Business Account, no embedded signup, and no template approval — you link a number in seconds and start sending on the `whatsapp_alt` channel.

<Note>
  WhatsApp Alternative is a gated feature. It must be enabled for your team before the `whatsapp_alt` channel and the `/v1/whatsapp-alt/*` endpoints become available. Contact Zavu to enable it. It is not available with test-mode API keys.
</Note>

## When to use it

<CardGroup cols={2}>
  <Card title="No Business Account" icon="qrcode">
    You want to message from a number that isn't set up on the WhatsApp Business Platform (Cloud API).
  </Card>

  <Card title="Fast onboarding" icon="bolt">
    You need a client's number live in seconds — scan a QR instead of running embedded signup.
  </Card>

  <Card title="Personal / existing numbers" icon="mobile">
    The number already uses the regular WhatsApp app and you want to automate it without migrating to a WABA.
  </Card>

  <Card title="Two-way conversations" icon="messages">
    Inbound and outbound texts, media, reactions, and groups, delivered through the same webhooks as every other channel.
  </Card>
</CardGroup>

## How it differs from official WhatsApp

|                | Official WhatsApp (Cloud API)   | WhatsApp Alternative                         |
| -------------- | ------------------------------- | -------------------------------------------- |
| Connection     | Meta embedded signup (WABA)     | Scan a QR code (like WhatsApp Web)           |
| Setup time     | Minutes to hours                | Seconds                                      |
| Templates      | Required outside the 24h window | Not used                                     |
| 24-hour window | Enforced by Meta                | Not enforced                                 |
| Egress         | Meta's servers                  | Zavu residential proxy or your own device    |
| Best for       | Scale, compliance, marketing    | Quick links, existing numbers, conversations |

<Warning>
  WhatsApp Alternative connects through the same channel the WhatsApp mobile app uses. To keep a linked number healthy, all of its traffic egresses through an in-country residential IP (never a datacenter IP) and the number always appears from the same exit. Sending unsolicited or high-volume marketing from an unofficial link risks the number being blocked by WhatsApp. Use it for consented, conversational messaging. For large marketing sends, use the official WhatsApp channel.
</Warning>

## How it works

<Steps>
  <Step title="Create a session">
    Call the API to start a session. Zavu spins up a linked-device connection and generates a QR code. See [Sessions](/guides/whatsapp-alt/sessions).
  </Step>

  <Step title="Scan the QR">
    Open WhatsApp on the phone → **Linked devices** → **Link a device**, and scan the QR. The session moves to `ready`.
  </Step>

  <Step title="Link the session to a sender">
    Attach the session to one of your senders. That sender's `whatsapp_alt` traffic now routes through the linked number.
  </Step>

  <Step title="Send and receive">
    Send with `channel: "whatsapp_alt"` and receive inbound messages via your sender webhook. See [Sending & Receiving](/guides/whatsapp-alt/sending-receiving).
  </Step>
</Steps>

## Egress: keeping the number active

Every WhatsApp Alternative number reaches WhatsApp through an **egress** — an in-country residential IP. You choose between the managed **Zavu residential proxy** and your own **Android egress device**, and Zavu can automatically fall back between them so the number stays active. See [Egress & Fallback](/guides/whatsapp-alt/egress).

## Connecting clients via invitations

If you're a partner onboarding clients, you can send a QR-link invitation instead of driving the session API yourself — set `connectionType: "whatsapp_alt"` when creating a [partner invitation](/guides/partner-invitations/api). The client scans the QR and the resulting sender lands in your project.

## Next steps

<CardGroup cols={2}>
  <Card title="Sessions" icon="qrcode" href="/guides/whatsapp-alt/sessions">
    Create a session, get the QR, link it to a sender.
  </Card>

  <Card title="Egress & Fallback" icon="route" href="/guides/whatsapp-alt/egress">
    Zavu proxy vs. your own device, per-GB billing, automatic fallback.
  </Card>

  <Card title="Sending & Receiving" icon="messages" href="/guides/whatsapp-alt/sending-receiving">
    Send on the `whatsapp_alt` channel and handle inbound webhooks.
  </Card>

  <Card title="Groups" icon="users" href="/guides/whatsapp-alt/groups">
    Receive and identify group messages and their author.
  </Card>

  <Card title="Stories & Status" icon="circle-dashed" href="/guides/whatsapp-alt/stories">
    Receive contacts' status/story updates as opt-in events.
  </Card>

  <Card title="Partner Invitations" icon="user-plus" href="/guides/partner-invitations/api">
    Onboard client numbers with a QR-link invitation.
  </Card>
</CardGroup>