Most WhatsApp marketing tools sell speed. They fire hundreds of identical messages in a few minutes from a number with no history, and the number is limited or banned within days. The tool is not saving you time; it is spending your number.
Spun takes the other side of that trade. It connects to the number you already use, sends one conversation at a time with a real gap between each, holds a new number back for its first week, budgets first contacts per day, and prefers campaigns where the customer messages you first. This page lays out the limits WhatsApp is understood to enforce, what Spun does about each of them, and why running several numbers is a strategy rather than a workaround. It also says plainly what none of this can do.
What WhatsApp marketing looks like in Spun
Everything runs on the number your business already answers, linked the way WhatsApp Web links a computer, with the team layer on Spun's side. Campaigns leave from that number, replies come back to a shared inbox where the team answers them, and the customer sees an ordinary conversation.
- Broadcast campaigns: one message to many people, sent one conversation at a time at a pace you choose, with audiences built from labels and segments rather than an uploaded list of strangers.
- Scheduled messages: write it now, send it at the right hour, per conversation.
- Spin-to-win lead games: a prize wheel on your own page where, by default, every entrant has to message you on WhatsApp before the wheel unlocks.
- Replies in one shared inbox, assigned and answered by the team, with each contact's history in one thread.
- Several WhatsApp numbers on one account, with a campaign able to split across them.
Related: How the broadcast controls work in detail · The spin-to-win wheel
The limits WhatsApp enforces, as far as anyone can tell
WhatsApp publishes no number for the app. It judges behaviour: how fast messages leave, how many go to people who never saved you, how much of it is identical, and how many people block or report you. What follows are the thresholds people who run many business numbers report, not figures WhatsApp has ever confirmed, and they are the assumptions Spun's defaults are built around.
| What WhatsApp is understood to score | What it looks like in practice | What Spun does about it |
|---|---|---|
| Velocity | Under about 30 messages an hour is reported as safe; above 60 the risk rises sharply. Even a brief burst of five a minute is reported to draw attention. | Paced sends with a random gap inside the range you chose, a server-side cap on top, and quiet hours during which nothing leaves. |
| A new or quiet number that starts blasting | Under about 200 a day until a number has three weeks of history, and 20 to 50 a day on a brand-new one. | A warm-up tier of about three messages a minute for the first week, and a daily first-contact budget of 50 while the line is under 30 days old, 150 after. |
| Unsaved recipients | Messages to people who never saved your number, especially many in a row. | Audiences from the workspace, a first-contact budget that defers the overflow to the next day, and a wheel that makes the customer message you first. |
| Identical content | Two hundred messages of the same length, link, photo and attachment in a short window look like a broadcast whatever the text says. | Per-recipient personalisation, an opt-out footer, and a slight per-recipient variation on an image going to more than 20 people. |
| A metronome | A perfectly regular interval between sends is itself a signal. | Spun picks a random value inside the pace range each time, and adds jitter on the server. |
| Blocks, reports, and a message after a stop | A customer who said stop and received three more messages. | Auto-slow watches replies and single ticks and steps the pace down; the consent half is yours, and nothing here changes that. |
| Where the connection comes from | A session reaching WhatsApp from shared Wi-Fi or a datacenter address far from the phone. | The connection region is checked when you connect, and Self Proxy runs the session from your own internet. |
Reported thresholds, not published ones. Spun's defaults sit below the reported safe values on purpose; a higher margin reflects lower risk, it does not remove it.
Related: The 14 signals WhatsApp scores before it bans a number · Sending bulk WhatsApp messages without getting banned
What Spun does about each of them, in the order it happens
- 1
Before you send: the preflight
A panel shows the run as WhatsApp would see it: recipients, how many are first contacts, how many are unsaved, whether the body is identical for everyone, links, the send window, the duration at the pace you picked, the line's age and its Sending Health. Four hundred recipients at a conservative pace is a couple of hours, and seeing that before you press send is usually what stops someone reaching for the fastest option.
- 2
The pace is a range, and the gap is random
Conservative leaves fifteen to thirty seconds between messages, normal eight to fifteen, and the fastest setting three to eight and is flagged as one to use only on an established number in good standing. The server caps the pace to what the channel can safely take, adds extra jitter on top, and holds sends entirely during quiet hours.
- 3
A new number is held back
For the first week after a number is connected its send rate is held to a warm-up tier of about three messages a minute, whatever pace the composer offered. New contacts are budgeted separately: 50 first messages a day while the line is under 30 days old and 150 after, with the overflow deferred to the next day, never dropped.
- 4
While it runs: Auto-slow
After 40 sends, if fewer than 15% of recipients have replied within 48 hours or more than 30% of sends are sitting on a single tick, the pace steps one preset slower and stays there. It never pauses a run by itself; the second time it fires it suggests you consider pausing.
- 5
If the line is restricted
If three first contacts in a row fail while existing chats still deliver, Spun treats the line as restricted for up to 24 hours and defers new-contact sends to the next send window rather than pushing through. A disconnect mid-campaign stops the run.
- 6
Afterwards: Sending Health
A 0 to 100 score per line built from what Spun can observe: replies, sending bursts, the share of new contacts, unanswered chats, single-tick sends, line age and disconnections. Healthy is 80 and above, Watch 50 to 79, At risk below 50. It is advisory: it never blocks a send.
Every guard is optional. Managers can switch any of them off per line in Sending preferences, and Expert mode lifts them all at once. Two things stay on regardless: the platform rate limit and the campaign daily limit.
The safest campaign is the one where they message you first
Every threshold above is about outbound first contact: a number writing to people who never wrote to it. A conversation the customer opened is a different thing entirely. There is no unsaved recipient, no cold first message, and your follow-up is a reply inside a chat they started.
That is why Spun's lead wheel works the way it does. You publish a spin-to-win page on your own hostname, and by default a participant has to send your business a WhatsApp message containing their entry code before the wheel unlocks. Every completed entrant is a contact in your inbox with a conversation already open. The participant is always the one who presses Send; Spun never writes to an entrant first.
The same logic applies to a QR code on the counter, a wa.me link on the website, or a "message us" button in an email. Build the list from people who reached you, then market to the list.
Related: Spin-to-Win Lead Games · WhatsApp marketing without getting banned: the playbook
Several numbers as a strategy, not a workaround
Every limit above is per number: the hourly and daily figures, the warm-up week, the first-contact budget, the reputation. A business that needs to reach more people than one number can safely reach has a choice between pushing one number past its limits and spreading the same volume across several numbers that each stay inside them. The second is the whole point of running more than one line.
With more than one WhatsApp number connected, the campaign composer asks which line should send. You can pick one, or choose "Split across lines" and let several carry it: "Take turns" alternates recipients between them, "By percentage" gives each line a share, and "Match country" sends each recipient from the line whose country matches theirs, with a fallback line for everyone else. Each line keeps its own pace, its own first-contact budget and its own quiet hours, and the campaign shows progress per line.
Two things follow from the per-number rules. Connect a second number weeks before the campaign that needs it, because a new line spends its first week in the warm-up tier and its age counts towards Sending Health until 90 days. And keep each line's audience coherent: a line that only ever talks to customers in one country, from a connection in that country, has a cleaner history than one that talks to everyone from everywhere.
Splitting shares the volume; it does not change what WhatsApp thinks of the content. Three numbers sending an unwanted message are three numbers at risk, not one number at a third of the risk.
Where the connection comes from matters too
Spun connects to your number the way WhatsApp Web does, as a linked device. That session lives on a server, and that server has an address somewhere in the world. A session reaching WhatsApp from a datacenter far from where the phone is, or from an address shared with many other businesses, is one of the signals the ban guides describe.
Spun checks where the connection comes from when you connect and warns when the two stop agreeing. Self Proxy runs the session from your own internet, so WhatsApp sees the connection arriving from where your business actually is. For a business running several numbers in several countries, "Match country" on the campaign and a connection in each country are the two halves of the same decision.
What this is not, and what it cannot do
- This is not the WhatsApp Business API. There are no pre-approved template messages and no per-message fee, and equally no official bulk-sending allowance. The API route exists, and the integration page explains when it is the better choice.
- Consent is not optional. Messaging people who never opted in is the single fastest route to a restricted number, whatever pacing you use.
- Spun can slow you down but cannot make an unwanted message wanted. Pacing reduces the operational signals, not the complaints.
- Sending Health is Spun's estimate from observable behaviour, not a number WhatsApp publishes. A higher score reflects lower risk; it does not remove it, and nothing on this page promises immunity.
- A paced campaign takes real time. Hundreds of recipients is hours, not minutes, and that is deliberate.
Related: Do you need the WhatsApp Business API? · What Spun will not let you send