Scheduled Publishing for WeChat Official Accounts on a Phone

A team producing local lifestyle content runs seven WeChat official accounts, split across different districts.

Their problem was not a shortage of content. It was that they could not get it out. An editor laid out seven articles in the morning, and the rest of the job was picking up a phone, switching accounts, finding a draft, tapping mass send, seven times over. The whole loop took over forty minutes. Sometimes a person was busy when the time came, so it slid to the next day.

I asked why they did not hand that step over. Their first answer was that the back office already has scheduled mass send.

It does, but scheduled mass send solves getting one post out at one time. It does not solve rotating through seven accounts. Seven passes still cost the same forty minutes.

Take the flow apart first

Publishing an official account splits into two stages.

One is content preparation: choosing the topic, writing the piece, layout, images, proofreading. That takes judgement and mostly takes screen space, which makes the desktop back office the right place for it. It ends with a saved draft.

The other is the publish action: pick up the phone, open the account assistant, switch to the target account, find that article in the draft list, preview it, choose the send method, confirm. That stage requires almost no thinking. It is just repetition.

Stage	Who should do it	Note
Topic, writing, layout, images	Person	Needs judgement and screen space
Saving the draft	Person	One pass in the desktop back office
Opening the assistant, switching accounts	Computer	Fixed actions, suited to a template
Finding the draft, previewing	Computer	Fixed order
Setting the send method, confirming	Computer	Keep manual confirmation the first time
Recording the result	Computer	Which account and when, for review

With that split, the person owns the front half and the computer owns the back half. Once the division is clear, publishing seven accounts drops from forty minutes to a few. You dispatch seven tasks and wait for the results.

Multiple accounts are where the trouble really comes from

One account is simple. The built-in scheduled send is entirely adequate. The trouble starts with the second account.

Each additional account adds another pass: switch, find the draft again, set the time again. And switching accounts on a phone carries its own cost. Switching to the wrong one and posting there is worse than not posting at all.

There is also a hidden cost in record keeping. What went out on seven accounts, when, and which pieces performed, is not something anyone retains reliably. Running through workflows leaves a trace in Execution History, showing the time, the device, and whether it succeeded.

My suggestion is one phone bound to one official account, with the device alias set to the account name, such as North District or South District. Choosing a device then means choosing an account, which removes both a decision and a chance of switching wrong. Aliases and grouping are covered in more detail in the Devices documentation.

Pairing with Channels

Official accounts and Channels often appear together in the WeChat ecosystem, but the formats differ. Readers come to an article for the content. Viewers watch Channels while scrolling. Turning an article directly into a video usually performs poorly.

The practical approach is one topic expressed twice: the article lays out the full argument, and the video carries a single core point in about a minute. Managing both publishing flows through one setup then keeps the cost down.

The Channels publishing flow was covered separately and is worth reading alongside this: publishing to WeChat Channels.

How to set it up

First, lay out the material in the desktop back office and save a draft. Do not do layout on a phone. That is volunteering for extra work.

Second, install the workstation and phone-side program using the install selection page, then scan the phones in, alias them and group them, with aliases matching account names.

Third, on the Conversation page, pick the phone and describe the flow: open WeChat, go to the account assistant, switch to the target account, find the draft, preview it, tap mass send. Keep the send for manual confirmation the first time. This step is not optional, because a mass send cannot be undone.

Once the flow runs cleanly, save it to Workflows with draft title left as a parameter. Then set different times per account on the Schedule page, spaced by ten minutes or so.

Three things easy to overlook

First, a schedule only triggers. It does not judge whether a piece should go out. Confirm the content yourself.

Second, the device must be online at the moment the schedule fires. For USB devices, the cable and computer both need to be working. For wireless, the phone-side program needs to be running. Confirm these when you set the schedule rather than finding an offline device when it fires.

Third, do not compress the rhythm too tightly. Firing seven accounts at once looks efficient, but when something breaks you cannot tell whether the flow is at fault or one account is in a particular state. Spreading the times slightly makes it obvious which device is the problem.

Back to that team. They turned the publishing for all seven accounts into workflows, each with its own schedule, running from half past seven to nine in the morning at ten minute intervals. The person handling content now says he only thinks about whether the writing is good, and publishing times have left his head entirely.

With a single official account, honestly, the built-in scheduled send is enough. But if you run several accounts and want them on the same flow as Channels or your other platforms, get one account working first and build from there.