Sending and safety

WhatsApp safety

Health scores, warmup and the guardrails that prevent bans.

Why numbers get banned

A personal or business WhatsApp number connected by QR code is your real number, running through WhatsApp's own app. WhatsApp watches how that number behaves, not just how fast it sends: a number that blasts messages at a constant, mechanical rate, ignores sending hours, or gets marked as spam by too many recipients can be banned outright. The Safety tab exists to keep a number inside the pattern of a real person sending real messages.

Safety: health score, warmup and the daily budget
The WhatsApp safety tab

Health score and bands

Each WhatsApp QR channel has its own health score gauge, backed by a 7-day sparkline so you can see whether it is trending up or down. The score sits in one of three bands:

BandWhat it means
HealthySending normally, no action needed.
At riskSomething in recent sending is raising flags. Slow down and review recent activity.
CriticalHigh risk of a ban. Sending should stop until the score recovers.

Warmup and daily budget

A newly connected number starts in a warmup stage: its daily send budget starts low and grows as the number ages, the same way a real person's usage would ramp up rather than jump straight to bulk volume. The daily budget bar on the Safety tab shows how much of today's allowance has been used.

Do not skip warmup on a new number
Pushing a brand-new number straight into a broadcast is one of the fastest ways to trigger a ban. Let the warmup stage run its course before relying on the number for volume sending.

Pacing, hours and the circuit breaker

Safety settings let you tune how cautious a channel is:

  • Warmup schedule and band thresholds, if you want to adjust how the defaults behave.
  • Pacing and sending hours, so messages go out at a human pace and only during hours a real person would be messaging.
  • A circuit breaker that automatically pauses a broadcast if it hits a spike in failures, so a bad send list cannot burn through a number's health before anyone notices.

A flow's message steps follow the same thinking: the wait before a step's next action is a randomised 5 to 15 seconds rather than a fixed delay, so an automated conversation does not read as a machine sending on the second.

Events log and WABA channels

The safety events log records what happened and when: warmup stage changes, band changes, circuit breaker trips. It is the first place to check when a score moves and you want to know why.

WABA channels are exempt
The WhatsApp Business API is hosted by Meta itself, not by a phone Chatz connects to. Meta applies its own quality and ban rules directly, so no health score, warmup stage or circuit breaker applies to a WABA channel.