The short version
WhatsApp doesn't ban numbers for selling. It bans numbers for one-sided conversations. Every big enforcement change since 2024 points at the same thing: messages people didn't ask for, didn't answer, and reported.
For B2B sales teams in India this matters more than anywhere else. WhatsApp is the default sales channel here, and India is where WhatsApp bans the most accounts: roughly 50 to 100 lakh +91 accounts every month, going by its published compliance reports.
Three ideas run through this guide.
- A ban is a lagging indicator. The things that cause it (blocks, reports, unanswered outreach, unofficial apps) show up days or weeks earlier. Teams that watch for them rarely get banned.
- The number isn't the asset. The conversation history, the context and the pipeline are. If those only live in one rep's phone, they go when the SIM goes.
- 2026 rewards reply-first selling. Caps on unanswered messages, quality-based limits and India's SIM-binding rule all lean the same way: two-way conversations get more room, and broadcast-style outreach gets less.
How big this is, and how detection works
WhatsApp bans millions of Indian accounts a month, and most bans come from automated detection, not complaints. Under the IT Rules, 2021, WhatsApp publishes a monthly report covering accounts with a +91 number.
| Month | +91 accounts banned | Banned before any user report |
|---|---|---|
| April 2026 | 54.7 lakh | Not stated in coverage |
| March 2026 | 59.78 lakh | 13.76 lakh |
| June 2025 | 98 lakh+ | 19.79 lakh |
| February 2025 | 97 lakh+ | 14 lakh+ |
Two details matter for a sales team.
- Appeals rarely win. In April 2026 WhatsApp received 19,189 grievance reports from India and took action on 486. In June 2025, 16,069 ban appeals led to action on 756 accounts. Plan as if a ban is final.
- Detection looks at behaviour. WhatsApp says it can't read end-to-end encrypted messages. It watches three moments: when a number registers, how it messages, and negative feedback (blocks and reports). It also uses unencrypted signals such as profile photos and group names. WhatsApp has said more than 95% of its bans are for unauthorised automated or bulk messaging.
In practice the system judges how you message, not what you say. Volume to strangers, speed, identical text, low reply rates and block rates are what it reads.
The enforcement ladder
Bans are usually the last rung of a ladder, and the first two rungs are warnings you can act on.
On the app, the "restricted" state blocks new chats but leaves replies and calls working, and lifts on its own. On the API, a falling quality rating now stops your limit growing rather than cutting it at once, which gives you time to fix things.
Seven habits that get sales numbers banned
Most B2B bans trace back to one of seven patterns. Most of them are ordinary sales habits that look like spam to a machine.
| # | Habit | What it looks like in a sales team | Why it trips detection | Risk |
|---|---|---|---|---|
| 1 | The trade-show blast | A rep imports 400 visiting-card numbers and sends the same brochure to all of them on day one. | High volume to people who don't have your number, identical text, few replies, some blocks. | Very high |
| 2 | The bulk-sender hack | Chrome extensions, GB or mod apps, or scripts that blast messages from the rep's number. | WhatsApp spots modified apps and machine-speed sending. Both break its terms. | Very high |
| 3 | The brand-new SIM | A new hire gets a fresh SIM and starts cold outreach the same week. | New numbers get the least trust, and a sudden spike of messages from one is a classic trigger. | High |
| 4 | The follow-up chain | Three or four nudges to a lead who never replied. | Every unanswered message now counts against a monthly cap, and silence plus repeat messages invites blocks. | High |
| 5 | The bought list | A purchased database of "decision makers" fed into broadcasts. | Nobody on it asked to hear from you. "Didn't sign up" is the block reason that hurts quality most. | Very high |
| 6 | The group sweep | Adding prospects to groups or Communities without asking. | Mass adds and exits generate reports. | Medium to high |
| 7 | The shared number | One number logged in across several people and devices outside WhatsApp's own linked-device feature. | Unusual session patterns. Under India's SIM-binding rule the SIM must stay in the primary phone. | Medium |
One pattern worth naming: on the Business API, a "ban" is usually a slow squeeze first. Quality drops, templates get paused, the account stops scaling, and only repeated problems end in a disabled number.
Where tools like ours fit
We should be upfront here. Leadcues connects to WhatsApp by QR code, and we can't promise a number will never be banned.
What gets numbers banned is the behaviour in the table above: blasting strangers, bought lists, endless follow-ups, machine-speed sending. So we built Leadcues to make that behaviour hard to fall into.
- Replies are never limited. Answering people who wrote to you is what keeps a number healthy.
- A new number can't start with strangers. From the app, it only messages people who have written to that number first, or chats that already existed on the phone.
- First messages to new people are capped per day for each number, so one rep can't run a trade-show blast by accident.
- Sending is paced like a person. Each message shows typing first, and there is a gap between sends. Campaigns go out a few seconds apart, never in a burst.
- Do-not-contact is respected. Campaigns skip anyone marked do-not-contact in the CRM, and a number pauses itself after repeated failed sends.
- No extensions, no mod apps. Your reps keep the normal WhatsApp app on their phones.
- If a number does go down, the pipeline doesn't. Every conversation, note and deal stage sits in the CRM, so you pick up from a new number with full context.
If your plan is bulk marketing to cold lists, use the WhatsApp Business API for that, not us. Leadcues is for teams that sell through real conversations.
Sell on WhatsApp the way it now rewards
A shared inbox on the numbers your team already uses, with every chat tied to a contact and a deal. Free CRM, no card needed.
The 2025 and 2026 rule changes
Five changes in 18 months moved the line between "sales" and "spam". Older ban guides were written before most of them.
| Date | Change | What it means for sales teams |
|---|---|---|
| Dec 31, 2026 (deadline) | India's DoT SIM-binding rule: apps must keep +91 accounts tied to the active SIM in the primary phone. The deadline was extended to Dec 31, 2026, and the six-hour forced web logout was dropped in favour of risk-based logouts. | Shared numbers, SIM-less devices and virtual numbers get harder to run. A rep who leaves takes the working session with the SIM. |
| Jan 15, 2026 | Business API terms bar general-purpose AI chatbots (ChatGPT-style assistants). Bots built for your own sales, support and FAQs are still allowed. | Keep any AI in your WhatsApp flow about your own business. |
| Oct 2025 onward | WhatsApp is testing a monthly cap on messages to people who aren't contacts and haven't replied. A pop-up warns you near the cap, and after it, messaging new people pauses. | Unanswered follow-ups now have a direct cost. Messages that get a reply don't count. |
| Oct 7, 2025 | Business API messaging limits move from each number to the whole business portfolio. The Flagged quality state is gone; a low rating stops your limit growing instead of cutting it straight away. | One careless campaign on one number affects every number you own. |
| 2024 to 2025 | "Account restricted" rolls out: a temporary block on starting new chats, with replies and calls still allowed, as a warning before a ban. | You often get one warning. Treat it as the last one. |
The prevention playbook
One rule sits behind everything below: get the other person to start the conversation, or to reply to it. The rest is detail.
Get permission before the first message
- Let the lead message you first: Click-to-WhatsApp ads, a wa.me link or QR code on your site, your visiting card and your stall standee.
- At events, ask "Can I WhatsApp you the brochure?" and send only to people who said yes.
- Never upload bought or scraped lists. One "didn't sign up" block hurts more than ten ignored messages.
Write messages that invite a reply
- Open with a question, not a PDF. "Reply 1 for the price list, 2 to book a call" turns a broadcast into a conversation.
- Personalise the first line with the lead's company or what you talked about. Identical text to lots of strangers is a strong spam signal.
- One follow-up, then stop. Move the lead to a call or email after that.
Pace your numbers
- Warm up new SIMs: start with existing customers and warm leads, and build volume over days, not hours.
- Spread outreach through the working day. No bursts of hundreds of messages in minutes.
- Respect quiet hours and cap marketing frequency. Two a week is a common ceiling.
Use the official API for marketing at scale
- Bulk marketing, repeat promotions and automated sends to cold lists belong on the WhatsApp Business Platform (the API), with verified business details and approved templates.
- Never run bulk senders, Chrome extensions or mod apps on a number you can't afford to lose.
- Pick the right template category. Marketing copy submitted as utility gets rejected or penalised.
Watch the early warnings
- On the API: check the quality rating (green, yellow, red) and block reasons in WhatsApp Manager every week, and pause a campaign the moment it turns red.
- On the app: the "account may be restricted soon" banner, or the warning about the unanswered-message cap, means stop cold outreach on that number now.
Plan for the day a number dies
- Keep conversations, notes and deal stages in a CRM, not only in the rep's phone.
- Register business numbers to the company, not the rep, and keep a warmed-up backup number for important lines.
- Don't share one number across lots of devices outside WhatsApp's own linked-device feature.
If a number gets restricted or banned
Work out which state you're in first, because the right move differs.
- Read the exact message. "Your account is restricted right now" is a timed warning: you can still reply and call, and it lifts on its own. "This account is not allowed to use WhatsApp" is a ban. "Register your number" is usually a SIM or session issue, not a ban.
- Stop whatever caused it. Pause campaigns, uninstall unofficial apps, and stop cold outreach on every number in the team, not just the affected one.
- Appeal once, honestly. Use "Request a review" in the app (or Meta Business Support, or your provider, for API numbers). Explain the business use and what you changed. Repeat appeals don't help, and only a small share succeed.
- Recover the pipeline. Pull the lead list and open deals from your CRM, and tell active leads from a working number, or by email, that you have a new line.
- Restart slowly. A replacement number is new and low-trust. Warm it up with existing customers first, and don't repeat whatever caused the ban.
What this means for sales leaders
A WhatsApp number is now infrastructure, and it needs an owner. Four things follow.
- Revenue risk is concentrated. If deals live in one rep's chats, one ban takes out a slice of the pipeline and the context behind it. The fix is a system of record, not a better appeal.
- Outreach has to change shape. Cold, one-way WhatsApp blasts get more expensive every quarter. Lead capture that starts with the buyer (ads, links, QR codes, inbound forms) plus fast replies is what lasts.
- Choosing a tool is a risk decision. Ask every vendor how they connect to WhatsApp, what they do to stop risky sending, and what happens to your data if a number goes down. Here are our answers.
- Reply speed protects the number. Conversations that get answered keep a number healthy. A team inbox with assignment and follow-up reminders helps deliverability as much as productivity.
The teams that get the most out of WhatsApp in 2027 will treat it like a relationship channel and measure it like one: reply rates, response times and opt-ins, not messages sent.
Sources
Figures checked on November 4, 2026. We used vendor blogs to explain how Meta's rules work in practice; check Meta's own documentation before quoting exact limits.
- WhatsApp bans 54 lakh Indian accounts in April 2026 (Republic World)
- WhatsApp bans 59.78 lakh accounts in March 2026 (Ground News, summarising NEWS9)
- WhatsApp bans over 98 lakh accounts in June (Free Press Journal)
- WhatsApp bans over 9.7 million accounts in February 2025 (Deccan Herald)
- WhatsApp banned over 2 million Indian accounts in August (Communications Today: the 95% figure and detection signals)
- WhatsApp bans more than 85L accounts in September (Siasat: the three stages of detection)
- WhatsApp will curb messages people and businesses can send without a response (TechCrunch)
- WhatsApp moves to temporary message restrictions (Candid.Technology)
- WhatsApp quality rating and messaging limits (Leapstream, citing Meta's docs)
- WhatsApp Business API updates 2026 (Manifest)
- Not all chatbots are banned: WhatsApp's 2026 AI policy (respond.io)
- Government drops WhatsApp Web logout rule, extends SIM-binding deadline (Beebom)
- WhatsApp SIM-binding rule explained (GoTrust)
- WhatsApp ban for automation: which tools are safe (Kraya)
- Messaging limits (Meta for Developers)