Inbox

The inbox lists DM threads from every connected X account on the left, and the selected thread's full message history on the right, with a composer at the bottom.

Tabs

Five tabs sit above the thread list: All, Leads, Community, Follow-ups, and Escalated. A thread's tag and any Reply Manage escalation are independent of each other, so a lead conversation and an escalated mention can both need attention without competing for the same tab.

Tagging a thread

Open a thread and pick General, Lead, or Community from the row above the message history. The tag is just a filter: it doesn't change how the thread behaves, only which tab it shows up under.

Follow-ups

Any thread can carry a follow-up date, set from the same row. A thread with a follow-up date appears in the Follow-ups tab, sorted by how soon it's due, and gets a follow-up due badge once that date has passed. Clearing the date removes it from the tab; a follow-up date is orthogonal to a thread's tag, so a lead conversation can also have a follow-up without the two settings conflicting.

Escalated

The Escalated tab isn't built from DM threads at all: it's a read-only preview of mentions that hit a Reply Manage guardrail, labeled with the reason (a named red-line topic, or low confidence) and a link to handle it there. This is what lets Reply Manage's guardrail decisions and Inbox conversations live in one place, so an operator working through the Inbox doesn't have to remember Reply Manage exists somewhere else.

Nothing here sends automatically

Unlike Reply Manage, the inbox has no auto-send mode and no drafting for DMs. It's read-and-reply: you pick a thread, read it, and type a response yourself.

Why DMs are a manual view and mentions aren't

Mentions are public and high-volume enough that drafting them automatically is worth the approval-gate it comes with. DMs are private, lower-volume, and usually warrant a real read before anything gets sent back. So the inbox deliberately stays a plain thread viewer rather than growing the same auto-draft machinery.

Refreshing

Threads and messages are fetched live from the platform each time you open the inbox or select a thread: there's no background job keeping a local copy in sync, so opening the page is always a live pull of what's actually there.