Keep your number safe

Oxtro is not the official WhatsApp Business Platform and is not affiliated with WhatsApp or Meta. Oxtro cannot prevent a ban, and cannot reverse one. The habits below lower the risk. They do not remove it.

Message people who expect to hear from you

This is the rule that matters most. When recipients block or report a number, WhatsApp notices. Order updates to a customer who just bought something, a login code a user just asked for, a reply to someone who wrote first: these are expected. A promotion to a list of numbers you bought or scraped is not.

• Collect the number yourself, and say at that moment that you will message on WhatsApp.
• Keep a record of that consent.
• Tell people how to stop the messages, and honour it straight away.
• Never send to purchased, scraped or guessed numbers.

Warm up a new number

A number that was registered yesterday and sends hundreds of messages today looks like spam. Give a new number time to look like a real one before you automate it.

• Use the number normally for a while first: a profile name and photo, real conversations, replies coming back.
• Start with a small number of messages a day to people who know you, and raise the volume gradually over weeks.
• Prefer conversations that get replies. A number that only ever sends looks different from one that talks.
• If you see failures or a disconnection, stop and lower the volume instead of pushing through.

What gets numbers restricted

• Cold outreach to people who never gave you their number.
• The same text sent to many people in a short time. Use template variables so messages carry real, per-person content.
• A sudden jump in volume on a number with little history.
• Sending to many numbers that are not on WhatsApp, which is a sign of an unverified list.
• Recipients blocking or reporting you.
• Links to unfamiliar domains or shortened URLs in a first message.

What Oxtro does, and what it leaves to you

• Every message goes through a queue with a per-number send rate, so a burst of API calls does not hit WhatsApp all at once.
• Campaigns are paced. The default is 60 messages a minute and you can lower it per campaign. For a young number, lower it.
• The OTP API has a resend cooldown and per-phone hourly and daily caps, so a form cannot be used to flood one person.
• Oxtro does not check who is on your list or what your message says. That part is yours.

Plan for a disconnection

• Subscribe to the connection.disconnected and message.failed webhook events and alert a person when they arrive.
• Sends to a disconnected number fail with CONNECTION_OFFLINE. Queue them on your side and resume when the number is linked again.
• Keep the phone that owns the number charged and online, and do not log the linked device out from the WhatsApp app.
• For anything critical, such as login codes, have a fallback that does not depend on a single number.