Run

How-to Reviewed · not yet fact-checked

Goal

Every new reply triaged: categories accurate, questions answered, interested threads acted on.

Preconditions

Running sequences and the inbox receiving threads. The consolidated Inbox gathers threads from all sequences by all team members; it shows replies that came from automatic and manual emails, and notifications also cover LinkedIn messages.

Steps

1. Open the Inbox from the main header menu — the counter next to the button shows unread messages. Threads list chronologically with the most recent replies on top.
2. Narrow the view: the main categories Inbox, Unread, and AI draft on the left panel combine with inbox categories, and the top filters cut by sequence, sending email, category, and time. The All switch in the upper left filters threads by the team member who started them (All, My, or a specific teammate).
3. Check the AI-assigned inbox categories — Interested, Not interested, Do not contact, Not now, Forwarded, and the Meeting intent subcategory — and correct mistakes: select the thread, click Manually assign/reassign category, pick the category, and click Apply. Only one inbox category can be assigned per thread (plus Meeting intent), and you can bulk-assign across selected threads.
4. Work the AI draft category — threads with replies generated by Jason AI. When a sequence's AI replies are set to save a draft, the draft opens with the thread so you can review and edit it before sending.
5. Answer each thread: click Reply (or Reply all when the message has CC recipients — the CC list is shown and editable before sending), write the response using templates and variables if useful, preview, and send. The reply always goes out from the email account that sent the original step and stays in the same thread — including when you answer on a teammate's behalf via the team-member switch.
6. Reuse good answers: type the response, right-click it, select Save as Canned Response, and name it. Insert saved responses from the note icon, by typing "/" in the reply field, or with CTRL + S on Windows / Command + S on Mac.
7. Forward when someone else should own the conversation: Forward at the end of the thread sends the entire conversation; Forward next to an individual reply sends only that message.
8. Find anything with the search bar — first or last name, the subject line, or the email address of the contact; fragments match at the beginning, middle, or end of the value.

Expected result

Zero unread threads in the categories you act on; every Interested thread has an answer or an owner; category labels match the conversations.

Verification

The unread counters next to each category read zero, and spot-checked threads carry the right category label.

What happens next

Interested threads flow into your pipeline — Process positive replies covers routing; CRM sync carries outcomes out. Replies also set contact statuses per reply detection.

Common mistakes

• Treating a displayed auto-reply or out-of-office as a real reply — Reply classifies them separately and the contact continues in the sequence; see Reply detection.
• Trying to stack several inbox categories on one thread — only one applies, plus the Meeting intent subcategory.
• Searching by a truncated subject — search matches only the visible part of the subject line.

Related

• Inbox · Conversations
• Reply management
• Why was a reply not detected?

Build with Reply

• REST API: docs.reply.io — inbox endpoints
• MCP: agents.reply.io/mcp — agents run this routine end to end
• Agent skills: agents.reply.io/skills — manage-replies workflow