How to keep track of emails I'm waiting on a reply to?

What the job actually is

You keep track of emails you're waiting on a reply to by turning sent threads that stayed silent into a list you actually open, plus a later nudge if they never write back. The send is not a reminder, a label, a nudge, or a task until something else happens to it.

Founders and operators send the intro, the deck, or the ask, then the thread dies in Sent. They said they would get back to you, and unless the wait is on a list, the thread is dead. Inbox zero does not keep it. Starring it is a list people forget exists. A sales cadence that sends on its own is a different product.

The buying prompt collapses four jobs: a reminder you remembered to set, a label you still open, a nudge when sent mail gets no reply, and a draft of the bump a person still sends. A promise you typed is a neighboring job, on how to stop forgetting emails you promised. Work across apps with a send gate is on Lindy vs an AI employee in Slack.

Which tool wins which job

Fund the row that matches the leak. A snooze, a Waiting label, and silence after send are neighboring jobs.

Gmail has no search for no reply

Gmail's search operators include from, to, in:sent, in:snoozed, is:starred, and label. None of them means the last message in the thread was yours. in:sent is everything you sent. You still open each thread to see who spoke last.

Nudges sit on top of that gap. With conversation view on, Gmail can suggest emails to follow up on, and emails you forgot to reply to, at the top of the inbox. It is a suggestion, not a complete list of silence.

A Waiting label is the list you build yourself. Only you see it. If conversation view is on, the label applies to the messages you tagged, not to new replies. You still take the label off when the loop closes. Snooze hides a thread until a time you picked; search in:snoozed to find those. Silence in the body does nothing by itself.

A promise you typed is a different job

Most inbox tools watch silence after you hit send. That is emails I'm waiting on a reply to. I'll send you that report by Friday is the other leak: you still owe the work even if they write back. That job is on how to stop forgetting emails you promised.

Superhuman Auto Reminders detect that a follow-up is needed from the latest outgoing message if no reply has been received. Fyxer keeps those threads in Sent until your wait period passes, then labels them Awaiting reply or To follow up and drafts the bump. Lindy's follow-up bumps routine does the same after 1, 2, 3, 5, or 7 days. None of those, by itself, reads a promise in the body and keeps Friday.

If the leak is they never wrote back, fund the no-reply row. If the leak is you said you would send the deck and then forgot, fund the promise row.

The caveat that should decide the setup

The failure operators name first is an AI that sends the follow-up on its own. A prompt that says draft only is not a send gate: people have watched a bot email the team after they told it not to. Worst case with a draft is you delete it. Worst case with auto-send is you explaining the email on Monday.

Fyxer states that it never sends drafts automatically; you always review and approve. Superhuman Auto Drafts wait for you to hit send, and still alert if a placeholder is empty. Lindy's follow-up bumps land in your drafts folder. Anything with outside impact waits for approval, and Always allow turns that gate off. Guardrails apply in shared Slack threads only, not in the web app, Slack DMs, iMessage, or SMS.

Concrete is an AI employee that works in existing Slack channels and reads Gmail alongside them. It keeps every thread waiting on a reply as a follow-up. Each morning it nudges the owner. It drafts the follow-up as a Send / Edit / Skip card in Slack. A Gmail send needs the same tap. There is no auto-send mode. Follow-ups survive reboots. It is in design-partner preview; the longer thesis is on the vision page. It does not run sequences or cadences.

A practical setup for a 2-to-50 person shop

This is the boring version that holds when the founder still owns the one-to-one threads. Pin it before the next intro goes cold in Sent.

• Name the leak. A snooze, a Waiting label, a no-reply nudge, and a promise you typed are different. Snooze covers a time you picked. Labels cover threads you tagged. Nudges cover some silence after send. The waiting-on-reply job is sent mail that stayed quiet.
• Capture the thread when you send it. A sent email that needs a reply has to land on a list before it ages out of Sent. Manual copy into a notes app is the step that fails. A star is a graveyard if you never open Starred.
• Put the list where you will actually open it. A follow-up that only lives in Sent is easy to skip. A Waiting label you review on a set day, a Superhuman returned reminder, or a morning nudge in Slack is the list. Gmail Nudges live at the top of the inbox.
• Keep send as a tap on the exact text. Draft the bump. Send stays a tap. Always allow, Auto, or a prompt that says draft only is a different setup. One-to-one threads with a warm intro, a prospect, or an investor are not a sequence.
• Keep Gmail and Slack on the same list. The same wait is often an email and a Slack ping. Two tools, two lists, and the intro still goes cold. One follow-up that survives both is the job.