1. Overview
This guide is for operators running customer service / marketing with WhatsApp personal numbers on SaleWisely. The goal: over the first 2–4 weeks, warm a new number into a healthy one that looks like a real person on a clean network, sharply lowering ban rate.
Core idea: WhatsApp scores each number with an overall trust score. Warming = behave like a human, keep the network clean, and never do cold-start blasting. The deadliest signals are blocks / reports / low read rate.
2. How WhatsApp decides a number is 'bad'
WhatsApp doesn't ban on a single threshold; it continuously computes an overall trust score:
- Number quality: age, registration method, SIM authenticity, real usage history.
- Network reputation: egress IP type (residential>mobile>datacenter), whether flagged, IP-vs-number-country match, frequent IP hopping.
- Device consistency: stable device environment, no abnormal multi-device concurrency.
- Human-like behavior: send rate/spacing, day-night rhythm, send-only vs two-way, instant send/read.
- Social feedback (highest weight): whether recipients reply / block / report.
In our testing, what WhatsApp cares about most is how messages are received over roughly the last 7 days (recency-weighted): blocks, reports and low read rate drop a number's standing the fastest.
3. Startup SOP (the first 14 days matter most)
Number source & registration
- Prefer a clean physical SIM; virtual / OTP-farm numbers are far riskier.
- After registering, use it normally on a real phone with the official app for 3–7 days (send a few, add a few real contacts, join 1–2 real groups, set photo/profile) before connecting it to the platform.
- Don't batch-register many numbers on the same machine/IP (number-range + IP correlation gets them banned together).
- Keep number country, SIM country, proxy IP country and profile language consistent.
First login
- After connecting to the platform, sit idle 24–48h, only receive and reply, don't initiate.
- Don't log out / re-login repeatedly (rapid repeated logins trigger risk controls).
- Only one active login per number at a time.
Profile / device / network
- Fill photo, name, About early; complete the business profile for WA Business.
- One number = one stable device environment, kept unchanged after binding; don't share one environment across numbers.
- One number = one dedicated residential IP, geo-matched to the number's country, all egress via proxy; never hit WhatsApp from a datacenter's real IP.
4. Staged ramp & rate limits
Ramp a new number gradually; cap cold-adds separately and always conservatively. The table below is the baseline we settled on from testing (~1.8× daily growth):
| Stage | Outbound msgs/day | Cold-adds/day |
|---|---|---|
| Day 0 (login) | 0 (receive only) | 0 |
| Day 1–2 | ≤5 (mostly replies) | 0 |
| Day 3–5 | 10–20 | ≤5 |
| Day 6–7 | 20–40 | ≤8 |
| Week 2 | 40–60 | ≤10 |
| Week 3 | 60–100 | ≤15 |
| Week 4 | 100–150 | ≤20 |
| Mature (1 month+) | 150–300 | As few as possible; prefer inbound adds |
Pacing details
- Randomized spacing: 30s–several minutes per message, never fixed intervals; add extra delay for strangers.
- Show the 'typing' indicator; don't read instantly (delay seconds to tens of minutes).
- Match the time zone: send in daytime, slow down heavily or stop at night (e.g. 02:00–06:00).
- No floodgate bursts; spread across the day.
5. Content strategy & cold outreach (high risk)
Content
- De-dupe + variants: don't send the identical sentence to a batch; use multiple scripts + placeholders (name/time/product).
- Few links/media early: keep new numbers mostly plain text for the first two weeks; if a link is required, use your own trusted domain, not short links / unknown / reported domains.
- No keyword stuffing, no spammy CTAs, no suspicious attachments.
Cold outreach = the #1 ban trigger
- Sending a first message to many strangers not in your contacts is the strongest ban trigger, especially fatal for new numbers.
- Prefer letting customers add you: official link
wa.me/number, QR codes, website widget, ad landing pages. - When you must reach out: throttle hard (single digits/day for new numbers), only message people with a reason (ordered, left info, opted in), keep the first message short and human.
6. Engagement quality & reply rate
Reply rate / being-replied-to is the lifeline of a number's health. If many recipients don't reply, block, or report, the trust score collapses.
- Better to send less to people who reply than more to people who ignore you.
- Keep two-way conversations: during warm-up you can have a few of your own warmed numbers chat human-like with each other (back-and-forth, with delays) to feed activity and social feedback.
- Being replied to, saved as a contact, added to groups are strong positives.
- Stop messaging contacts that still have <10% reply rate after 5 messages.
7. Monitoring & disconnect/ban handling
Warning signs (slow down / isolate the number)
- Messages stuck at a single check (undelivered), or suddenly many fail to send.
- The number disconnects frequently or repeatedly asks to log in again.
- Rising block/report rate, plunging reply rate.
- Frequent add-contact failures.
What to do on disconnect / ban
- Occasional disconnects: the system recovers automatically; no action needed.
- Frequent disconnects / repeated re-login prompts: usually the number or its network (IP) is being risk-controlled — slow down immediately and check the IP and behavior; don't re-login repeatedly in a short time (it worsens risk control).
- 'Account banned / cannot log in': usually terminal — file an official WhatsApp appeal and don't keep retrying login during the appeal; if it never recovers, switch numbers.
8. Built-in protection & operator actions
SaleWisely already has multiple built-in protections to lower ban rate: human-like send pacing and online status, risk monitoring with auto slow-down/pause, a stable device and network environment, progressive history loading, and more — operators don't need to manage the internals.
What operators should do:
- Ramp by number age: keep new numbers strictly on the staged table above; don't rush volume.
- Restrain cold outreach: prefer letting customers add you; throttle proactive outreach hard.
- Watch reply rate: slow down or pause numbers with abnormal reply/report rates.
- One number = one dedicated IP; don't share across numbers or hop IP/country.
9. Common pitfalls & security
Common pitfalls
- New number straight into broadcast → dead the same day.
- Multiple numbers sharing one IP / one device environment → correlated and banned together.
- Saving money with datacenter IPs → very low startup success.
- Re-logging in repeatedly on every disconnect → more logins, more bans.
- Send-only, fixed-interval blasting → classic bot signature.
- Retrying login over and over after a ban → turns a temp ban permanent.
Compiled from SaleWisely's long-term hands-on testing across many real numbers.
