Scheduled Publishing for WeChat Official Accounts on a Phone

A team that makes local-life content runs seven WeChat official accounts, split by district.

They have the content. They cannot get it all out. The editor lays out seven pieces in the morning. What is left is picking up a phone, switching accounts, finding the draft, and tapping mass send. One round takes more than forty minutes. Sometimes the person is busy when the time comes, the post misses the slot, and it slides to the next day.

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

It does. Scheduled mass send covers sending at the set time. It still leaves the seven-account rotation. Walking through seven accounts still costs the same forty minutes.

Split the flow first

Publishing an official account splits into two stretches.

One is content preparation: choosing the topic, writing the piece, layout, images, and checking. That takes judgment, and most of it wants a large screen, so the desktop back office is the comfortable place. When it is laid out, save it as a draft.

The other is the publish action: pick up the phone, open the official-account assistant, switch to the target account, find that piece in the draft list, preview it, set the send method, and confirm mass send. That stretch needs almost no thinking. It is the same sequence, over and over.

Stage	Who should do it	Note
Topic, writing, layout, images	Person	Needs judgment and a large screen
Saving the draft	Person	Finished once 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 later review

The person owns the first half. The computer owns the second. Publishing time for seven accounts drops from forty minutes to a few. You dispatch seven tasks and wait for the results.

Where multiple accounts get messy, and how Channels fits

Running one account is straightforward. The built-in scheduled mass send is enough. The trouble starts with the second account.

Each extra account adds another pass: switch accounts, find the draft again, set the time again. Switching accounts on a phone has its own cost. Sending to the wrong account is more serious than missing the send.

There is also the record. What went out on seven accounts, when it went out, and which piece performed, all held in someone’s head, is a mess after a week. When the work runs through a workflow, the tasks leave a trace in Execution History. Time, device, success or failure: all of it can be looked up.

Bind one phone to one official account. Set the device alias to the account name, such as “South District” or “North District”. Choosing a device at dispatch time is the same as choosing the account, which removes one decision and one chance of switching wrong. Aliases and grouping are covered in more detail in the Devices documentation.

Official accounts and Channels are often run together inside WeChat, and the two formats differ a lot. Readers come to an article for the content. Viewers meet Channels while scrolling. Turning the same article straight into a video usually performs poorly.

The practical version is one topic expressed in two places. The article lays out the argument. The video carries one core point and says it in a minute. The publish actions on both sides then sit in the same kind of flow, and the cost stays lower.

The Channels publish flow was written up separately: WeChat Channels auto publish.

How to set it up, and three things easy to miss

First, lay the material out in the desktop back office and save a draft. Keep the layout off the phone.

Second, install the workstation and the phone-side program from the install selection page, then register the phones, set aliases, and group them. Align each alias with the account name.

Third, on the Conversation page, pick the phone and describe the flow: open WeChat, go to the official-account assistant, switch to the target account, find the draft, preview it, tap mass send. The first time, leave mass send for a person to confirm. A mass send cannot be undone, so this confirmation stays.

Once the flow runs cleanly, save it as a workflow and leave the parts that change each time, such as the draft title, as parameters. Then on the Schedule page, give each account its own time, spaced by ten minutes or so.

A schedule only fires at the set time. Whether the piece should go out is still your decision. Confirm the content yourself.

At the moment the schedule fires, the device has to be online. For a USB connection, the cable and the computer both have to be working. For a wireless connection, the phone-side program has to be running. Confirm these when you set the schedule, before the slot arrives and the device turns out to be offline.

Keep the rhythm from getting too tight. Sending all seven accounts at the same moment makes a failure hard to place: you cannot tell a problem in the flow from a condition on one account. Spread the times a little, and a failure points at a specific phone.

That team later turned publishing for all seven accounts into workflows, each with its own schedule, from 7:30 to 9:00 in the morning, one every ten minutes. The person who handles content says he now only cares whether the writing is good. The publish times are no longer in his head.

With a single official account, the built-in scheduled mass send is enough. With several accounts, and with Channels or other platforms on the same kind of flow, get one account through first and add the rest after that. Installation is in the install documentation.