Posting by hand, on time
When a platform cannot publish something automatically, or somebody has not connected an account, they get a message at the scheduled time with everything ready to paste.
Not everything can be published through an API. Some platforms do not offer the endpoint, some charge for a tier nobody needs, and some people would simply rather post from their own phone.
None of that stops a launch. Those posts take the assisted route, and they are a normal part of the plan rather than a fallback.
What happens at the scheduled time
The author gets a message with:
- their post, already written and approved, ready to copy
- any images or video, ready to download
- a link that opens the platform's own composer with the text in place
- for a reply or a repost, the launch announcement already attached
- one button to confirm they posted, and a box for the link if they have it
Once they confirm, the post appears on the launch alongside everything that published automatically. If they do not, a reminder follows.
Why a post ends up here
Three reasons, and the screen says which one:
- The platform cannot do it. A Repost on X is the clearest example: X only offers that through its Enterprise tier, so it routes here instead of being scheduled and failing later.
- Nobody connected an account. A participant who never connects still gets their reminder and still gets counted.
- They chose to. Anyone can mark a post as one they will publish themselves.
Assisted posts are free
Only automatic posts count against a plan's monthly limits. A post published by hand costs nothing and is never counted, which is what makes it the answer when a launch runs past a cap rather than a reason to upgrade.
What it is not
It is not a to-do list that hopes somebody checks it. The message arrives at the moment the post is due, with the post in it. The work left is pressing publish.
Last updated 2026-08-18
