Inbox activity: your processed email feed

Inbox activity is the complete, filterable history of every email InboxAgent has processed — your go-to for “what happened to that email?” and for spot-checking classifications.

The list

Each row shows the sender, the mailbox it arrived in, the subject, the category chip, the confidence score, the processing status, and when it arrived.

Narrow it down with:

• Outcome tabs — what happened to the email, each with a live count. They open on Needs your review, because that is the only one that is a to-do list:

  • Needs your review — waiting on a person. Work these.
  • Not delivered — classified fine, but we couldn’t deliver it. Each row says why: no CRM or helpdesk connected (connect one and you’ll be offered the chance to push them), or delivery failed (something rejected it — see Delivery failures). This is now uncommon: sales inquiries go to Leads and everything else that needs a person goes to Follow-ups, with or without an integration.
  • Handled — it reached a board (Leads or Follow-ups), or a record was created in your CRM or helpdesk, or a comment was added to an existing one.
  • No action needed — spam, newsletters, auto-replies, internal mail. Categories an admin has sent to Follow-ups appear under Handled instead.
  • Already handled — a duplicate, or a reply on a thread already tracked.
  • All — everything.

  A tab stays visible at zero rather than disappearing, so the set of outcomes looks the same every day. The counts always describe the mailbox, category and search you currently have set.

• Category — focus on one type of mail, e.g. everything filed as Marketing.

• Mailbox — one inbox at a time.

• Search — by sender or subject. The search box in the top bar (Ctrl+K / ⌘K) lands here too.

• Sortable columns — Confidence, Status, and Time.

Arriving from a Dashboard card

Clicking a card on the Dashboard brings you here with the list already narrowed to match it, so the number you clicked is the number you land on. That can be two things at once: what the card counts (leads we identified, for example) and the card’s date range, since the Dashboard always shows a period rather than all time.

Each one is named in a note above the list and can be cleared on its own. They are separate on purpose: if you came from “Leads Identified” for the last 7 days, you might want every lead, or you might want everything from the last 7 days, and clearing one should not throw away the other.

Clear both and you are back to the full history.

The detail panel

Click any row and the full story opens on the right:

• Classification — status, category, and confidence.
• “Why this classification” — the AI’s own reasoning, in plain text. The fastest way to understand a surprising call.
• Actions — what was actually done: the lead or ticket created (with its record ID in your CRM/helpdesk), the review queued, or the error if something failed.
• Conversation — other messages on the same thread, when there are any.
• Re-classify — fix a wrong call on the spot; see Re-classify an email.
• Reprocess — run the email through the pipeline again (admins and members). Useful after you’ve fixed the cause of a failure — say, reconnecting your CRM. Reprocessing is duplicate-safe: an email that already created a lead won’t create a second one.

Opening an email from a notification (via the bell) lands you on that message on its own; use Back to Inbox activity to return to the list.

Reading it like an operator

• No action needed isn’t a problem — it’s the filters doing their job on newsletters, auto-replies and internal mail. Spot-check that tab occasionally to confirm nothing real is in there.
• Not delivered is usually one problem, not many. If the reason is no CRM or helpdesk connected, it is a setup step rather than a pile of separate failures: connect one and the Integrations screen offers to push the waiting messages in a single click. Nothing moves until you accept that offer, so if you would rather leave last week’s mail where it is, you can. If the reason is delivery failed, that is a genuine fault worth reading.
• Failed rows deserve attention — they also surface on Failed messages with retry controls.
• Members and viewers can browse everything their mailbox access allows; re-classify and reprocess need admin or member rights.