
A customer asks about pricing in an Instagram DM. A complaint sits unanswered under a Facebook post. Someone tags your client's brand on X, and nobody sees it until the next day. The posts went out fine — these are inbox problems, and they cost customers.
Every channel has its own inbox and its own rules about what shows up when. A team managing five client accounts across six platforms is really managing thirty inboxes, and the message that gets missed is usually the one that mattered most. A unified social inbox fixes the structure: every comment, DM and mention from every connected account lands in one queue, worked in priority order instead of app-hopping all day.
A unified social inbox is a single queue collecting the conversations arriving across your channels — comments, direct messages, mentions and tagged posts. Instead of logging into each network in turn, the team opens one screen and sees everything new in one place.
It is not a scheduler: scheduling is about what goes out, the inbox about what comes back. It earns its keep on the days nothing is scheduled.
For agencies, the inbox is where multi-account work becomes manageable: one workspace per client, one inbox per workspace, and a community manager can cover five clients without five phones logged in. It is the same operations system behind our guide to how to manage multiple social media accounts.
Customers now go to social media when they want an answer: according to the 2025 Sprout Social Index, 73% of social media users expect brands to respond within 24 hours, and 73% say they will buy from a competitor if a brand does not respond to them on social media at all.
That makes the inbox a revenue surface: a pricing question answered in an hour can become a sale; answered three days later, it is a sale that went elsewhere. A complaint answered publicly, calmly and quickly is visible to everyone who reads the thread later — and so is one that was ignored.
Reply time is worth measuring, and it can only be measured when all messages pass through one queue. A team checking six apps cannot tell you its average first-response time; a team working one inbox can — see our social media report template.
The channels iPlanr supports today deliver the following into the queue:
| Channel | What arrives in the inbox |
|---|---|
| Comments, DMs, mentions, tagged posts | |
| Page comments, Messenger threads, mentions | |
| TikTok | Comments on videos, mentions |
| X | Replies, mentions, DMs |
| Comments on Page and profile posts, mentions | |
| Bluesky / Mastodon / Telegram | Replies, mentions, messages in connected chats |
Two limits: Pinterest, Snapchat and WhatsApp are coming soon, not live yet, so messages there still need their native apps; YouTube is not supported, so its comments stay outside the queue. If a client depends on an uncovered channel, say so at onboarding and staff it separately.
Worked like email — oldest first, or loudest first — the inbox fails. The order messages are answered in is a business decision, and every incoming message fits one of five tiers:
| Tier | What it is | How to handle it |
|---|---|---|
| 1. Buying intent | Price, availability, booking, delivery | Answer first, in the same working block, completely and directly — a half-answer that asks for a DM loses the sale. |
| 2. Questions and objections | "Does this work with…?", "Is this suitable for…?" | Answer publicly and completely — future visitors will read the reply, so you are writing an FAQ entry. |
| 3. Complaints | Late delivery, broken product, bad experience | Acknowledge publicly and briefly, then move the resolution to a DM or email. Never argue in the thread. |
| 4. Praise and mentions | Compliments, tags, user photos, shout-outs | Warm, short, varied, batched once the higher tiers are clear — the cheapest loyalty-building work there is. |
| 5. Spam and scams | Bots, crypto pitches, fake giveaways, phishing links | Hide the comment or ignore the DM — any minute here is stolen from tiers one to four. |
Triage is the operating system in miniature: the messages that decide revenue get answered first.
A queue only works if everyone can see what everyone else has done. Two rules prevent the classic failures: the same message answered twice, and the message nobody answered because everyone assumed someone else had it.
One owner per conversation. Every open conversation has exactly one assigned team member — by client, channel, or tier. Pick one rule and keep it; a mixed rule is no rule.
Three states, no more. Every conversation is open, in progress, or resolved — untouched, owned, or answered. Add "waiting on client" for agency work where the answer depends on the client confirming a fact. The states must be visible to the whole team, and nothing sits "in progress" overnight without a note saying why.
End-of-day zero. The daily goal is not to answer every message the moment it arrives — that is how a team spends its whole day reacting. It is that at the end of the working day the open queue is empty, or every remaining item has a named owner and a reason.
Work the inbox in blocks, not continuously: constant monitoring destroys the rest of the job — planning, approvals, reporting — because every notification pulls the team back into the queue.
Between blocks, notifications stay off.
Most inbox messages are variations on a dozen questions — prices, hours, delivery areas, booking links. Answering each from scratch wastes the day; answering each with an identical pasted block makes the brand sound like a bot.
The middle ground is a small library of saved replies, in the brand's voice, adapted before sending: the facts stay the same, the greeting and the detail change. Ten well-written saved replies cover most of a small brand's inbox.
AI can help draft replies — iPlanr's AI caption engine, built on integrated ChatGPT, Claude and Meta AI, drafts on-brand — but a draft is not a send: a human edits and approves before anything reaches the customer. Complaints and buying intent should always be answered by a person.
Every platform has a quirk:
Three numbers, reviewed weekly:
Set targets from your own baseline: four weeks of your own data first, then improve on it.
The setup itself is short; the operating rules above are the actual work. In iPlanr the inbox lives alongside scheduling and approvals, in the same workspace as the client's calendar:
From then on, the inbox is part of the content calendar's daily rhythm — see our social media content calendar guide.
Judge a unified inbox with one client, one week: connect their accounts, run the two daily blocks, and count the messages answered that would have been missed.
Start a 14-day free trial — no credit card required — and run your pilot client through it: start your free trial.
A single queue collecting comments, DMs, mentions and tagged posts from all connected accounts, so one team answers from one place. In iPlanr it sits in the same workspace as the calendar and approvals — see the inbox feature page.
According to the 2025 Sprout Social Index, 73% of social media users expect a reply within 24 hours, and 73% will buy from a competitor if a brand does not respond. Treat 24 hours as the outer limit, not the target: buying intent and complaints deserve a reply within the working day — and Meta's 24-hour DM window is a hard deadline.
Yes, with the right structure: one workspace per client, one named owner per workspace, and the five-tier triage system so the owner always knows what to answer first. Messages get missed through ambiguity, not volume — when nobody knows who owns them. Our multi-account guide covers the workspace structure.
No — AI should draft, a human should send. AI drafts save time on routine questions, but complaints, buying intent and anything involving personal data need a person: draft, edit, then send, the same way you would approve a post.