# Messaging customers on WhatsApp without losing your number > WhatsApp does not ban commercial messages, it bans accounts that behave like software. What Kanz refuses to do, the guardrails you set yourself, and why the card stays the safest channel. - Source: https://usekanz.com/en/blog/whatsapp-customers-without-a-ban - Language: en - Other languages: [ar](https://usekanz.com/ar/blog/whatsapp-bidoon-hazr), [fr](https://usekanz.com/blog/whatsapp-clients-sans-bannissement) - Format: Markdown, generated from the same source as the page. - Published: 2026-08-02 - Author: Kanz - Topics: WhatsApp, Follow-ups, Product - Reading time: 4 min WhatsApp does not ban commercial messages. It bans accounts that behave like software: bursts, texts identical down to the character, instant sends with no typing time, messages at three in the morning, and a brand new account firing off three hundred messages the day it is set up. What protects your number is not what your messages say, it is their rhythm. It is worth saying plainly, because what goes wrong is not an integration breaking. It is the number your business runs on, the one on your shopfront and in your customers' phones, disappearing. There is no support desk, no appeals process that works reliably, and no second chance. ## What Kanz does between two messages It waits. Every send is separated from the one before it by a pause that is never the same twice, and the queue stops regularly to take a longer breath. A freshly linked number starts slower still, and earns its rhythm over its first week rather than on its first day. The exact values are not published, and the absence is deliberate. A precise table of pacing reads both ways: it reassures the honest shopkeeper and it doubles as an instruction manual for whoever wants to blast a personal number at volume. What concerns you fits in one sentence, and it holds whatever your plan: the real rate towards your customers is a few messages a minute at best, and nothing you set raises it. The gap between two messages is **drawn at random** rather than fixed. A regular interval is easier to recognise than a long one: a machine sending at a constant interval is a machine, whereas a person replying to their messages leaves uneven holes. It is the variation that does the work, not the slowness. ## One send at a time, per business Sending is **serialised per business**. Each business has its own session, named with its identifier and never shared, and two follow-ups launched at the same time cannot interleave into a burst. Without that, two campaigns that are each fine on their own produce together exactly the behaviour that takes an account down. ## The three things Kanz refuses to do **No groups.** The address of a WhatsApp group ends in `@g.us`, and the function that builds a recipient throws when it sees one. There is no setting to allow it. **No bulk sending.** The gateway in use does expose a bulk send function. Kanz does not use it, for two reasons: its default pacing is more aggressive than ours, and a bulk send does not leave one line per recipient, so nobody knows any more who received what. **No automatic retry.** When a send times out, we do not know whether it arrived. Retrying blind means sending the same message twice to the same person, which is at once the surest way to irritate them and a textbook automated behaviour. The send is marked as failed and it waits for a decision. ## The pacing is only the floor Everything above sits underneath your own rules, not in place of them. By default, Kanz does not contact the same person more than **2 times in any rolling 30 days**, does not send more than **50 messages a day**, and sends only between **10:00 and 21:00** on the local time of your business. Those three numbers are yours: they are written in your panel, you can see them, you can change them. They are promises made to your customers, not technical tuning. You can raise them, within limits: at most 10 contacts per person per month, and 500 sends a day. Those bounds are not decorative caution. A business owner who sets 5,000 sends a day loses their number, loses their channel, and blames the software. A ceiling the product refuses to go past is a more honest position than a free text field with a warning next to it. And underneath your 500 there is still a wall you cannot move. The pacing layer has no checkbox, it appears nowhere in the settings, and even on the most generous plan a business cannot push a recent session beyond its ramp-up. ## The best WhatsApp message is often an updated card Updating the card in your customer's wallet costs **no credit** and carries **no risk of a ban**, because it goes through no messaging service at all. A WhatsApp costs 1 credit, an email 0.2. When an updated card is enough to say what you have to say, that is what should go out, and it is what Kanz offers first. It is also why the pricing is shaped the way it is. The detail is on the [pricing page](/en/pricing), and how the card works in the wallet is described in [this article](/en/blog/wallet-loyalty-card). ## If your number gets restricted anyway It happens, and you want to know what follows before it does. The session moves into a "banned" state, sends stop for that business, and nobody automatically recreates a session on another number: that is how one ban becomes two. What comes next happens over email and over the wallet cards, which never depended on WhatsApp. The simple rule to keep, if you keep only one: a channel that belongs to somebody else can be taken away from you overnight, and a card that lives in your customer's wallet cannot. ## Create an account The trial runs 30 days and asks for no card. - [Sign up](https://usekanz.com/signup) - [Merchant panel](https://usekanz.com/panel)