Warming Up a New WhatsApp Number — A Day-by-Day Send Schedule

You just paired a new WhatsApp number, wired it into your integration, and you're ready to push your entire contact list through it on day one. Don't. A number with zero sending history that suddenly messages forty new recipients looks exactly like a spam operation to Meta — and to TextMeFlow's own anti-spam pipeline, which watches for precisely that pattern.

This article gives you a concrete schedule for bringing a new number up to full volume without tripping any of the warning signs, and explains the one mechanism that matters most: the new-contact spike warning.

Why a fresh number is scored differently

WhatsApp restricts individual numbers, not accounts. If your account has three paired devices, one of them can get throttled while your account-wide totals still look perfectly calm. TextMeFlow's anti-spam pipeline mirrors that: it counts first-contact messages per number and compares each number against its own recent history, not against some fixed global cap.

That comparison is the whole game. A holiday rental number that greets 40 new guests a day, every day, is normal — that's its baseline. A number that greeted 2 people yesterday and suddenly greets 40 today is not, even though 40 is a perfectly modest volume in absolute terms. The trigger only logs a warning and bumps the account's risk score; it never blocks the send outright, because a genuinely busy day shouldn't cost a guest their door code. But racking up that warning repeatedly on a brand-new number is exactly how a risk score climbs toward suspension before you've even sent your first invoice reminder. Full details on how the score accumulates are in the anti-spam policy and in our breakdown of the risk score itself.

A four-week ramp-up plan

There's no magic number that makes a number "trusted" — the pipeline only ever compares a number to its own history — but a gradual, steadily-increasing curve never looks like a spike to that comparison. This schedule works for most senders switching from a legacy tool or provisioning a second number for a new location:

Week 1 — establish a baseline. Send to 5–10 new contacts per day, spread across the day rather than in one batch. This is enough for the pipeline to start building "recent history" for the number without registering as unusual on a number that has none yet.

Week 2 — double, don't jump. Move to 15–25 new contacts per day. Still spread out, still nowhere near your plan's hourly ceiling.

Week 3 — approach real volume. Scale to 40–60 new contacts per day, depending on how large your actual daily intake is. If your real, steady-state volume is lower than this, you're already there — stop scaling and just run normally.

Week 4 onward — normal operation. By now the number has four weeks of gradually increasing history behind it. A day that matches or modestly exceeds recent days is exactly what the comparison expects, whatever the absolute number is.

Existing contacts you're migrating from another tool don't need to go through this at all — the spike warning only fires on new (account, recipient) pairs, so re-messaging people who already know you doesn't count against the ramp.

Don't fight the pacing that's already built in

While you're warming up, resist the urge to also disable the random pacing between sends (20–90 seconds by default) or the first-contact opt-in preamble. Both are there specifically to make a young number's traffic look human rather than scripted, and turning them off during exactly the period when the number has the least trust built up is the opposite of what you want. Save those toggles for later, if at all, once the number has real history.

Watch the signal that moves before the score does

The new-contact spike warning tells you when something already tripped. The confirmed-delivery ratio per number, visible in the portal, tells you when something is about to. A number being quietly squeezed by WhatsApp often keeps returning "sent" from the API while fewer of those messages actually arrive — check that ratio weekly during the ramp-up period, not just the risk score.

Checking your progress via the API

You can pull the current risk score for the account at any point during the ramp-up:

curl -H "Authorization: Bearer $TOKEN" \
  https://api.textmeflow.eu/v1/accounts/me

A flat, low risk_score throughout the four weeks means the schedule is working. If it climbs anyway, slow down further before pushing more volume — the pipeline is telling you the number needs more time, not that something is broken.

Start the clock today

The sooner a new number starts sending at a small, steady volume, the sooner it builds the history that lets it scale. If you're setting up a second number for a new location, or replacing a number from a provider that got you banned before, this is the moment to start slow rather than the moment to catch up fast.

Try TextMeFlow free — the anti-spam pipeline, pacing, and risk score all run on every plan, including the free one: 50 messages a month, no time limit.