The inbox pulls together three things almost no tool treats alike: private messages, comments on your posts, and reviews. They arrive from the brand's connected accounts, group into one thread per conversation, and are answered from the same screen, with a clock that flags anything sitting more than 24 hours without a reply.
Three different objects, one job
A direct message, a comment under a reel and a review on a Google listing are different things to the platform that produced them. To whoever runs the account they are the same thing: somebody wrote something and is waiting for an answer. Most scheduling tools model only the first two, and the third ends up in a tab somebody opens on Fridays if they remember.
Here all three are kinds of the same object and they live in one list. That has an immediate practical effect: the person replying opens one screen instead of four, and the work stops depending on nobody forgetting one of them. Tuesday's two star review and a prospective client's comment sit in the same queue, ordered by whatever has been waiting longest.
The second effect is grouping. A conversation is a person, not an event. If somebody commented on a post yesterday and sent you a private message today, that is one thread with two things inside it rather than two entries in two separate inboxes. Whoever replies sees what was already said before they write, which is the difference between a useful answer and a template.
What arrives from each network
The inbox is not equally deep across the fourteen connected networks, and it is worth knowing that before promising a client that everything gets answered from one place. What arrives depends on what each platform lets an outside tool read.
| Network | Messages | Comments | Reviews |
|---|---|---|---|
| Yes | Yes | No | |
| Yes | Yes | Yes | |
| No | Yes | No | |
| YouTube | No | Yes | No |
| Threads | No | Yes | No |
| Bluesky | Yes | Yes | No |
| Yes | Yes | No | |
| Telegram | Yes | No | No |
| Yes | No | No | |
| Google Business | No | No | Yes |
| TikTok | No | No | No |
| No | No | No | |
| Snapchat | No | No | No |
| Discord | No | No | No |
Ten of the fourteen networks contribute something to the inbox and four contribute nothing. TikTok, Pinterest, Snapchat and Discord publish perfectly well from the calendar, and their conversations are answered in their own apps, because there is no door to read them through from outside. Saying that plainly is more useful than drawing an empty tab: the full inventory of what each network does is in supported social networks.
Facebook is the only one that appears in all three columns, because a Page carries messages, comments and reviews at once. LinkedIn, YouTube and Threads come in through comments only, which for a brand is usually exactly the half that matters.
The review is the odd case, and the valuable one
Google Business has no direct messages at all. What arrives from that listing are reviews, with their rating and their text, and they are answered from the same thread list as an Instagram DM. That is a genuine difference from an ordinary scheduling tool, and it is felt most by anybody running accounts for businesses with a physical door: restaurants, clinics, workshops, shops.
For those accounts a review is not one more interaction. It is the only one still sitting there six months later, in the place where somebody decides whether to walk in. Having reviews and comments in one queue changes what gets answered first, because an unanswered review weighs more than an unanswered comment, and across two separate inboxes that is never visible.
Facebook supplies the other kind of review, the one on the Page, which is why it is the only network in all three columns of the table above. Between them they cover most of what a brand with a physical location receives in writing, and that is half of a support workload which normally lives outside any social tool at all.
There is an operational reason too: a review arrives when it arrives, not when you publish. An inbox that only gets opened during a campaign lets weeks of reviews go unanswered. A single queue with a clock on top of it puts them in front of you like everything else.
The 24 hours are not an internal convention
A message is marked overdue 24 hours after it arrives without a reply. The number is not an invented productivity target: it is the window Meta itself imposes for answering a message outside a template. Past that window the conversation can no longer be picked up with free text, so the flag marks a real limit rather than an aspiration.
The clock shows on the row, before you open the conversation, which is where it is useful. An urgency marker inside the thread arrives too late by definition: to see it you have to have gone in, and if you went in you already decided to handle that one and not another. Outside, the list can be sorted by what is about to expire and worked through in that order.
That same clock is what lets you promise a client a response time and then hold to it. Not because the tool answers, but because it makes what is slipping visible while it can still be prevented.
It is worth noticing that the 24 hours belong to Meta and are not a rule that applies equally everywhere. A three day old YouTube comment can still be answered and a Google review never expires. The clock flags them the same way because the service standard is the same, but the cost of overrunning it differs by where the message came from, and that is a judgement for whoever runs the account rather than for the tool.
Everything in this article happens in one place in GoFeed.
Try it freeWho answers what
On a small account the inbox runs itself. As soon as there are two people, the problem stops being reading and becomes distribution: two replies to the same person, or none because each of them assumed the other was on it.
So a conversation has an owner. It is assigned to whoever is going to answer it and leaves the shared list, rather than being forwarded through some other channel and multiplying. The thread stays readable by the team, so somebody picking up an account on a Monday can see what was said on Friday without having to ask.
For an agency there is a detail that matters: you answer for each client without leaving your own account and without asking anybody for their Instagram password. That sounds small and it is the difference between a clean handover of accounts and a shared sheet full of credentials. How the inbox is assembled underneath is on the inbox page.
There is also a link back to the calendar that goes underused. Comments arrive from the posts you put out, so the inbox is telling you, without being asked, which pieces start a conversation and which go by without anybody saying a word. A piece that collects twenty comments and one that collects none cost the same to produce, and that signal reaches you through the inbox before it reaches any metrics dashboard. What you do with it is plan next month from calendar and publishing.
What to know before you promise it
Three limits, and all three show up on day one.
Outbound attachments work on four networks only: Instagram, Facebook, Telegram and WhatsApp. Instagram takes image, video and audio, and the other three take a document as well. Everywhere else the reply goes out as text, and no paperclip is drawn there that would only fail after the file had finished uploading.
The inbox does not write for you. There are no generated replies and no automatic suggestions anywhere in it, and that is deliberate: what gets said in a brand's name is written by a person. What does exist, and is a different thing entirely, is an automatic message triggered when somebody comments a keyword on Instagram or Facebook, which is what Auto DM does, and it is configured by hand, line by line.
And a shared inbox does not fix a volume nobody can handle. If two hundred messages arrive a day and there is one person, the queue is easier to see and still does not fit. The decisions about templates, hours, and what gets answered and what does not are in the guide to managing your DMs, and they come before any tool.