How BuzzRelay sends messages
BuzzRelay drives a real Chromium browser logged into your WhatsApp account and sends through WhatsApp Web, the same interface you would use by hand. For each recipient it opens the chat, types the message with human-like timing, sends it, waits a random interval, and moves on. Nothing passes through our servers — the sending happens on your computer, from your account.
The mechanism
BuzzRelay ships with its own Chromium browser. When a device is connected, BuzzRelay opens a browser profile for it, loads WhatsApp Web, and uses the saved session from your QR scan. From then on it operates that page the way a person would.
For each recipient in a campaign it:
- Opens the chat for that number.
- Types the message into the input box, character by character, with variable timing.
- Attaches media if the message has any.
- Sends it.
- Repeats for every message in the sequence, pausing by the sequence delay between them.
- Marks the recipient's outcome.
- Waits a random interval within your delay range before the next recipient.
What follows from this
Almost everything else about BuzzRelay is a consequence of this design.
| Because sending is a real browser session… | …this is true |
|---|---|
| Your account does the sending | Replies land in your normal WhatsApp and you can carry on the conversation |
| There is no server in the middle | Your PC must be on and online for a campaign to run |
| Messages are ordinary one-to-one messages | The broadcast-list rule about saved contacts does not apply |
| Each device is a separate browser profile | Accounts never share cookies or state |
| WhatsApp sees a normal client | Pacing and typing behaviour matter — they are what makes it look human |
| It is automation of a real account | It breaches WhatsApp's terms, and numbers can be restricted |
| The page is the interface | WhatsApp Web changes can require app updates |
Typing simulation
With typing simulation on — the default — BuzzRelay types with variable rhythm, occasional pauses and human-like irregularity rather than pasting the text instantly. There is also a typing speed setting so you can make it slower or faster.
The purpose is not decorative. Instant, perfectly uniform input is one of the cheapest things for a platform to detect.
The delays
Two separate delays apply:
- Delay between messages (default 5–15 seconds) — between one recipient and the next, chosen at random within the range each time.
- Sequence delay (default 3 seconds) — between individual messages sent to the same recipient.
Both can be overridden per campaign, so a cautious campaign can use wider gaps than your global default without changing it for everything else.
What is not involved
There is no cloud sending service, no message queue on our servers, and no relay. We never see your contact list or your message content. The only things that reach us are licence checks and update requests.
BuzzRelay also does not use the WhatsApp Business API. It is not connected to Meta's official channel in any way — see WhatsApp Business API vs WhatsApp Web automation.
Why campaigns take a while
Every message is a real interaction with a real page: open the chat, wait for it to load, type, send. That is inherently slower than an API call, and the delays are deliberately added on top. A 200-recipient campaign at default settings takes something over half an hour.
Speeding this up by cutting delays is possible and is exactly the wrong move — the pacing is the protection. See How anti-ban protection works.
When something goes wrong mid-send
Because it depends on a live browser session, a campaign can be interrupted by the session expiring, the phone going offline, the PC sleeping, or the network dropping. When that happens the campaign stops rather than silently skipping people, and recipients not yet reached stay pending so you can resume without double-sending — see Campaign and recipient statuses.
Frequently asked questions
How does BuzzRelay actually send WhatsApp messages?
It drives a real Chromium browser logged into your WhatsApp account through WhatsApp Web. For each recipient it opens the chat, types the message with human-like timing, sends it, then waits a random interval before the next one.
Do my messages go through BuzzRelay servers?
No. Sending happens entirely on your own computer from your own WhatsApp account. There is no cloud sending service and no message queue on our servers, and we never see your contacts or message content.
Does my computer need to stay on during a campaign?
Yes. The campaign runs in a browser session on your PC, so the machine must stay on and online for the duration. Many users run BuzzRelay on a Windows VPS for this reason.
Why is sending slower than an API?
Every message is a real interaction with the WhatsApp Web page — opening the chat, typing, sending — and randomised delays are deliberately added between recipients. That pacing is what makes the activity look human, so shortening it removes the protection.
Last updated: