If a work email gets no reply, wait two to three business days (or until the day after any date they gave you), then reply in the same thread with a short message that restates what you need and by when. If that also goes unanswered, make the second follow-up easier to answer than the first, and make the third a brief note that closes the loop.
Most advice on this topic is written for sales outreach, where the reader is a stranger and the goal is a reply rate. This guide is for the emails you send to people you work with: a colleague who owes you a file, a client sitting on a decision, a manager whose sign-off you need, a recruiter who went quiet after the interview. With these people, a follow-up has two jobs. It has to get an answer, and it has to leave the relationship exactly where it was. If you are chasing cold prospects instead, the follow-up email templates cover sales sequences.
Key takeaways
- Wait two to three business days for most work email. If they named a date, follow up the day after it.
- Reply in the original thread so your first request is one scroll away.
- Restate the ask as one question the reader can answer quickly, and give the real date you need it by.
- "Just following up" and "as per my last email" describe your waiting, not your request. Replace them with the request itself.
- The second follow-up should be easier to answer than the first: a yes/no question, two options, or a smaller piece of the ask.
- The final follow-up says what you will do next, so their silence stops blocking you.
- After two unanswered emails, change the channel or the person you ask, not the wording.
Why your email got no response
An unanswered work email is usually not a refusal. It arrived at a bad moment, it needed more than a minute to answer, or it reached someone who cannot answer it. Work out which before you write the follow-up, because each one needs a different fix.
| What probably happened | Typical sign | What the follow-up should change |
|---|---|---|
| It got buried | The ask was small; the person is busy or traveling | Only the length. Resend the ask, shorter, in the first line. |
| Answering takes real work | You asked for a decision, a review, or numbers | Make the ask smaller, or offer options they can pick in one line. |
| They are not the right person | The request crosses teams, or their role changed | Ask who should handle it. |
| They are waiting on someone else | Budget, approvals, their own client | Ask for a status or an expected date, not the final answer. |
| The answer is no, and they would rather not say it | A quote, a job application, a partnership | Make "no" easy to send. |
The second row is the one people miss. If your first email asked for something that needs time and thought, sending the same question again puts it back at the bottom of the same list, for the same reason it sat there the first time.
How long to wait before following up
For most work email, two to three business days is a fair wait. If the person gave you a date ("I'll get back to you by Friday"), follow up the day after that date and not before. Go sooner only when a real deadline is close, and then say what the deadline is.
These are common workplace norms, not research findings. No study sets a correct interval for work email, so adjust for how quickly this person usually replies and how much your request asks of them.
| Who you are waiting on | First follow-up | Next one |
|---|---|---|
| Colleague, quick question | 1 to 2 business days, often as a chat message | Ask in person or in a shared meeting |
| Colleague, a file or a review | The day after the agreed date; with no date, 2 to 3 business days | About a week later |
| Manager, approval or sign-off | 2 to 3 business days, sooner if a deadline is days away | When the deadline is at risk, in person |
| Client, after a proposal or a question | 3 to 5 business days | About a week later |
| Vendor or supplier who owes you something | The day after the promised date | 2 to 3 business days later, by phone if it is blocking you |
| Recruiter, after an interview | The day after the date they gave; with no date, about a week | About a week later, then stop |
| Overdue invoice | The day after the due date | About a week later, then call |
| Someone you were introduced to | About a week | One more, a week or two later, then stop |
Whatever the interval, write the date you actually need in the email. People are poor at guessing a sender's timeline: in a 2021 study of work email, recipients consistently overestimated how quickly senders expected replies to non-urgent messages. A stated date removes the guess.
What to write in a follow-up email
A good follow-up after no response is three or four sentences in the same thread: what this is about, the ask restated so it can be answered quickly, the date you need it by and why, and an easy way to say "not yet." Leave out the recap of your first email and any comment on the silence.
- Reply in the original thread. The reader sees your first message below the new one and does not have to search for it.
- Open with the topic, not the waiting. "Following up on the vendor shortlist" works because it names the item. "Just following up" on its own does not.
- Restate the ask as a question. One question, phrased so it can be answered in a line: "Can you approve it as is, or should I change the dates?"
- Give the date and the reason. "By Thursday, so I can send it to the client on Friday" is easier to prioritize than "when you get a chance."
- Leave room for "not yet." "If you need more time, a rough date is fine" turns a reply the reader was avoiding into one they can send now.
Hi Dana, just following up on my email from last week. Let me know your thoughts when you get a chance.
Hi Dana, following up on the [document] I sent on [date]. Could you tell me by [date] whether it works as is, or what you would change? If you need more time, a rough date is fine.
The first version tells Dana you are waiting. The second tells her what to answer and by when, and makes "not yet" an acceptable reply.
If what you need is a progress report rather than an answer, how to ask for an update politely has ten phrasings by formality level.
Follow-up email subject lines
The best subject line for a follow-up is usually the original one: reply in the thread and leave it as "Re: [original subject]." Write a new subject only when you have to start a new email, for example because the first went to the wrong address or the thread has drifted to another topic. Then name the item and, if there is one, the date.
- Re: [original subject] (the default)
- [Item]: decision needed by [date]
- Following up: [proposal name], sent [date]
- Invoice [number], due [date]
- [Role] interview on [date]: next steps
- Question about [specific item]
Subject lines to avoid: "Following up," "Checking in," and "Any update?" on their own say nothing about the content. "Friendly reminder" tends to read as the opposite of friendly. "URGENT" in capitals, when the matter is not, teaches the reader to discount your next urgent email.
Phrases that make a follow-up sound pushy, and what to say instead
The phrases to drop are the ones that talk about your previous email instead of your request. They suggest the reader ignored you, and they still do not say what you need. In a 2018 Adobe survey of more than 1,000 white-collar workers, "Not sure if you saw my last email" was voted the most annoying phrase in work email, with "Per my last email" second.
Part of the problem is that you hear your own tone and the reader does not. In a series of experiments on email, senders overestimated how well their tone came across. A line you meant as neutral can arrive sounding irritated.
| Phrase | How it reads to them | Say instead |
|---|---|---|
| "Just following up" | You have nothing new to say, and they must open the old email to learn what you want | "Following up on [item]: could you [ask] by [date]?" |
| "As per my last email" | "I already told you, and you didn't read it." | Restate the point: "To recap, [point]." |
| "Not sure if you saw my last email" | An accusation phrased as a question | Leave it out. The thread already shows your last email. |
| "Bumping this to the top of your inbox" | Your request outranks everything else they have | Leave it out and put the ask in the first line. |
| "I still haven't heard back" | You are keeping score | "Is this still something you can help with, or should I ask someone else?" |
| "Sorry to bother you again" | Your request is a nuisance, and they may agree | "Thanks for taking a look at this." |
| "Friendly reminder" | The word "friendly" signals the opposite in writing | "A reminder that [item] is due on [date]." |
| "Any update?" with nothing else | Fine with close teammates. To others, terse, and they have to guess which update | "Any update on [item]? I need it for [reason] on [date]." |
Hi Mark, as per my last email, I still need the signed contract. Not sure if you saw it. Please advise.
Hi Mark, could you send the signed contract by [date]? We need it to [reason]. If something in it is holding things up, let me know.
All three phrases in the original point at Mark's silence. The rewrite drops them and spends the same space on the ask, the date, and a way to raise a problem.
For a wider pass on tone than these phrases, the business email tone checklist walks through seven checks before you send.
Check how your own follow-up reads
We never store your text or use it to train AI.
221/800
Paste your draft above, or edit the example. The email tone checker shows which lines may read as impatient, cold, or too casual, and suggests a warmer version of the line that needs it most. If you would rather start from a cleaner draft, the email rewriter rewrites the whole message in a professional tone and keeps your facts as they are.
First, second, and final follow-up: what changes
Each follow-up should do something the previous one did not. The first one resurfaces the ask. The second makes it easier to answer. The final one closes the loop by saying what you will do if you do not hear back. Sending the same message three times only shows that you are still waiting.
| First follow-up | Second follow-up | Final follow-up | |
|---|---|---|---|
| Its job | Bring the ask back to the top | Lower the effort of replying | Let both of you move on |
| What it adds | The date you need it by | A smaller ask, options, or a yes/no question | The fallback you will take |
| Length | Two to four sentences | Shorter than the first | Two or three sentences |
Here is how the three look for one request: a client has not approved a homepage draft.
First follow-up:
Hi Sam,
Following up on the homepage draft I sent on [date]. Could you let me know by [date] whether it is approved or what you would like changed? We need it to keep [launch date] on track.
Thanks, [Your name]
Second follow-up:
Hi Sam,
Reviewing the full draft takes time, so here is a shorter question: are you happy with the headline and the first section? If so, I will start on those and we can come back to the rest. A one-line reply is plenty.
[Your name]
Final follow-up:
Hi Sam,
Since this has not come together over email, I will plan on [your fallback]. If you would like a different plan, reply here or call me at [number] and we will sort it out.
[Your name]
Only name a fallback you can take without their approval. "I will hold the slot until Friday" is fair. "If I do not hear back, I will treat this as approved" is not, when the approval actually matters: contracts, payments, anything legal, anything published under their name. In those cases the final note should say that the work is paused until they reply.
Reminders before something is due, such as a meeting or a deadline, follow a lighter pattern. How to remind someone politely covers those.
Follow-up email examples by situation
The structure stays the same in every situation. What changes is how much context the person needs, and what makes replying hard for them.
To a colleague who owes you something
Colleagues usually stall because something else is on fire, not because they object. Name the piece you need and what it unblocks for you, and offer help if the blocker might be on your side. For a quick question, a chat message often beats a second email.
Subject: Re: [original subject]
Hi [name], checking that the [file] is still on track for [date]. I need it to finish [your part]. If something is in the way, tell me and I will see what I can take off your plate.
To your manager
Managers answer decisions faster than open questions. Lead with the decision you need, then the deadline, then a one-line summary so they do not have to reopen the original.
Hi, sorry to bother you again about the budget. I know you're really busy, but I was just wondering if you might have had a chance to look at it yet?
Hi [name], could you approve the [budget] by [date]? I need it to [next step]. If you have questions, I can walk you through it after [meeting].
The original spends three clauses apologizing before it reaches a vague question. The rewrite starts with the decision and keeps the courtesy in the offer at the end.
To a client waiting on a decision
With clients, the risk is not the delay but the relationship. Ask whether the matter is still a priority, so they can tell you plans have changed without having to explain.
Subject: Re: [proposal name]
Hi [name], following up on the [proposal] from [date]. Is this still a priority on your side? If the timing has changed, that is completely fine. Knowing either way helps me plan [your next step].
To a vendor who has not delivered
Here you are the customer, so you can be direct. State what is late, ask for a new date rather than an apology, and say what depends on it.
Subject: Re: [order or project]
Hi [name], we have not received [item], which was due on [date]. Could you send a new delivery date by [date]? We need it to [reason].
After a job interview
Ask about the timeline, not the outcome. "Did I get the job?" puts the recruiter on the spot. "Is there an updated timeline?" is easy to answer even when the decision is not made yet. Send it to the person who has been coordinating with you, not to every interviewer.
Subject: [Role] interview on [date]
Hi [name], thank you again for speaking with me about the [role] on [date]. I am still very interested, and I wanted to ask whether there is an updated timeline for next steps. I am happy to send anything else that would help.
After sending a quote or proposal
Silence after a quote often means a question about price or scope that the client has not voiced, or a quiet no. Invite either one.
Subject: Re: Quote for [project]
Hi [name], following up on the quote I sent on [date]. Do you have any questions about it, or is something in the scope or price not working for you? If the project is on hold, just let me know and I will check back in [month].
When an invoice is overdue
Keep a payment follow-up factual, with no apology for asking. Attach the invoice again, because the original may be sitting in someone else's inbox, and ask who to contact if payment is stuck.
Subject: Invoice [number], due [date]
Hi [name], invoice [number] for [amount] was due on [date], and I have not seen the payment yet. I have attached it again. Could you confirm when it is scheduled to be paid? If it is waiting on an approval, let me know who I should contact.
After someone introduced you
Make the ask small and specific, so it costs a stranger little to say yes. Leave the person who introduced you off the follow-up; they made the connection, and keeping them in the thread puts pressure on both sides.
Subject: Re: Introduction: [your name] / [their name]
Hi [name], following up on [introducer]'s introduction on [date]. I would value a short reply on [specific question], or [length of time] on a call if that is easier. If now is not a good time, no problem at all.
Writing several of these at once? Draft them in Inki's editor, then select a phrase like "just following up" to compare alternative wordings in the context of your email. Start writing free.
No reply after two follow-ups: what to do next
After two unanswered emails, the wording is rarely the problem. Change the channel, change the person, or change the ask, and decide when you will stop.
Switch channels. A short chat message to a colleague, a phone call to a client or vendor, or a sentence at the end of a meeting you already share. Keep it to the ask: "Quick one on the [item] I emailed about. Can you approve it as is?"
Ask someone else. An assistant, a shared team inbox, a colleague on their team, the person who introduced you, or a recruiting coordinator. Be open about why you are writing: "I have been trying to reach [name] about [item]. Is there someone else who can help with it?"
Make the ask smaller. If the full request stalled twice, split it. Ask for the one part you cannot move without.
Escalate with notice. If the delay is blocking work, tell the person before you go above them: "If it is easier, I can raise this with [manager] so it gets prioritized." Adding their manager to the thread without warning tends to make the next conversation harder than the delay was.
Know when to stop. For a job application, a sales conversation, or an introduction, two follow-ups and a final note is enough. Silence after that is an answer, and the final note means you have already said goodbye politely.