How to write a follow-up email that gets a reply
A step-by-step guide to follow-up emails that get answered, with copy-paste templates and timing rules that work without any tool.
Harsha Gaddipati
May 12, 2026 · 8 min read

Most replies are lost to silence, not rejection. The recipient meant to answer, the email slid down the inbox, and the moment passed. A good follow-up is not nagging. It is a second, easier chance for someone who already wanted to say yes. The catch is that a bad follow-up ("just checking in", "bumping this up", "any thoughts?") gives the reader nothing new to act on, so it gets ignored a second time. This guide covers the structure, the exact wording, and the cadence that turns a dead thread back into a conversation.
Step 1: Decide whether a follow-up is even the right move
Before you write anything, ask one question: did the last email give the reader a clear, low-effort action? If the original was a vague "let me know what you think", the problem is not that they forgot. The problem is they did not know what you wanted. In that case, do not "follow up" on the old email. Send a new, sharper ask instead.
Follow-ups work when the original request was clear and the reader simply ran out of attention. They fail when you are reheating an unclear request. So the first move is honest triage: was the ball in their court, with an obvious next step, or did your first email leave them with homework?
Step 2: Open with context, not an apology
Do not start with "Sorry to bother you" or "I know you're busy." Apologizing frames your own message as an interruption and trains the reader to treat it as skippable. Instead, anchor the reader in the original thread in one line so they do not have to scroll or remember.
Reply on the same thread whenever you can. Keeping it in the existing chain preserves the subject line, the prior context, and any attachments, so the reader has zero reconstruction cost. A fresh email with a new subject forces them to rebuild the situation from memory, which is exactly the friction that kills replies.
One clean opener: "Following up on the proposal I sent last Tuesday." That is it. Context set, no groveling.
Step 3: Make the ask a single, specific, yes/no-able question
The most common reason a follow-up dies is that it asks for "thoughts." Thoughts are open-ended and expensive to produce. A reply-worthy follow-up narrows the ask to one decision the reader can make in seconds.
Compare these:
- Weak: "Any updates on the contract?"
- Strong: "Are you good to sign the contract this week, or should I push the start date to the 15th?"
The strong version offers two concrete options, so the reader can reply with one word. Give people a question they can answer without thinking, and far more of them will answer.
If you genuinely need a longer response, say what you need and how long it will take: "Could you send the two logos by Thursday? Should be a 5-minute pull from your brand folder." Naming the effort lowers the perceived cost of replying.
Slashy drafts replies in your voice, sorts what matters, and keeps important conversations moving.
Step 4: Get the timing and cadence right
Send the first follow-up 2 to 3 business days after the original, not the next morning. Same-day nudges read as anxious and arrive before the reader has had a fair chance to act. A few business days is long enough to be reasonable and short enough that the thread is still warm.
For sales or partnership threads, a workable cadence is roughly:
- Follow-up 1: 2 to 3 business days after the first email
- Follow-up 2: 4 to 5 business days after that
- Follow-up 3: about a week later, framed as a soft close
- Then stop, or move to a different channel
Space each touch a little wider than the last. And send during the reader's working hours in their time zone, not yours. An email that lands at 6am their time gets buried under the morning flood.
Step 5: Write a real subject line and end with an easy out
If you must start a new thread, the subject line carries the open. "Quick question on the Q3 numbers" beats "Following up" because it tells the reader what is inside. Specific subjects get opened. Vague ones get archived.
Close with a genuine off-ramp on your final touch: "If now is not the right time, just say the word and I will check back next quarter." Giving the reader permission to say no often produces a yes, because it removes the pressure that makes people avoid the reply altogether. An easy out also keeps the relationship intact for later.
Copy-paste follow-up templates
Here are three templates you can adapt. Keep them short. The whole message should be readable in one screen without scrolling.
Gentle first nudge:
Subject: (reply on the original thread)
Hi Priya,
Following up on the partnership deck I sent last Tuesday. Are you open to a 20-minute call this week to walk through it? Tuesday or Thursday afternoon both work on my end.
If the timing is off, no problem, just let me know and I will work around your schedule.
Thanks, Sam
Decision-forcing second nudge:
Hi Priya,
Circling back on the partnership deck. Two quick options: we can lock in the pilot for a June 1 start, or push to July if your team needs more runway. Which works better for you?
Happy to answer anything before you decide.
Sam
Soft close (final touch):
Hi Priya,
I do not want to keep cluttering your inbox, so this is my last note on the deck for now. If a pilot is interesting this quarter, I would love to set it up. If not, I will check back in the fall.
Either way, thanks for the time.
Sam
How Slashy automates this
The hard part of follow-ups is not the writing. It is remembering who has gone quiet and circling back at the right moment, across dozens of open threads. That is exactly the manual work Slashy removes.
Slashy is an AI-native email and calendar client built on an in-house memory system that learns your writing voice over time. When you send an important email, you can set a follow-up reminder with ghost detection: if the recipient does not reply by the time you chose, Slashy pings you so the thread never slips. Open tracking shows whether your message was even opened, with device and count, so you know whether you are waiting on a reader who has not seen it or one who is sitting on a decision.
When it is time to follow up, Slashy drafts the nudge in your tone, not a generic template, because the memory has learned how you write to that recipient. Draft acceptance climbs from around 30% on day one to over 80% by day 30 as the memory adapts. The calendar sidebar lives next to the inbox, so proposing a meeting time inside a follow-up takes one glance instead of a tab switch. For sales and partnership threads, Attio and HubSpot integration on the Professional tier keep the CRM in sync without copy-paste.
Slashy Professional is $30/user/month, or $300/year billed annually, and the product is SOC 2 Type II and CASA Tier 2 certified, with data encrypted at rest and in transit. Slashy supports Gmail and Google Workspace today, with Outlook coming soon.
Last updated: May 12, 2026
Visit Slashy
AI-native email and calendar client for founders and operators.
Frequently asked questions
Have more questions? Visit our Help Center.
Related reading
- How to set up email follow-up reminders
- Email Automation for Founders: What to Automate and How
- State of Founder Email 2026
Connect Gmail and see Slashy with your own email.

How to Connect Your Email to Cursor With an MCP Server
Connect your inbox to your IDE. This guide shows you how to set up an email MCP server for Cursor using Slashy to query, draft, and schedule without…

Salesforce Email Integration: Stop Logging Activities by Hand
Learn how to set up Salesforce email integration with Gmail. Automate activity logging, use AI to draft replies, and track email opens without manual…

HubSpot Gmail Integration: Log Emails and Follow-ups Automatically
Master your HubSpot Gmail integration to automate CRM logging and follow-ups. Learn how Slashy uses AI to track opens and draft replies with CRM context.
Let your inbox do the follow through
Slashy drafts replies, tracks what is waiting, and keeps important conversations moving.