Inbox

The Inbox is your team's review queue for feedback that came in from outside the portal - Slack messages your team flagged, customer emails forwarded to your inbound address, and (soon) Discord, Intercom, and Zendesk. Drafts land here in pending state. You triage them, edit if needed, then approve or dismiss.

The Inbox is available on every plan. It's a separate queue from Dashboard -> Moderation (which handles portal submissions); the Inbox is only for external-source intake. Of the intake sources that feed it, email intake is on every plan, while Slack is on Startup and Scale (not Growth). On Growth the Inbox fills from email intake only.

Open it

Dashboard -> Inbox (left sidebar). The badge shows the pending count across all sources.

What you see

The Inbox has two filter rows:

1. Source chips (top): All / Slack / Email. Click a source to narrow the list.
2. Status tabs (below): Pending / Approved / Dismissed / All.

Each card shows:

• Source context - for Slack: channel name, message author, permalink to the original thread. For email: sender name + address, subject, attachment count.
• AI-suggested title and body - extracted from the original content. Editable in-place before approval.
• Raw text - the original message, useful when AI extraction missed something.

Triage actions

Per draft, three buttons:

• Approve. Promotes the draft to a published Post on your default board (or the configured default for that source). The original Slack message gets a linkback (Slack only); the email sender gets nothing automatic.
• Dismiss. Marks the draft as not-actionable. The post stays as a draft and is hidden from end users. Useful for off-topic forwards or duplicates you've already seen.
• Edit. Inline-edits the title and body. The next Approve uses your edits.

All three log an entry in the workspace audit log under intake_draft.{approve|dismiss|update}.

Source-specific bits

Slack drafts

Slack drafts come from three places:

• Message events - your team flagged a message via the message-action shortcut.
• Slash commands - someone used /feedjolt in a channel.
• Message shortcuts - the "Capture as feedback" item in Slack's message context menu.

When you approve a Slack draft, Feedjolt posts a linkback message in the original thread so the customer (or your teammate) can see where the feedback ended up.

Email drafts

Email drafts come from forwarded customer emails. The sender becomes an EndUser in your workspace, keyed on the lowercased email address. If the same sender writes again, their drafts attribute to the same EndUser.

Replies to notification emails (e.g. a customer replying to "your post status changed to Planned") don't create new drafts - they thread back onto the original post as a comment automatically. See Email intake.

What it isn't

• Not a moderation queue for portal submissions. Public-portal post submissions still land in Dashboard -> Moderation, gated by is_draft=true on the Post itself. The Inbox is one step earlier - pre-Post staging from external sources.
• Not real-time chat. Drafts arrive within seconds of the source event, but this is a review tool, not a notification stream. Use Slack notifications or the dashboard overview for live signal.

Permissions

See also

• Email intake
• Slack integration
• Triage workflow