# Why your number quality matters

> Meta scores your number by how people react to your messages, and that score decides how much you can send. What Konverda does to protect it.

Fuente / source: https://soporte.konverda.com/en/docs/deliverability-and-meta/why-your-number-quality-matters
Idioma / language: en
Actualizado / updated: 2026-08-25

---
Your WhatsApp number has a reputation, and Meta measures it. If people block or report your messages, quality falls; if it falls far enough, Meta reduces how much you can send and, in the worst case, disables the number. There is no quick appeal and no spare number: it is the most fragile asset you own.

## What Meta measures {#what-meta-measures}

Meta does not read your messages to judge them. It measures **how people react to them**: blocks, reports and silence. A message that is irrelevant to the person receiving it costs quality even if it is perfectly written and approved.

Which gives an unintuitive rule: **sending less and better protects your capacity to send more later**.

## Messaging tiers {#tiers}

Meta assigns every number a tier that limits how many **new conversations** you may start per day:

**«50/día»** (50/day) · **«250/día»** · **«1.000/día»** · **«10.000/día»** · **«100.000/día»** · **«sin límite»** (unlimited)

The tier rises with sustained use and good quality, and falls when quality drops. Meta manages it, not Konverda: we respect it and show it in **«Ajustes»** (settings) → **«Canal»** (channel) → **«Envío»** (sending) as soon as Meta tells us.

:::nota
The tier limits **conversations you start** (the ones that go out as templates). Replying to someone who wrote to you, inside the 24-hour window, does not consume tier.
:::

## The daily limit you set {#daily-limit}

On top of Meta's ceiling, you set your own **«límite diario de conversaciones»** (daily conversation limit) in **«Ajustes»** → **«Canal»** → **«Envío»**. The limit that actually applies is always the lowest of the three: your limit, Meta's tier, and the **«arranque progresivo»** (progressive warm-up).

The same screen tells you today's effective limit, so you never have to work it out.

## «Arranque progresivo», for new numbers {#warm-up}

A brand-new number that starts by sending a thousand messages is a marked number. The **«arranque progresivo»** prevents that: the limit grows with real usage, never above **twice your best day in the last week**, and never below the floor you set.

:::importante
It is **off by default**. Turn it on when you put a new number into service — it is the difference between warming it up and burning it.
:::

Only completed days count, so what you send today cannot raise today's limit.

## The pace of sending {#pacing}

Konverda never sends a wave all at once. Messages leave **staggered**, at around **12 per minute**, through the send queue. The wave composer reminds you while you build it: **«~12/min escalonado · tope N/24h»** (≈12/min staggered · cap N/24h).

:::nota
Restarting the system mid-send is safe: the queue lives in the database and no message is ever sent twice.
:::

There is a second limit no setting solves: **how many people you can actually answer**. Every conversation you open may reply, and the 24-hour window starts running from that moment. Do not open more conversations than your team can answer in a day.

## «Guardián» (guardian) or «Manual» {#guardian-or-manual}

In **«Ajustes»** → **«Canal»** you choose what the platform does when Meta flags your number:

- **«Guardián»** — the system acts on its own: it pauses sending and resumes when the number recovers. It explains afterwards.
- **«Manual»** — it detects the same things and warns you, but the controls stay yours.

Some things cannot be switched off in either mode: **consent and opt-outs**, the **stop on a Meta block**, and the **number's tier ceiling**.

When something happens you get a notification with the fact and its consequence: quality at risk and sending paused, account disabled and sending paused, quality recovered and sending resumed.

## Pausing and resuming by hand {#pausing}

The **«Pausar envíos»** (pause sending) button in **«Ajustes»** → **«Canal»** is yours and only yours: no automatic signal can lift it. While sending is paused, campaigns and automations **hold** their messages in the queue and release them when you resume — nothing is lost.

## What actually protects the number {#good-practice}

- Only write to people who agreed to hear from you. The [opt-in rule](/en/docs/contacts-and-consent/the-marketing-opt-in) exists for this.
- Keep the **opt-out footer** on marketing templates. An easy opt-out is infinitely better than a report.
- Segment. A relevant wave to three hundred people does less damage than an irrelevant one to three thousand.
- Put new numbers into service with the **«arranque progresivo»** on.
- Reply. An answered conversation is the cheapest positive signal there is.