MationX
Sending through the API 4 days after go-liveSee the case

WhatsApp phone farm: warm-up and sending

New numbers warmed up between your own phones, then sending from your backend with a callback for every message, inside the real WhatsApp app.

What is a WhatsApp phone farm?

A WhatsApp phone farm is a group of phones, each with its own WhatsApp number, that warm up new numbers and send messages on a schedule or on request from your system.

It is how a business sends from real numbers in the real app, with real devices behind them, rather than through a template-only API.

How do you warm up a new WhatsApp number?

Gradually and in conversation: chats and calls between the farm's own phones first, one more contact a day, read delays and quiet hours, so a new number behaves like a person's.

MationX runs the ramp per group of phones and shows it in one control sheet you can change.

How does sending from your backend work?

Your server calls one HTTP API, a phone in the farm sends the message in the real WhatsApp app, and your server gets a callback with the result.

A 202 means accepted, a 429 means that phone's queue is full, and a 504 means the phone is offline and nothing was sent, so your system always knows what happened.

What happens when a number gets restricted?

It is taken out of rotation before it drags the rest of its group down, and you see it in the log; the group carries on without it.

WhatsApp Business API vs a phone farm

The official Business API is the right tool for opted-in customer messaging with approved templates. A phone farm is for work the API does not cover: warming up numbers, ordinary conversations, and accounts that have to be real app accounts.

Own SIMs or cloud phones?

WhatsApp numbers need SIMs for registration, so most WhatsApp farms use phones with their own SIMs. Where a number is already registered, cloud phones can run the same flows.

What is in the control sheet?

One Google Sheet for the fleet: the numbers, their groups, each one's ramp and daily cap. Change a cell and every phone follows, so you steer the farm without logging into anything.

Real example: a WhatsApp farm in production

A marketing company with fresh WhatsApp accounts asked for warm-up on their real phones and a way for their backend to send. It was built and proven on two of their phones, rolled out box by box on stock Samsung phones, and their backend was sending through the API four days after go-live.

Over 19 days that farm ran 135,099 automation runs and 1.73 million steps on screen at 99.8% run success. The full numbers are on the homepage, and the box phone farm page covers the hardware side.

How does MationX run a WhatsApp phone farm?

We build the WhatsApp flows for your accounts, prove them on two of your phones, then roll them out to the rest of the farm, and keep them running after that.

Every phone is watched, every run is logged step by step, a restricted account leaves rotation, and fixes after app updates are part of the monthly. You see the whole fleet in one place, and your backend can trigger any phone through one API with a callback. The steps are the same whether the phones are yours or rented in the cloud.

What does a WhatsApp phone farm cost?

The automation is a one-off pilot from $1,000, then from $300 a month to run, monitor and fix the farm.

The monthly grows with the farm and the price per phone drops as it does; the pricing page has a slider for the monthly total. Phones, SIMs, proxies or cloud phones stay on your side, on your own accounts, and the cost calculator adds them up for your farm.

Everything a person would do on the phone. Built for your apps, on your schedule.

03
11
07
02
05
09
07:00Next session 09:00
00061218quiet 23–07

Account warm-up

New numbers ramp up like real people: chats and calls between your own phones, one more contact a day, read delays and quiet hours.

11 · Reply to chats9 of 9 on time
03
11
07
06121823

Daily activity

Posting, watching, replying, on a schedule per phone with a daily cap.

POST /sendto: +1 415 555…callbackwaitingdelivered

Sending from your backend

Your backend calls one API, a phone sends it, and a callback confirms it.

GroupRampDaily cap
Group A · 6 phones+1 / day25
6 phones updated

One sheet for the fleet

Numbers, ramps and caps in one sheet. Change a cell and every phone follows.

5 accounts healthyRestricted, out of rotationSpare number in, group back to 5

Ban detection

A restricted account leaves rotation before it drags the rest of the group down.

Opened WhatsApp BusinessSent 14 messagesNew pop-up after updateStep updated, run retriedFixed, back to sending

Kept alive

Apps update and steps break. Every run is logged, and fixing it is our job.

A farm in production. From the first message to sending.

  1. 1

    The ask

    A marketing company with fresh WhatsApp accounts. Warm-up on the real phones, and a way for their backend to send.

  2. 2

    Built and tested on two phones

    Chats and calls inside each group, a daily ramp and ban detection, proven on two of their phones first.

  3. 3

    Rolled out box by box

    Stock Samsung phones in their own boxes, in groups that warm each other up three times a day.

  4. 4

    Sending

    Four days after go-live, their backend was sending through the API, with a callback for every message.

One client, 26 Sep to 14 Oct

135,099

automation runs

99.8%
run success
1.73M
steps on screen
3×
warm-up sessions a day
4 days
go-live to sending

From a message to a running farm. A call whenever you want one.

60 phones, short video apps, daily tasks10:41Got it. Price within a day.10:58

01

Tell us the job

One message about what the phones should do. A price within a day.

Tested on yours

02

We prove it on two

We build it on two of your phones, and you watch it work first.

Installing · 18/18Live on the fleet

03

We roll it out

You give us fleet access. We install the app and turn every phone on.

Fixed the same day
MTWTFSS
Monitored every day

04

We run it

Monitoring, fixes after every app update, changes as the farm grows.

Questions. About WhatsApp farms.

Something we didn't cover?

Tell us what your farm runs and what it should do. You get an answer within a day, from the person who would build it.

No. It works inside the real WhatsApp app on each phone, so no API approval or templates are needed.

Yes. One HTTP API, a callback for every message.

No. Phones, SIMs and proxies stay on your side, on your own accounts.

Warm up and send from real numbers

Tell us what the numbers should do. One number within a day.