Sending Limits

​

Account levels

​

Verifying a phone number

1. In the dashboard, go to Sandbox and click Generate Verification Code.
2. Scan the QR code or click Open WhatsApp on the phone you want to verify.
3. Send the pre-filled VERIFY- message to Zavu’s sandbox number.

​

Sending to any number

• Verify your identity under Identity verification (/kyc): an ID document and a selfie, a few minutes.
• Add a payment method under Billing: about half a minute. Nothing is charged.
• Settle a deposit under Billing.
• Subscribe to a paid plan.

​

Daily ceilings

• The SMS ceiling above Sandbox keys on identity, not on the level: an account that reached Verified by saving a card sends 200 a day until its identity or business verification is approved. A higher limit can be agreed for an account.
• Email has no verification gate on single sends. A sender with a verified domain sends from day one, within the plan’s quota: 100 a day and 3,000 a month on Free.
• A daily ceiling never reduces a monthly allowance: 100 a day on the conversational group still reaches the 2,000 messages a month Free includes.
• Broadcasts count each recipient against the same ceiling. Recipients beyond it are marked failed with errorCode DAILY_LIMIT_EXCEEDED and are not retried the next day.

​

Monthly allowance on the app channels

• Messages you send from the WhatsApp Business App on your own phone while coexistence is on. Meta mirrors them to Zavu so they appear in your inbox, but Zavu did not send them and does not count them.
• Failed sends. An outbound message counts when it is accepted by the channel, not when it is created.
• SMS, voice and email. Each is billed or metered on its own terms; see the daily ceilings above and your plan’s email quota.

​

What happens at the cap

• Sending is refused. POST /v1/messages answers 429 a2p_limit_exceeded, and so does every other way of sending: the dashboard composer, an inbox reply, a group reply, a reaction, an AI agent’s reply, and each remaining recipient of a broadcast (marked failed with errorCode A2P_LIMIT_EXCEEDED).
• Receiving is refused too. An incoming message on those channels is not stored, does not appear in your inbox, and fires no message.inbound webhook. It is not delivered later when the month resets. We email the team the first time this happens in a month.

​

Errors

​

a2p_limit_exceeded (429)

{
  "error": {
    "code": "a2p_limit_exceeded",
    "message": "Your sending is paused — monthly limit reached (2,000/2,000). The allowance counts messages you receive as well as the ones you send. Upgrade to Pro for unlimited messages/mo to restore it: https://dashboard.zavu.dev/upgrade?from=a2p-limit",
    "details": {
      "limit": 2000,
      "used": 2000,
      "remaining": 0,
      "tier": "free",
      "upgrade": {
        "nextTier": "hobby",
        "nextTierName": "Pro",
        "nextTierPrice": "$20/mo",
        "upgradeUrl": "https://dashboard.zavu.dev/upgrade?from=a2p-limit"
      }
    }
  }
}

​

destination_not_verified (403)

{
  "code": "destination_not_verified",
  "message": "This account can only send to numbers it has verified. Verify your identity or add a payment method to send anywhere.",
  "details": {
    "verifiedNumbers": ["+56912345678"],
    "dashboardUrl": "/kyc"
  }
}

​

daily_limit_exceeded (429)

{
  "code": "daily_limit_exceeded",
  "message": "Daily SMS limit reached (25/day). Verify your identity or add a payment method to raise it.",
  "details": {
    "limit": 25,
    "remaining": 0,
    "dashboardUrl": "/kyc"
  }
}

​

kyc_required (403) on broadcasts

{
  "code": "kyc_required",
  "message": "Verify your identity, add a payment method, or upgrade before sending broadcasts. You can keep editing this draft in the meantime.",
  "details": {
    "dashboardUrl": "/kyc"
  }
}

​

Test-mode keys

• WhatsApp only. The key ignores your senders and sends from Zavu’s shared sandbox number. Any other channel is refused with 400 Sandbox mode only supports WhatsApp — including Telegram, Instagram, Messenger and email.
• Only to a phone on your team. The recipient must be a team member’s phone number, confirmed in your account. Anything else is refused with 403.
• No calls. POST /v1/calls refuses a test key with 400.

​

Next Steps