Eighty accounts, one afternoon gone
A cross-border seller I know runs his WhatsApp marketing out of the Middle East. Eighty WhatsApp Business accounts, each holding a catalog of twenty to thirty SKUs. It is a common shape among cross-border ecommerce sellers with a large account base.
What he dreads every month is not shipping. It is adding new products.
When a new item arrives, he opens the first account, goes into Catalog, and loads the product field by field: name, price, currency, description, image. Then he backs out, opens the next account, and does it again. Eighty accounts at twenty minutes each is more than twenty hours. He usually spreads it over three days, while customer enquiries keep arriving.
His own summary was blunt: it is not hard, it is just that nobody wants to do it. He does not either, so it often slips into the second week, and for those days he answers questions about new stock by sending pictures by hand.
Get the two features straight first
Many people treat WhatsApp Business as a WeChat with products attached. There are actually two separate things inside.
Catalog governs what you sell. Which products sit under the account, at what price, in or out of stock, what the image looks like. This is what a customer sees when they open your profile.
Quick Replies govern what you say. Price, shipping, minimum order, lead time: store each answer as a line, pick one when replying.
The problem sits with Catalog, because it is per account. Eighty accounts means eighty catalogs. Quick Replies, by contrast, can be reused across accounts and rarely need touching once configured.
The two features have completely different maintenance rhythms, so they should be treated separately.
Maintaining catalogs in bulk
The approach is to turn “edit one account” into a repeatable action, then let it run per device.
Start by preparing all assets. Product name, price, description, hero image, gathered into one sheet. Do not skip this. Product details scattered across chat history will produce mistakes.
There is a trap with images: WhatsApp enforces size and aspect limits, so use a square hero image on a clean background. Very tall images get cropped. Resize to spec before uploading, or a large share will come back.
Then run two or three accounts first. Not all eighty. Take two or three through the whole flow and watch for snags. Most problems surface here: an image at the wrong ratio, a price in the wrong currency, a description truncated, the wrong pickup location on one account and twenty listings in the wrong city.
Only then dispatch by device group. Split the eighty into groups and work through them one at a time, checking results after each.
Grouping is not cosmetic. Eighty accounts on one screen means you cannot tell which device failed. Four groups of twenty means a lookup takes seconds.
Building and calling Quick Replies
Quick Replies are the highest-value part of this setup.
Four questions dominate the inbox: how much, what does shipping cost, what is the minimum order, how soon can it ship. Across his accounts those four account for well over half the volume.
Store them as Quick Replies and replying collapses to picking one and sending it. Paired with multi-device replies, you can fill different content across several devices at once, so accounts serving different regions get the right shipping line.
One detail matters: keep ordered and random sending separate. Replies with a progression, such as asking about requirements then proposing an option, should send in order. Alternative phrasings of the same answer, such as greetings or common questions, should send at random. Mixing them produces replies that do not follow.
Which replies a machine should send
Draw this line clearly or it will cause problems.
Price, shipping, minimum order and lead time: a machine is more consistent than a person. Customers want accuracy and speed, and people tend to paraphrase, drop details, or contradict earlier answers.
Negotiation, complaints, returns and chasing orders: these must reach a human. They need judgement and tone, and a machine will drive customers away.
His arrangement is straightforward. Support staff watch the message list, pick a Quick Reply for standard questions, and take the rest themselves. Replying now takes less than half the time it did, and customers get consistent wording instead of different answers from different accounts.
When iEasyRun takes over
Everything above is daily work with a fixed flow, and an iOS cluster control setup handles it well.
But he ran into a different kind of job: a monthly catalog audit. Comparing the products in eighty accounts against the warehouse stock sheet, looking for delisted items, price changes and missing images. It happens once a month, and writing iOS automation scripts for it does not pay: scripting takes longer than doing it by hand.
That work went to iEasyRun. The difference is that no script is needed: describe the job and it works from the screen. One-off, low-frequency work with a flow still moving is far cheaper to describe than to script.
In practice the split looks like this. Daily catalog sync and Quick Replies run on iOS cluster control, fixed and scheduled. The monthly audit and ad-hoc price checks go to iEasyRun as a single sentence. Both run on the same phones, and the USB HID route keeps the whole thing no-jailbreak, with no signing or developer account required. Multi-account operations at this scale only hold together because the fixed parts are handled: without WhatsApp automation on the standard questions, the hours go straight back into typing.
Lines not to cross
First, catalog content has to be true. Price, stock, specifications: say what is actually there. Efficient bulk maintenance is no reason to load in placeholder data.
Second, do not use Quick Replies to inflate volume. They exist to answer people, not to pad message counts. That approach takes the accounts down with it.
Third, do not switch logins in rapid succession. Eighty accounts cycling through one device is an obvious anomaly. Spread them across devices by group, each handling only its own set.
To close
Back to that afternoon. His restocking now runs like this: assets prepared the day before, eighty accounts dispatched in four groups in the evening, results reviewed the next morning, and the few failures rerun.
The time he saves goes somewhere more valuable: writing descriptions that read like a person rather than “premium product, quality guaranteed”.
Tools can take over repetition, but what customers remember is what you said. For the wider picture, see Apple cluster control for WhatsApp; for putting many device screens on one display, see iOS no-jailbreak screen mirroring.
About EasyClick: A phone automation AI-agent platform covering Android no-root, iOS no-jailbreak (proxy / Bluetooth HID / OTG HID) and HarmonyOS Next, offering script development, Apple cluster control, local central control & mirroring, and cloud control systems. → Explore all products
Ready to build it for real?
Every approach in this article can be built on the EasyClick phone automation platform — full documentation, developer tools and cluster/cloud-control products, free to try.