Oops! Something went wrong while submitting the form.
Gmail's Schedule send handles the email you have already written. This finds the threads where you sent the last message and nothing came back, drafts a short nudge on each, and shows you the queue before anything is scheduled. In the recorded run it reviewed four active threads, found none that qualified, and scheduled nothing.
The recording is a real session. The sheet on the right is what it produced.
Sai opens each profile, pulls the signal, and writes the row, live, in a real browser.
Eight columns, sorted by score, with a source link behind every claim.
Gmail access. A look-back window (7 days), a waiting threshold (4 days), and the send time you want.
A queue for approval: each stalled thread with the date of your last message, days waited, what you asked for, and a drafted nudge. Nothing is scheduled until you approve. If no threads qualify, an empty queue plus the list of threads reviewed.
Every Monday morning, so the week starts with the stalled threads identified and the nudges drafted.
On a computer:
On Android, iPhone and iPad the same option sits behind the three-dot menu in the compose window.
Scheduled emails send in the timezone you scheduled them in. Google states this directly: "Your emails will be sent based on the timezone you schedule them in." A message set for 8:15am in San Francisco reaches a London recipient at 4:15pm. Gmail has no recipient-timezone option.
The cap is 100 scheduled emails. Google's documentation gives this as a hard limit on how many can be queued at once.
Delivery is approximate. Google notes that scheduled emails may send a few minutes after the scheduled time.
Cancelling turns the email back into a draft. Open the Scheduled label in the left panel, select the email, and click Cancel send at the top right. The message moves to Drafts rather than being deleted, and can be rescheduled from there.
Schedule send acts on an email that already exists. Composing it, choosing who it goes to, and deciding it needs to be sent at all happen before the feature is involved.
For a single planned message that is the whole job. It becomes a different problem across an inbox: at any point there are threads where you sent the last message and nothing came back. Some need a nudge. Some do not, because the recipient said they would answer next week, or because the message was informational and no reply was expected.
Working out which is which means opening threads, reading the last message, and checking the date. Schedule send does not participate in that.
Gmail Nudges is Google's built-in answer. It surfaces messages at the top of the inbox with a prompt — "Sent 3 days ago. Follow up?" — and it is free, automatic, and requires no setup. It identifies candidates. Writing the follow-up and deciding when it should go out remain manual.
Boomerang, Right Inbox, Mixmax and Mailbutler go further. Their core feature is conditional follow-up: at the moment you send an email, you set a rule that fires a follow-up if no reply arrives within a set number of days. It runs unattended after that. Several of them also send at the recipient's local time, which Gmail's native scheduling does not.
Outreach, Salesloft and Lemlist run multi-step sequences with reply detection and cadence control, built for outbound at volume.
For outbound you plan in advance, these are the tools designed for the job, and the conditional-follow-up model is a better fit than any after-the-fact sweep: it needs no second pass and cannot miss a thread.
Conditional follow-up has to be configured at send time. Boomerang's rule is set when the email goes out. A sequence requires the contact to be enrolled.
Emails sent without any of that in place — most email — are outside it. The threads that stall are frequently the ones where following up did not seem necessary at the time.
Gmail Nudges covers part of this by surfacing them afterwards, but stops at surfacing.
This task starts from the existing inbox: it reads back over the last seven days, identifies threads where the last message is yours and nothing has come back in four days, drafts a nudge on each, and schedules them.
Whether a thread counts as waiting determines who receives an email, so the criteria are specified rather than inferred.
A thread qualifies when the last message is yours and it asked for something — a decision, an answer, a document, a next step.
It does not qualify when the last message was informational, when the recipient stated a date they would respond by and that date has not passed, or when the only response was an out-of-office. Newsletters, notifications and no-reply addresses are excluded. So are threads already followed up since the recipient's last message, which is what otherwise produces repeat nudges to the same person on a weekly schedule.
The recorded run reviewed four active threads and scheduled nothing.
"I searched and analyzed every thread you sent into over the last 7 days. Here's what I found — the queue is empty, so I haven't scheduled anything."
Underneath, Threads reviewed (4 active), with columns for the thread, your last message, what happened after, and whether it is waiting — the four threads it looked at and the reasoning that excluded each one.
The pressure in a batch follow-up tool runs the other way. A run that finds nothing looks like a run that did nothing, and the threshold can always be relaxed until something qualifies — counting a thread where the recipient said they would reply on Thursday, or one where no reply was expected.
These drafts are sent to real recipients. A tool that pads the queue has to be checked row by row, at which point writing the follow-ups directly costs less.
Listing the reviewed threads alongside the empty result makes the judgement checkable rather than asserted.
Monday morning suits the cadence: a four-day threshold means anything sent in the second half of the previous week is not yet due, and anything from the week before it is.
The exclusion for threads already followed up is what makes a weekly schedule safe to leave running. Without it, the same unanswered thread reappears in the queue every Monday.
