Product · 5 min read
We Do Not Schedule Posts. Your Calendar Still Runs This.
We do not schedule posts. There is no queue, no calendar view, no best-time-to-post suggestion, no draft library, and nothing here publishes anything to Instagram, ever.
That is not a limitation being worked around. We reply to people. Creating and publishing content is a different product, and if that is what you came for, the honest answer is that you need a scheduler and this is not one.
The reason this page exists anyway is that there is a real connection between the two, and almost nobody sets it up correctly. An automation is attached to a post. So the moment a post exists is the moment an automation decision exists, and if your publishing happens on one schedule and your automation work happens on another, the two drift apart and the gap is where things break.
Publishing is what makes an automation start mattering
The chain is short and worth stating exactly.
The caption carries the trigger word. The trigger word is what makes people comment it. The comment is what fires the automation. Remove the caption line and the automation is switched on, correctly configured, and completely inert — nothing will ever match it.
An automation without the line in the caption is not broken. It is unemployed, and nothing anywhere will tell you.
Which produces the failure that costs people the most: the post goes up at 7pm on a Thursday, the caption says comment GUIDE, and the automation for it gets built the following Monday. Four days of comments landed on a word that meant nothing. The comment window is seven days from each comment, so some of them are still answerable — but you have to go looking, and nobody does.
The order that avoids it
- Write the caption line and the reply at the same time. They are one decision. The word in the caption and the message it produces cannot be designed separately without one of them being wrong.
- Build and test the automation before the post is published. Test on myself runs the whole pipeline and delivers to your own account, which takes a couple of minutes and is the only rehearsal available.
- Restrict it to that post under Advanced. An account-wide trigger plus a scheduler pushing four posts a week is how last month's offer gets sent under this month's reel.
- Write the retirement date down the day you build it. Not when the campaign ends — the day you build it, while you still remember what makes it temporary.
Your scheduler posts at 11pm and your quiet hours start at nine
Here is the specific collision between the two tools, and it catches people who did everything else right.
Schedulers optimise for when a post gets seen. That is frequently late in the evening, sometimes very late. Comments arrive in the hour after publication, which means a post that goes out at 11pm generates its first wave of comments at 11pm.
If your quiet hours run from around 9pm, every one of those is held until morning. That is correct behaviour and it is the right default — a 1am automated message reads as a machine no matter how it is written — but it is worth knowing rather than discovering. Two honest options: accept the delay, which is usually fine, or stop scheduling posts into your own quiet window when the post is built around a comment ask.
The publish-time habit worth having
Teams that run this well have one small ritual and no software supporting it: at the moment a post is queued, somebody answers three questions.
Does this post need an automation, or is it a post people just look at? If yes, is it built and tested? And what does it replace — meaning, which older post's automation should now be retired or rewritten?
The third question is the one that gets skipped, and it is where old prices, finished offers and sold-out things keep answering strangers months later. A post stays on the grid for years. Whatever is attached to it stays true only as long as the world it described.
What this does not become
There is no integration between a scheduler and this. No Zapier connector, no webhook that builds an automation when a post publishes, no API that reads your queue. Somebody does it by hand, and it takes a couple of minutes, and if that somebody is not named it does not happen.
There is also no analytics product, no best-time recommendation, no content calendar, no caption or hashtag tool, and no follower growth feature. Leads leave as CSV. No WhatsApp.
Official Instagram Graph API only, which sets the clocks everything runs on: seven days to reply to a comment, counted from the comment rather than from the post, and twenty-four hours inside a DM thread, restarted only when the person messages you again.
The short version
Keep scheduling wherever you already schedule. Add one line to whatever checklist that tool has, at the point where a post is queued: what is the trigger word, is the automation live, and what does this retire.
That is the whole overlap between publishing and automation, and it is a checklist item rather than a feature. If you want the mechanic itself, the comment-to-DM flow is the thing your caption is pointing at, and choosing the word is the decision the build turns on.
