Qwela Blog
Guides

How to avoid getting your WhatsApp number banned when sending from an API

· 6 min read · By JPL365

The most common worry about sending WhatsApp messages from software is simple: will my number get banned? The honest answer is that nobody can promise it will not, including us. WhatsApp decides what looks like spam, it can restrict a number at any time, and the account owner has the final say on whether a message is wanted. What you can do is behave in ways that make restriction much less likely. This checklist applies to any way of sending automated messages, and we built these habits into Qwela as defaults.

Why numbers get restricted

WhatsApp's systems and its users both signal when a sender looks like a spammer. The usual triggers are:

  • Messaging people who do not know you or never asked to hear from you.
  • Recipients blocking or reporting your number.
  • Sending the same message to many people in a short burst.
  • A sudden jump in volume from a number that was barely used before.
  • Messages to numbers that are not on WhatsApp.

1. Only message people who expect it

This is the single most important rule. Order confirmations, payment receipts, delivery updates and appointment reminders go to people who just did something with your business, so they want them. Cold lists, bought contact databases and "I found your number online" messages are how numbers get reported. Collect the phone number and a clear yes at the point of sale or booking.

2. Pace your sending

Humans do not send fifty messages in ten seconds. Spread messages out and use a daily ceiling that fits your real needs. Qwela queues every message and sends them a few seconds apart, with random variation, and enforces a daily limit per account. If you build your own sender, do the same.

3. Make each message useful and specific

Messages with the customer's name, the order number and a real detail look like conversation. Identical promotional text blasted to a list looks like spam. Keep messages short, plain and relevant to something the person did, and avoid long chains of links.

4. Make it easy to stop

Tell people how to opt out, for example "Reply STOP to stop these messages", and honour it straight away by adding the number to a do-not-contact list in your own system. A recipient who can opt out politely will not report you instead.

5. Do not message numbers that are not on WhatsApp

Qwela checks that a number is on WhatsApp before sending and marks the message as failed if it is not, so you never send to an unregistered number. Still, clean your list, and fix typos in numbers at the point of entry.

6. Treat the number like an asset

  • Use a number with real history, not a brand-new SIM that suddenly sends hundreds of messages.
  • Keep it for business notifications, separate from your personal number.
  • Ramp up gradually. If you plan to send 100 messages a day, do not start there on day one.
  • Let people reply. Two-way conversations look very different from one-way blasts.

7. Monitor and have a fallback

Watch for rising failure rates and for the session.logged_out webhook event, which tells you the number was unlinked. Keep another channel available, such as SMS or email, for messages that must reach the customer, so a restriction is an inconvenience and not an outage.

If your number is restricted

  1. Stop sending immediately and find out what changed, such as a new campaign, a bad list or a volume jump.
  2. Use the appeal options inside WhatsApp if it offers them.
  3. Do not respond by spinning up new numbers to keep sending the same messages. That repeats the problem.

When a linked-device gateway is the wrong tool

If you need broadcasts, marketing campaigns, high volume or a number you cannot afford to lose, use the official WhatsApp Business Platform with approved templates. We compare the two honestly in WhatsApp API in Kenya: official Business API vs Qwela.

If your use case is notifications and conversations, you can try Qwela free for 7 days at qwela.jpl365.com.

Keep reading