How to follow up on an email without annoying anyone

The short answer

Follow up on the same thread, a few working days after your first email, with one new piece of information and one clear question. Keep it short, make it easy to answer yes or no, and say what happens if you do not hear back. That reads as organized rather than pushy. The timing below is a rule of thumb from experience, not a researched standard, so shorten it when something has a real deadline.

Why people hold back, and why it is usually fine

Most unanswered emails are not refusals. They were opened on a phone, meant to be answered later and buried. A follow-up is the second chance for the same message to land. Being annoying comes from how you follow up, not from the fact that you did.

When to send it

• Routine request: three to five working days.
• Time-bound request: a day or two before the deadline you gave, and say so.
• Sales or outreach: a week, then another a week or more later, and stop after two or three.
• After a meeting: send your own recap the same day, then follow up on open items by the date you stated.

How to write it

1. Reply on the same thread. The original message and its context stay below your note. A new email with a new subject loses both.
2. Add something. A new fact, a deadline, an attachment, a shorter version of the ask. "Just checking in" adds nothing.
3. Ask one thing. Two questions halve the chance of an answer.
4. Make it easy. Offer a yes or no, two time options, or a one-line choice.
5. Leave a way out. "If this is not a priority right now, tell me and I will close it on my side" gets replies from people who were stuck.
6. Keep it to four sentences. If you need more, the original was too long.

A template

Hi Maya, following up on the Thursday call. I have attached the two-page scope so you do not need to dig for it. Can you confirm by Friday that we are on for the 12th, or tell me what is blocking it? If the timing has changed, a one-line reply is enough and I will adjust.

Examples for common cases

After an interview or a pitch. "Thank you again for Tuesday. You mentioned a decision by the end of the month. Is there anything else I can send to help?" One question, a reference to what they said, no pressure.

For a document or an answer you need. "Could you send the signed form by Thursday? Without it I cannot book the room. If it is easier, a photo of the signed page is fine." It names the consequence and lowers the effort.

For an invoice or a payment. "This invoice was due on the 3rd. I have attached a copy in case the original got lost. Could you confirm when it will be paid?" Polite, factual, and with the document attached.

For a colleague who owes you input. "I am sending the draft to the client on Friday at noon. I still need your section. Can you get it to me by Thursday evening, or tell me what is blocking it?" Specific about the deadline and the reason.

What not to do

• Do not send the same text twice. Change the angle.
• Do not copy extra people in to apply pressure. It shifts the tone from help to escalation.
• Do not follow up daily. Space them, and decide in advance when you will stop.
• Do not write "per my last email". It reads as a reproach.

Remember to follow up at all

Most late follow-ups are forgotten ones. The fix is to decide when you send. Superhuman's Mail page describes reminders if nobody replies in a time you pick, and SaneBox lists reminders when someone does not respond. Many mail apps have some version of this.

In Otto you can set a follow-up on a thread and it watches for you: if a reply arrives, the reminder cancels itself, and if none does, the thread comes back. The snooze and follow-ups guide explains it, and the assistant can set one when you ask. It is our product, and the habit matters more than the app.

When to stop

Two or three follow-ups over a few weeks is a reasonable ceiling for most requests. After that, send a brief closing note, such as "I will take this as a no for now and am happy to pick it up later", and move on. It ends the loop on your side and often prompts the answer.