Every reply to your posts,
in one inbox

Everything published through Content Drifter is polled for replies and collected into a two-pane inbox: the conversation list on the left, the full comment and your response on the right. Mark read, archive, come back to it. The same pass that answers a LinkedIn comment answers the Instagram one.

The reason this matters is not tidiness. Replies in the first hour are the single cheapest thing you can do for a post’s distribution on most networks, and the reason people miss them is not laziness, it is that nobody opens five apps on a Tuesday afternoon.

Your Instagram direct messages appear next to the comments: who wrote, the last line, what is unread, and how long you have left to answer. Instagram only lets a business reply within 24 hours of the other person’s last message, so each conversation shows that window as a countdown, and says plainly when it has closed instead of letting a reply fail.

You see each message as sent, delivered or read, and a message that Instagram refuses is marked failed with a Retry. On a comment you can press “Reply privately” to send that one person a message. It is always a person pressing the button: Instagram allows one private reply per comment, within 7 days, and nothing here sends a message for you.

Messages are on the same plans as the inbox. Instagram only shares messages after you approve message access, so an account connected earlier asks you to reconnect once. Your posts and history stay as they are.

Press suggest and you get a draft written against your brand voice, with a match score showing how close it landed. Not to post automatically, which would be the fastest way to embarrass yourself in public, but so the blank box is never the reason a comment goes unanswered for three days.

Every network caps a reply at a different length, and the failure mode is silent: the platform truncates you mid-sentence and the reply you actually posted is not the one you wrote. The ceiling for that network is enforced here, before the send button will do anything.

Pinterest, YouTube and TikTok are absent. Pinterest has no comments in its API, so no app can read them. YouTube comments are not supported yet by our publishing partner, and they will appear here once they are. TikTok offers comments only to Business accounts, through its own business programme, and our publishing partner does not offer them. We would rather say so than show you tabs that are permanently empty and let you conclude the product is broken.

Direct messages work on Instagram only, because Instagram is the one network that lets a tool like this read and answer them. Brand mentions elsewhere on the internet are out of scope. That is social listening, it is a different product, and the tools that do it start in the hundreds of dollars a month.

Commenter names were missing, and are now mostly there. Probed against the live API on 23 August 2026, the integration returned an empty author field for every Instagram comment, and for LinkedIn a bare actor URN with no name behind it. We concluded the name was not obtainable, and that conclusion has since been superseded: our publishing partner now returns an Instagram username on most comments and resolves LinkedIn names. Measured on production on 12 October 2026, 31 of 37 recent Instagram comments carried a username and 10 of 11 LinkedIn comments carried a name. Where one is still missing we label the person by network, “Instagram user”, rather than showing “Unknown account” and letting you conclude the sync failed.

Threads replies were returning 500, on every post. Measured on production on 24 August 2026: six Threads posts probed directly, six 500s, against an Instagram control that answered 200. Eighteen Threads posts sat inside the sync window, so roughly a fifth of every tick's budget was being spent on work that could not succeed, and had been for days. Across the 155 runs on record at that point: 898 failures against 3,130 processed, and all 155 reported success, because a pooled failure rate cannot show one network being completely dead.

We did not fix that by calling a 500 permanent. A 500 is plausibly transient, and reclassifying a vendor outage as permanent is how a post gets hidden for good. What changed is the schedule: a target that fails three times running is rested on a widening delay, up to a day, and any success clears it. It heals itself when the vendor does, and a rested target is still reported rather than silently dropped.

Each sync reconciles against what the platform still returns, so a comment someone deleted is retired from your inbox instead of sitting there as a reply you can never send. An inbox that shows work that no longer exists stops being a to-do list.

New replies arrive on a background schedule, and a refresh button is there for when you have just posted and want to watch. The refresh is rate limited by plan on purpose: continuous polling of every network for every account is how an inbox feature turns into an API bill that gets the feature switched off.

Included on Lite and up, with no team tier needed. Most of the category gates engagement behind a team tier.