The screen is blunt: you are temporarily banned from WhatsApp, a countdown, and no explanation. If the number runs a business, the timer is the smaller problem. The bigger one is that a temporary ban means WhatsApp has already classified something you did as abuse, and the next strike may not come with a timer.
This guide covers what the countdown means, the two causes WhatsApp names on its own Help Center page, the sending habits that put most business numbers there, why repeat bans get worse, what to do while the clock runs, and what to change before you send again.
What the countdown screen actually means
A temporary ban is a timed lock on the number. WhatsApp opens to a message saying you are temporarily banned, shows how long is left, and lets you back in when the countdown ends. Nothing you tap speeds it up. WhatsApp does not publish a schedule. People who manage large numbers of business WhatsApp numbers report that the countdown typically runs 24 to 72 hours, which matches the 72-hour figure many people search for; treat that as an industry estimate, not a WhatsApp rule. The only figure that binds is the one on your screen.
Read it as one step on a ladder that people who manage many business numbers describe as Normal, Restricted, Temporarily banned, Banned. Restricted means new chats are blocked while old ones still work (next section). Temporarily banned is the countdown. Banned reads "This phone number can’t use WhatsApp" and offers a Request review button instead of a timer. If you see a countdown, you have not lost the number. You have been warned, and the warning is on record.
Two things stay true while the ban lasts: you cannot read your chats or restore a backup on a banned number, and "third party services can’t ban your WhatsApp account or remove your account ban".
Restricted Account: the step before the countdown
WhatsApp’s Help Center lists a restricted-accounts page next to its ban pages; people who manage many business numbers describe what it looks like from the sender’s side. The number stays signed in and your existing chats keep working. Until the timer on the screen ends, everything that reaches new people is blocked: starting a chat with a number you never messaged, calling a new contact, creating a group, adding members, linking a device.
If you send from a computer through a linked device, the tell is a split: messages into your existing chats go through, messages to new people stop going through. That split means restricted, not banned. Pause everything aimed at new people and let the timer run. Switching to another number here is the evasion pattern described below, and the behaviour that caused the restriction moves with you.
Restricted is the reversible step and the clearest early warning you get: whatever was running when it landed is what the countdown will punish if it runs again.
The two causes WhatsApp names
WhatsApp’s Help Center page on temporary bans gives exactly two reasons: "it could mean you’re using an unofficial version of WhatsApp or harvesting information, known as scraping." The instruction that follows is just as short: "Switch to the official app or stop engaging in scraping after being temporarily banned. If you don’t, your account might be permanently banned from using WhatsApp."
Unofficial versions are the modified apps such as GB WhatsApp and WhatsApp Plus. WhatsApp cannot validate their security, treats their use as a Terms of Service violation, and notes in its "Stopping Abuse" white paper that modified clients "cannot circumvent our detection systems that run on our servers". If you are on one, the only fix is the official app, installed before the countdown ends.
Scraping is defined by WhatsApp as "the automated extraction of information, both targeted and at scale, for any unpermitted purposes", including "phone numbers, user profile pictures, and statuses". For a business this is usually a tool rather than a habit: a group-member exporter, a number checker that pulls profile data from thousands of contacts, or a bulk extension that reads your chat list to build its own database.
If neither describes you, and for most business owners neither does, the ban came from the behaviour signals below, which the Help Center spells out on other pages.
The causes businesses actually hit
- Burst sending. The white paper describes normal use as "tapping messages one at a time or occasionally forwarding content", and gives the extreme case: an account that "registered five minutes before attempting to send 100 messages in 15 seconds" is banned "immediately and automatically". Older numbers get more room, but a burst is a burst. A coaching business used the phone’s forward-to-many feature to push 540 messages in about 3 minutes; the number was disconnected three days later.
- Messaging people who never saved you. WhatsApp’s stated best practice is to "only send messages to those who have contacted you first or have requested you contact them on WhatsApp". A first message to someone who does not have you in their contacts arrives with a report and block prompt already on screen, and reports on a first message from an unknown number are the ones WhatsApp trusts most.
- Over-using broadcast lists. The Help Center warns that "frequent use of broadcast messages may lead people to report your messages, and we ban accounts that are reported multiple times". Broadcasts only reach people who saved you, so a list blasted daily is a list of your most loyal contacts being trained to report you.
- Bulk-sender extensions and bots. The rule is plain: "Don’t bulk message, auto-message, or auto-dial using WhatsApp." Browser extensions that drive WhatsApp Web, desktop senders and scripts all produce the same pattern: identical text to hundreds of chats, at machine speed, with no pauses.
- Lists you did not build. "Using contact lists that aren’t yours" is a named practice to avoid. Bought or scraped lists have never heard of you, which makes the report rate on the first message high.
- Group adds without consent. The white paper says WhatsApp bans "accounts with suspicious group behavior, if appropriate, even if their activity rates are low". Ask before adding anyone, and if they leave, "honor their decision".
- Ignoring a stop. "If a contact asks you to stop messaging them, you should remove the contact from your address book and refrain from contacting them again." A second message after a stop is the surest way to turn a mild complaint into a report.
Why it happens again and again, and when it turns permanent
The Help Center gives the rule in one sentence: keep doing it and "your account might be permanently banned". It does not publish a ladder of durations. What the white paper adds is that every ban feeds the model. WhatsApp uses banned accounts to "reverse engineer past behavior to prevent similar abuse in the future", and if its systems "previously caught accounts after they sent 50 messages", the next model "will catch similar attempts much faster".
That is why repeat offenders feel they are being banned for less each time. The number now carries a history. The campaign that earned a countdown in March can earn a permanent ban in April, because the account no longer gets the benefit of the doubt WhatsApp extends to "an innocent user simply telling their contacts about a new phone number".
The other escalation is one you cause yourself. Reinstalling, moving the SIM to another phone, registering the number again, or opening it in a modified app while the timer runs all look like evasion. WhatsApp’s bulk-messaging notice says it is "aware that some companies attempt to evade our machine learning systems". Evasion is scored, not ignored.
What to do while the countdown runs
- 1
Leave the app alone
Do not reinstall WhatsApp, do not switch phones, do not re-register, and do not try a second number from the same phone or network. Check the timer once a day if you must; otherwise leave it.
- 2
Remove the tool that did the sending
Uninstall the extension, script or bulk sender, and log out any linked device you do not recognise under Linked devices. If a modified app is involved, replace it with the official app before the countdown ends, because that is the one instruction WhatsApp gives.
- 3
Clean the list
Delete everyone who asked you to stop, everyone who never replied to two messages, and any contact you cannot say how you got. The white paper’s yardstick is whether recipients have "the sender’s account in their contacts"; a list that mostly fails it is the problem, whatever tool sends to it.
- 4
Use the downtime
The same people’s advice for a countdown ban: look at how many of the messages you sent in the last 30 days got a reply, work out what you were sending when the ban hit, and come back slower, because "coming back at the same pace that triggered the restriction produces the same result". Their target, 30 replies for every 100 messages, is an industry estimate, not a WhatsApp rule.
- 5
Write the opt-out into your messages
Add one line to every campaign: reply STOP to stop hearing from us. It gives an annoyed recipient a cheaper action than the report button, and it is a signal you can act on before WhatsApp does.
- 6
Set up an inbound route
A QR code on the counter, a click-to-chat link on your site, a form that opens a chat. WhatsApp’s own best practice: "It’s best to give contacts your phone number so they can message you first." A report on a conversation the customer opened is one WhatsApp checks before trusting; a report on your cold first message is the one it trusts most.
What to change before you send again
- Pace every send. Seconds between messages, never the same gap twice, and a hard ceiling per minute and per hour. If a tool sends for you, it should enforce this rather than leave it to your restraint.
- Send to people who know you. Start with contacts who saved you or replied in the last 30 days. Cold contacts, if you must, in small numbers, personally worded, with an opt-out line, and never as a list.
- Keep the number in normal use. A line that is silent for two weeks and then sends 400 messages is a spike. A line that talks with customers every day and then sends 100 is a bump. WhatsApp weighs "current and past behavior" together.
- Send in daytime. WhatsApp publishes no rule about hours, but a message at 3 a.m. is more likely to be blocked, and blocks are what is scored.
- Answer replies. WhatsApp says about 90% of its messages are one person to another; a number that sends hundreds and receives almost nothing does not look like that. There is no published threshold, but a shared inbox where someone actually answers changes the shape of the account.
- Honour every stop immediately and permanently, not at the next list clean-up.
Is WhatsApp Web or a linked tool the problem?
Linking a device is not a violation; WhatsApp Web and the desktop app are WhatsApp’s own feature. What gets numbers banned is what runs on top of the link. An extension that fires 300 identical messages through the browser tab is automation whether or not the tab itself is official.
A tool that connects as a linked device the way WhatsApp Web does, with nothing installed on the phone and no modded app, avoids the "unofficial version" cause entirely. It does not avoid the behaviour causes. Spun spaces every campaign message by a random gap and caps the pace on the server so a fast setting cannot override it, pauses campaigns overnight by default, can limit a campaign to saved contacts or to people you spoke with recently, and drops anyone who replies with a stop word onto a do-not-send label that every future send respects. That reduces the risk. It does not make a cold list safe, and no tool on any lane can promise immunity to a sender who spams.
One more variable the white paper names is the network: "reputation of other users sharing the same computer network" is a scored feature. WhatsApp does not publish how it weighs where a session connects from. What Spun can say is where the session connects from: with Self Proxy it exits through your own home or office connection, so WhatsApp sees the same address your phone uses rather than a datacenter.
Related: Can shared Wi-Fi, a VPN or a datacenter get you banned? · How to get a WhatsApp number unbanned
The problems behind a temporary ban, and how Spun handles each one
- 1
Your campaign ran at machine speed
A burst of hundreds of messages is the velocity signal WhatsApp bans on, and a perfectly even gap between them is the automation signal. In Spun every campaign uses a pace preset (Conservative 15 to 30 seconds, Normal 8 to 15, Aggressive 3 to 8 with an on-screen warning) with a random gap per message, and the server caps the pace on top, so a fast preset is a request, not a guarantee. It reduces the risk; no tool can promise immunity to a sender who spams.
- 2
Your campaign ran overnight
A message at 3 a.m. gets blocked more often, and blocks are what is scored. Spun’s quiet hours (22:00 to 08:00 by default) and the per-campaign send window pause a campaign overnight and resume it in the morning.
- 3
You blasted a list and half of them had never saved you
Each first message to someone who never saved you arrives with a report button, and those reports are the ones WhatsApp trusts most. Spun’s audience filter has a "Saved contacts only" setting and an activity filter (last 7, 30 or 90 days), and a pre-send check refuses numbers that are not on WhatsApp. The consent half is yours.
- 4
A customer said stop and got three more messages
WhatsApp’s rule is to remove that contact and never message them again; the next message is the surest route to a report. Spun creates a DONOTSEND label on every account, detects STOP, unsubscribe, remove me and their equivalents in 11 languages, applies the label automatically and enforces it in every campaign, bot, follow-up and forward.
- 5
You reinstalled and re-registered while the countdown ran
Reinstalling, switching phones or re-registering during a ban looks like evasion, and evasion is scored. If WhatsApp blocks the number, Spun parks the line rather than auto-restarting it, walks you through WhatsApp’s own review, and reconnects only when you say the number is restored; it never swaps the number behind your back. The review decision itself is WhatsApp’s alone.