Each weekday at [time], check [inbox or label] for conversations where I owe a reply after [number] business days. Exclude [senders or labels]. Read the full thread, identify the last substantive question or promise, and skip anything already answered or closed. Draft a short follow-up in my tone that refers to the real open item. Show me the recipient, subject, last message date, and draft. Mark anything that needs my decision. Do not send, archive, or change a thread until I approve the specific action.
Inbox follow-up for unanswered threads
Find unanswered inbox threads, draft specific follow-ups from their history, and hold every outgoing message for your review.
Copy-ready brief
Example output
Example queue for illustration only: Priya at Brackenwold Studio, last message Tuesday. Open item: Sam promised a revised onboarding timeline. Draft: “Priya, I have the revised timeline ready. Could we use ten minutes on Thursday to check the two handoff dates?” Status: Waiting for Sam to verify that the timeline is ready and approve the message. Acme Inc, last message Monday. Open item: none. A reply arrived overnight, so this thread was removed from the queue. Sent: 0 messages.
Trigger and cadence
- A daily inbox check finds a thread past its follow-up threshold.
- Scan each weekday morning and report only threads that meet the rule.
Inputs
- Inbox or label scope, excluded senders, and follow-up thresholds.
- Prior thread history and any promised next step.
- Tone guidance, reply length, and priority contacts.
Steps
- Read only the inbox scope named in the instruction.
- Identify the last substantive message and who owes the next reply.
- Exclude threads already answered, closed, or marked do not follow up.
- Draft a reply that names the actual open item.
- Present recipient, thread, and text for approval.
Approval boundary
Every outgoing follow-up waits for review of the exact recipient and message.
Stop conditions
- The thread contains a request requiring the reader's decision.
- The recipient or current state of the conversation is unclear.
- The thread is sensitive or on an exclusion list.
Expected output
A short queue of reply drafts with each thread's age and open item.
Receipt fields
- Threads checked and reason each draft was proposed.
- Exclusions, edits, approval decisions, and send status.
Recovery when it fails
- Recheck the thread before an approved send if new mail arrives.
- Keep held drafts attached to their original thread and flag stale ones.
On this page
Follow up on the open item, not the age of the email
An inbox follow-up workflow finds threads where you owe a reply and prepares a message tied to the actual conversation. An old timestamp alone is a poor trigger. The other person may have answered elsewhere, the task may be complete, or the next move may still be yours. OperatorNest can read the scoped threads and draft replies; the examples below are illustrative, not records of a live inbox.
Start by choosing the inbox or label. A client work label and a personal inbox call for different rules. Name people who should never receive an automatic draft, and set the threshold in business days if weekends would distort the queue. Your instruction should say which threads are closed and how to recognize a reply sent from another channel.
Check ownership before drafting
Each candidate thread needs three answers: what was the last substantive message, who owes the next response, and what question remains open? If Sam promised Priya a revised timeline, the right draft depends on whether that timeline exists. A reminder that asks Priya to respond would reverse the obligation.
For example, Sam’s email to Priya says, “I will send the revised plan Friday.” Friday passes with no new message. The workflow should flag Sam’s promise and ask whether the plan is ready. It can prepare a draft with a placeholder for the attachment, but the draft cannot claim the plan is attached until it is. That is a decision for Sam.
Another thread may be six days old but include an overnight reply. The operator should remove it from the queue on the next check. Counting it as overdue would create needless contact and weaken trust in the list.
Make the review queue short
For each draft, show the recipient, subject, last message date, open item, and exact text. Put items needing a decision at the top. A short queue lets you approve the clear replies and resolve the uncertain ones without rereading every thread.
The inbox assistant use case covers broad triage. This workflow focuses on conversations that have stalled after a specific promise or request.
Avoid a generic “checking in” line when the thread contains a concrete question. “Could you confirm the two handoff dates?” gives the recipient something to answer. If the operator cannot identify the open item, it should flag the thread for you and leave the message unwritten.
Hold and recheck every send
No follow-up leaves the inbox while you are away. The approval view should show exactly who will receive it and whether any attachment or copied recipient is present. Editing a draft changes the final text; the edited version is what you approve.
The thread may move while a draft waits. Before sending an approved message, recheck for new mail and hold the draft if the other person has answered. The receipt should record that a draft became stale, the new message that caused the stop, and whether you approved a replacement. That is as valuable as a sent follow-up: it shows the workflow avoided an awkward duplicate.
Run it on a schedule
Plan the timing and missed-run behavior with the recurring task planner. For documented schedule controls across assistants, read scheduled AI tasks compared.
Related tools
- Inbox triage rules generator
Sort investors, customers, vendors, and newsletters into a review plan. Download Gmail filters or copy Outlook and operator instructions.
- AI follow-up email writer
Draft two or three follow-up emails for a proposal, meeting, unpaid invoice, or introduction, with a suggested send time and copy buttons.
- AI agent approval policy
Set clear approval rules for an AI agent. Choose systems and risk limits, then copy a policy that says what waits and what can run.
Common questions
How does the workflow know who owes the next reply?
It checks the thread's last substantive message and any explicit commitment. If the responsibility is unclear, it flags the thread instead of drafting a nudge.
Will it follow up on every old email?
No. Scope it to a label, senders, or projects and define a threshold. Closed, answered, and excluded threads stay out of the draft queue.
What if the other person replies while a draft waits?
Recheck the thread before sending. A new reply makes the old draft stale and calls for a fresh review.
Keep reading
- An AI follow-up assistant that keeps threads from going coldIt tracks the threads you're waiting on and drafts the next nudge once one goes quiet, so nothing important gets forgotten.
- An AI inbox assistant that works while you sleepIt triages your inbox overnight, drafts replies in your tone, and leaves a short list of decisions for the morning.
- Approvals before anything that mattersIt asks before it sends, pays, books, deletes or posts. You approve, edit or hold from any channel.
- Your AI operator by emailEmail your operator like a colleague, or CC it on a thread. It researches, drafts and organizes, and asks before it sends, pays or books.
Hand off your first task tonight.
Tell us your email and what you'd hand off first. We'll send your access details and help you set up your operator.