Transparency
Three lists, no spin.
What the platforms do by design, what we know is imperfect on our side, and what we have fixed. If something looks broken and is not here, tell us — and check the status page first.
Last reviewed: October 18, 2026 · re-checked whenever a platform changes.
Platform rule — not our bug
Platform rules we work within
Not bugs — every comment-to-DM tool on the planet works inside these rules. Where a rule is Instagram-specific we say so; the same questions for TikTok, Threads and YouTube are answered per platform in the app.
| Question | State | What actually happens |
|---|---|---|
| A DM to someone new lands in their Message Requests | By design | If a person has never messaged you, Instagram puts your DM in their Requests folder instead of their inbox; Facebook does the same in Message Requests. Every tool on both platforms works this way — it is Meta’s rule, not ours. Two things help: your DM copy can say “check your requests”, and buttons still render there (quick-reply chips do not, which is why we recommend buttons for first contact). |
| One private reply per comment | By design | Instagram and Facebook allow exactly one automated reply per comment. TikTok, Threads and YouTube do not have DMs, so there we post one public reply per comment instead — you pick which. If it fails (for example, the person has restricted messages), the reply is spent — we show that in the activity log instead of retrying blindly. Anything after the first reply happens once the person messages you. |
| No delivery receipts on Instagram | By design | Instagram does not tell anyone whether a DM was delivered (Messenger, on Facebook, does). That is why “Delivery confirmed” shows — on Instagram instead of a number, and “DMs sent” is the strongest count Instagram will stand behind. |
| Follower status is only visible after someone messages you | By design | Instagram reveals the follow relationship only for people who have messaged the account (Facebook exposes more, the other four platforms expose less). For everyone else our follow-gate asks them to confirm — a tap is a message, which unlocks the real check. That is why “Follower at trigger” sometimes shows —. |
| Stories are 24-hour objects | By design | Story automations only work while the story is live, and story replies stop when it expires. Reels and feed posts do not have this limit. |
| Likes on Instagram comments need meta approval | By design | Liking comments as your account works on Facebook, and on Instagram only for accounts Meta has allowlisted for it. When it is not available the like is skipped silently and noted in the activity log — the DM still goes out. |
Our issue — we can fix it
Known on our side
| Issue | State | What we know and how to work around it |
|---|---|---|
| One active automation per post | Our issue | Two automations can’t run on the same post at the same time (a rule of the delivery engine, so a comment never triggers two DMs). If you see “an active automation already exists for this post”, pause or delete the one already there — the message links you to it. Multiple posts in one setup are fine: each post gets its own automation. |
| Click rate only counts link-tracked sends | Our issue | Click-through uses “DM deliveries that carried a tracked link” as its denominator, so campaigns from before you enabled link tracking show no CTR. New sends count immediately. |
| Post history covers about 12 months | Our issue | The post picker shows roughly a year of synced history plus everything since. For anything older — or anything you haven’t published yet — choose “Any post” and the keyword works everywhere. |
Fixed
Recently fixed
| Fixed item | State | What changed |
|---|---|---|
| Multi-post campaigns saved only the first post | Fixed | Caught and fixed in one day; verified with fan-out test runs against the real engine. |
| Conversation threads that never announced themselves were missing | Fixed | The sync now bridges and repairs those threads on the next event. |
| YouTube link previews failed from our servers | Fixed | Preview fetches now use a fast-path for YouTube links. |