Everything from Instagram, Facebook, and Threads ends up in one place, with comments and DMs sitting together in the order they came in. The post someone's commenting on or messaging about is pinned right there next to the conversation, so you don't have to keep flicking back to remember what they're reacting to.
New comments and DMs push in the moment they happen, so nothing sits there unanswered while you're waiting on a notification that never quite arrives. You can reply with text or media, hide whatever shouldn't be there, and leave a note your team can see but the customer can't. Flip the safety timer on and every reply gets a five-second undo before it goes out, which is the kind of thing you appreciate the day you nearly send a personal reply from a brand account.
And the posts you write in the composer and lay out on the calendar attach themselves to the threads they generate, so the conversation about each post lives right next to the post itself. If you're running multiple workspaces as an agency, you get one inbox per client, side by side.
Threads on the left, the conversation in the middle, the post pinned to the right. So when someone says the link in your caption is broken, the caption's right there.
Filters across the top narrow things by platform, account, or message type, and a search box picks up whatever the filters miss. Anything you can do here is also available through the public API and the MCP server.
Context, one click away
When someone comments on a post you scheduled here, that post sits right next to the conversation with the caption, the media, and when it went out. So when someone says the link's broken, you can see the link without leaving the page.
No five-minute delay
The moment someone comments or DMs, it shows up in your queue. There's nothing to refresh and no waiting around for a sync, and you won't see the same comment twice either.
Replies under the parent
Comment threads read the way they look on the platform itself, with replies indented under the parent and your replies marked out by a coloured rule down the side, so you can scan a long thread without losing track of who said what.
Your team sees them, the customer doesn't
Every thread has a notes tab only your team can see, so you can drop in context like "this one's the founder, escalate fast" and the next person who opens the thread picks up right where you left off. The customer never sees a word of it.
Optional 5-second pause
Flip the safety timer on and every reply pauses for five seconds with an undo button sitting there waiting, which you'll appreciate the day you nearly send a personal reply from a brand account. Off until you turn it on.
Catches Meta's 24-hour rule
Instagram and Facebook close their DM threads 24 hours after a customer last messaged you, and the inbox keeps an eye on the clock so you know before you type out a reply the platform won't actually deliver.
Instagram, Facebook, and Threads, all stitched together. Comments on all three, DMs on Instagram and Facebook, with new conversations landing the moment you connect an account.
A pill row at the top with All, Comments, DMs, Reviews, and Mentions, so you can tap one to narrow the list. Reviews and Mentions show up as their channels come online.
Channel circles for IG, FB, and Threads, with an avatar row underneath for whichever specific account you want to focus on. Pick the platform first and the account row narrows to match.
A search box on the thread list that narrows by handle, last-message preview, or visible content. It works alongside the filters rather than replacing them, so you can stack a search on top of the view you've already got.
Replies indent under their parent the way they do on the platform itself, with your replies marked out by a coloured rule. Top-level comments group by date, so a long thread still reads in order.
Plain text on every channel that allows it, plus images, video, audio, or documents on Instagram and Facebook DMs. We catch the platform's awkward rules before you hit send, like Instagram refusing to let you mix text and media in the same DM.
An optional five-second pause on outgoing replies with an undo button right there. Off by default, but once you flip it on it stays on per browser.
Instagram and Facebook close DM threads 24 hours after a customer last messaged you, and the inbox warns you before you send into a closed window. So you don't burn a reply the platform won't actually deliver.
Hide a comment, unhide it, or delete it outright. Editors and admins only (viewers see the action greyed out), and every change shows up in the audit log with who did it and when.
When a send fails because of a rate limit, a dropped connection, or an expired window, the bubble shows a retry button. One click and it goes again, no need to retype anything.
Every conversation has a notes tab only your team can see, so you can leave context for whoever opens the thread next. Anyone with edit rights can clear a note, and the platform never sees them.
Mark a single thread read, or hit the header button to clear every visible thread in one go. The bulk action respects whichever filters you've already got on.
Read it on the laptop and the phone catches up. Conversations and read state push live across both, so you don't end up clearing the same notification twice.
When a thread's tied to a post you scheduled here, the post gets its own column on wide screens with the caption, media, and scheduled time. On narrow screens it collapses into a banner across the top.
Coloured labels you define at the workspace level, plus a hand-off field so a teammate can take a thread over. Labels show as dots in the thread header with the name appearing on hover.
Click a comment to reply directly to it, and the composer shows you who you're replying to and threads the response under that parent. DMs don't need this, comments do.
The unread and open numbers in the header badge are the same ones you can pull through the API or MCP. Handy for a daily digest, a dashboard tile, or keeping an eye on the queue from somewhere else.
If a platform connection ever drifts, an admin can resubscribe and pull recent activity straight from settings. No support ticket, no missed comments.
Claude, Codex, or Cursor can list, reply, moderate, and retry inbox messages with mcp:read and mcp:dangerous scopes. Confirmation strings on the high-risk verbs.
@ezibreezy/cli inbox commands cover the same surface as the web inbox: list, reply, moderate, retry, stats, mark-read. JSON in, JSON out.
Inbox endpoints under the public API for service-to-service automation. Same audit log as the web app, same permissions model.
The post editor that produces the posts the inbox responds to. Per-platform captions, native settings, live previews per channel.
Free monthly content calendar. Pair it with the inbox so the posts you plan and the conversations they generate live in one workflow.
Roll inbox stats (unread, replied, hidden, retried) into the monthly client recap without rebuilding the table.
The inbox isn't bolted on. It reads from the same workspace as scheduling, the same audit log as approvals, and the same media library as the composer. The links below cover the surfaces it touches most.
One place for the comments and DMs that come back at you on Instagram, Facebook, and Threads. Open a thread, see the conversation in order, see the post that triggered it, reply from your laptop. The phone stays in your pocket.
Instagram comments and DMs, Facebook page comments and DMs, and Threads comments. The other channels EziBreezy schedules to (LinkedIn, X, TikTok, YouTube, Pinterest) keep being scheduled and reported on, and we'll roll them into this inbox as their reply APIs come up.
Same queue, same filters. There's a pill row at the top: All, Comments, DMs, Reviews, Mentions. Tick one to narrow the list. Reviews and Mentions appear when their channels are connected; today the active surfaces are comments and DMs on the three Meta platforms.
Yes. Plenty of teams run it that way: a customer DMs or comments, the thread lands in one queue, you reply from your laptop with text or media, leave an internal note so whoever picks it up next has the context, hand it to a teammate, and the whole exchange stays searchable. It is built for replying and engagement, not as a monitoring or social listening tool, so it watches the comments and messages that come back at your accounts rather than scanning the rest of the web for brand mentions.
The moment they happen. We subscribe to each platform when you connect it, and new comments and messages push straight into your queue. No refreshing, no five-minute delay, and the same comment doesn't show up twice.
On Instagram and Facebook DMs, yes. The composer accepts an image, video, audio, or document and uploads before sending. Instagram has an annoying API rule: text and media can't go in the same message. The composer enforces that and tells you why instead of failing silently at send time.
An optional five-second hold on outgoing replies. Toggle it on, hit send, watch the undo button count down. Useful if you've ever pasted the wrong link into the wrong DM and wanted those five seconds back. Off by default; the setting persists per browser.
Each thread has an Internal Notes tab. Type the context ("this one's the founder, escalate fast", "launch is Friday at 9"), and your team sees it the next time they open the thread. The platform never sees them, the customer never sees them. They live alongside the conversation and stay searchable.
Per message: hide, unhide, delete. The action runs against the platform itself, not just your inbox view. Roles matter: viewers can read, editors and admins can act. Every change shows up in the workspace audit log so you can see who hid what and when.
Meta closes Instagram and Facebook DM threads 24 hours after the customer's last message. The inbox watches the clock and shows you when a window's about to close, so you don't type out a reply only to have the platform reject it. Comments don't have this rule. Threads doesn't either.
Yes. Replies hang off the parent comment, indented, with a coloured rule down the side so an outgoing reply reads differently to an incoming one. Top-level comments group by date. DMs render as a single linear conversation because that's what the platform sends.
Threads carry an assignedTo field plus colour-coded labels you define at the workspace level. Filter by account, by platform, by message type, by open vs all states, and search the visible threads by handle, preview, or content. There's a Mark All Read action up top that respects the filters you've already applied.
Right. If a comment lands on a post you scheduled here, the thread carries the original post next to the conversation: caption, media, the time it went out. On wide screens it sits in its own column to the right of the messages. On narrow screens it collapses into a banner at the top. The same posts you plan in the calendar and the composer are the ones the inbox attaches to.
Yes, through the MCP server. Reading scopes let an agent list threads, fetch messages, and pull stats. The riskier actions (reply, moderate, mark-read, retry) sit on a separate scope you have to grant deliberately, and they each need the agent to echo back the specific thread ID before the action runs. So a stray prompt that doesn't know your inbox can't act on it.