Post one video, then two more steps
A creator I know runs three channels for YouTube marketing, all YouTube Shorts, publishing nine to twelve a day. Running multiple YouTube channels means the upload is only part of the job.
He mentioned one detail early: the upload is not the annoying part. The cleanup afterwards is.
After each Short goes out he does two more things: add a first comment from his own account and pin it, carrying hashtags and a short prompt, then file the video into the matching playlist.
Nine videos means eighteen follow-up actions. And they have to happen straight after publishing. Do them the next day and the comment has already sunk.
“By the seventh one I genuinely cannot remember which of the earlier ones already has a pinned comment.”
Why mobile upload matters
Start with why it happens on the phone at all.
A video uploaded through the web does not always travel the Shorts classification path. The platform judges on duration, aspect ratio and upload route, and mobile upload is the most direct route.
The second reason is that the follow-up entry points live elsewhere on mobile. First comments, pins and playlists sit in different places on web, and most of that work is smoother in the app. Since the actions happen on the phone anyway, do the whole sequence there.
The rules have been adjusted several times, so check the current official figure before a bulk run. Prepare assets a little inside the limit rather than sitting right on it. Something sitting exactly on the line has to be redone the moment the rule tightens.
Staging bulk uploads
Uploading splits into prep, upload and confirmation.
Prep happens the day before: vertical video, thumbnail, title, description and hashtag set into one sheet. Preparing assets on a phone is awkward; finish it on a computer and move them over.
Uploads are staged by channel group. Three channels, three groups, each with its own time slot. Never keep one channel signed in on several devices at once, but different channels can share one central control for scheduling as long as the devices stay separate.
Confirmation is not optional. A failed Shorts upload sometimes raises no error at all and simply sits in drafts, and the missing video surfaces a day later. A habit of checking the execution record the next morning catches these early.
Pinned comments: one line, why automate it
His first comment is fixed: a short prompt plus three hashtags.
Fixed content means two things at once. It needs no judgement, and it has to happen on every single video. That is exactly the profile worth handing over: repeated, fixed, and costly to forget.
The implementation is small. Store the comment as a configuration value and add one step to the upload flow: post the comment, then pin it. Every subsequent video carries it automatically.
One line not to cross: off-platform links in comments are sensitive. Many channels put a promotional link in the first comment, which is among the more easily actioned patterns. Safer to use an in-platform prompt such as “full version on the channel page” or plain hashtags, and keep any link somewhere fixed on the profile.
Playlists and filing
A playlist is not required, but there are two practical benefits.
First, viewers who finish one video can continue into related content. The Shorts feed is random, and a playlist gives them somewhere to go next.
Second, you can compare series against each other when reviewing performance. Three months later, deciding whether series A or series B did better means going through videos one by one without playlists.
The action itself is fixed: content theme maps to a fixed playlist. Make it a step in the flow and it happens with the upload.
Where iEasyRun fits
Everything above is daily work with a fixed flow, which is what an iOS cluster control setup handles.
He then ran into a different category: launching a temporary series. Say a three-part tutorial where the covers, hashtags and playlist are all new, and it happens once. Writing iOS automation scripts for a run that happens once does not pay.
That work went to iEasyRun. No script: describe the job and it works from the screen. One-off work with an untested flow is cheaper to describe than to build.
The split now is: daily Shorts uploads run on iOS cluster control, grouped by channel, scheduled, with the pinned comment attached automatically; a temporary series launch becomes a sentence to iEasyRun. Multi-account operations of this shape run comfortably over the no-jailbreak USB HID route, with both tools sharing the same phones. YouTube automation here is not about uploading faster, it is about the two steps after the upload never being skipped.
Lines worth keeping
Do not use comments to manufacture engagement. A first comment is a prompt, not a way to have several accounts pad the numbers on the same videos. That pattern is easier to detect here than almost anywhere.
Keep the material your own. Shorts carries heavy recommendation traffic, and reuploaded content is easy to identify, with consequences that land on the whole channel.
Do not spike the publishing rate. A channel going from three a day to thirty overnight is itself a signal. Scale up gradually, because multi-channel operations suffer most from one oversized move.
To close
He now checks records the next morning: upload status for nine videos, whether the pinned comment landed, whether playlists are right. Five minutes, against the old problem of forgetting by video seven.
The time he recovered went into separating the three channels by content direction instead of publishing the same material across all of them. Audiences followed one and had no reason to follow a second.
For the wider multi-channel arithmetic, see running YouTube across multiple accounts; for device grouping, see running thirty iPhones.
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.