How to Follow Up on a Meeting Request by Email (Templates)
Last updated: October 2026
Direct answer: Wait three to four business days on a non-urgent request, then reply in the same thread with a one-line bump and two specific times (day, date, range, timezone). Ask which works — or for a counter-window if neither does. Do not resend “let me know when you’re free,” and stop after two follow-ups.
Silence after a meeting request is usually calendar friction, not rejection. The first email may have been too open-ended, buried under other mail, or sent when their week was already full. A good follow-up shrinks the ask so they can answer with a single pick. Below: when to bump, what to write, templates for work and networking, and how to refresh the times you offer.
When to follow up (and when not to)
| Situation | Wait before first bump | Notes |
|---|---|---|
| Internal team sync | 1–2 business days | Same Slack/Teams thread is fine if that is where you asked |
| Client or partner call | 3–4 business days | Keep the tone light; they may be in delivery crunch |
| Networking or coffee chat | 4–5 business days | You are asking for a favour — do not rush |
| Recruiter / interview thread | 2–3 business days | They often wait on other calendars; stay flexible |
| Same-day urgent block | Same afternoon or next morning | Only when the meeting must happen this week |
Do not follow up if they already declined, asked you to hold, or said they would come back after a specific date. In those cases, wait for their date or reschedule with fresh options when they reopen the thread.
Stop after two follow-ups. A third bump rarely converts and starts to feel like pressure. If there is still no reply, park the request or switch to an async alternative (shared doc, short Loom, email Q&A).
What every follow-up needs
A follow-up that gets answered has five parts. Skip any of them and you often get another silent week.
- Same thread. Reply under the original ask so context is one click away.
- One sentence of context. “Following up on finding 30 minutes for [topic].”
- A smaller ask. Two concrete windows beat “any update?” or another open calendar question.
- Timezone + duration. Even if you said them before — forwarded threads lose the top of the email.
- An easy out. “If neither works, suggest a window and I will make one fit” or “happy to push this to next month.”
The goal is a yes/no or a single counter-proposal — not another round of unbounded scheduling work. That is the same principle as proposing meeting times and asking for availability: constrain the question.
Email templates (copy and send)
Use plain text with one day per line. Soft line breaks inside a paragraph look fine in your draft and break on mobile; put each day on its own line so the list stays scannable.
Soft bump with two fresh times (default)
Subject: Re: [Original subject]
Hi [Name],
Following up on finding [duration] for [topic]. Would either of these work (all [timezone])?
[Day (Date)]: [time range]
[Day (Date)]: [time range]
Happy to take whichever is easier, or adjust if you send a better window.
Thanks,
[Your name]
Filled-in example:
Subject: Re: Q2 campaign sync — a few times that work
Hi Sarah,
Following up on finding 30 minutes for the Q2 campaign sync. Would either of these work (all EST)?
Tue (3/24): 10am–12pm
Thu (3/26): 1–3pm
Happy to take whichever is easier, or adjust if you send a better window.
Thanks,
Alex
After you asked “when are you free?” (fix the open ask)
If your first email was open-ended, the follow-up should propose, not ask again.
Subject: Re: [Original subject]
Hi [Name],
Circling back on [topic]. To make this easier, here are two windows that work on my side (all [timezone]):
[Day (Date)]: [time range]
[Day (Date)]: [time range]
Reply with a preference and I will send an invite. If neither fits, suggest a couple of times and I will lock one in.
Best,
[Your name]
Client or senior stakeholder (more room, less pressure)
Subject: Re: [Original subject]
Hi [Name],
Just bumping this gently — still hoping to find [duration] for [topic] when it is convenient on your side.
A couple of options that work for me ([timezone]):
[Day (Date)]: [time range]
[Day (Date)]: [time range]
No rush if this week is packed; a better window next week is fine too.
Thanks,
[Your name]
Networking or coffee chat
Keep it short. You are asking for their time.
Subject: Re: [Original subject]
Hi [Name],
Quick follow-up in case this got buried — still up for [duration] on [topic] if useful.
Two times that work for me ([timezone]):
[Day (Date)]: [time range]
[Day (Date)]: [time range]
Totally understand if timing is tough; happy to try again another month.
Best,
[Your name]
For the first outreach patterns, see how to schedule a coffee chat and share availability for networking.
Recruiter or interview coordination
Recruiters often need more options across a few days because they are aligning other people.
Subject: Re: Interview availability — [Role]
Hi [Name],
Following up with refreshed windows for the [duration] interview (all times [timezone]):
[Day (Date)]: [time range]
[Day (Date)]: [time range]
[Day (Date)]: [time range]
Happy to lock whichever works on your side. If the panel needs a different day, send two alternatives and I will confirm quickly.
Best,
[Your name]
More interview-specific patterns: how to send availability to a recruiter.
Slack or Teams (same idea, fewer words)
Following up on [topic] — free Tue 10–12 or Thu 1–3 (EST). Reply with a pick and I’ll invite.
Chat formatting tips: share availability in Slack and Microsoft Teams.
Refresh the times — do not recycle stale slots
A weak follow-up resends the same three options from last week. Calendars move. Before you bump:
- Re-check Google Calendar, Outlook / Microsoft 365, or Apple Calendar for the days you will name.
- Prefer ranges over single points so one small conflict does not wipe the option.
- Prefer new days when the old ones have passed or look crowded.
- Keep the list format:
Day (Date): time range, timezone once, one day per line.
ShareAvailability reads your calendar (Google, Outlook / Microsoft 365, or Apple via a public iCloud link) and copies a plain-text free-time list to your clipboard. Paste into the follow-up, send, done. The other person does not need an account — copy-to-clipboard plain text is the whole sharing method.
Follow up vs cancel vs reschedule vs decline
| Goal | Use this | Avoid |
|---|---|---|
| No reply yet to a request | Follow up (this guide) with two fresh times | Resending the same open question |
| Meeting already booked; need a new slot | Reschedule | Silently skipping the invite |
| Meeting must come off the calendar | Cancel | Ghosting after you accepted |
| You never accepted and cannot make it | Decline politely | A vague “maybe later” with no next step |
If they reply that none of your times work, switch from follow-up mode into a tight propose/ask loop: either send a fresh shortlist or ask for two windows on their side. Do not restart with “whenever works.”
Common mistakes
- Following up too soon. Same-day bumps on non-urgent asks feel pushy. Give people a few business days unless the deadline is real.
- “Just checking in” with no times. That asks them to reopen an unbounded calendar problem. Attach two options.
- Recycling last week’s slots. Offer windows you can still honor.
- A third and fourth bump. Two follow-ups is enough; after that, accept the soft no.
- Changing the channel every time. Email → Slack → LinkedIn multiplies noise. Stay in the thread where the request started unless they clearly live in another tool.
- Missing timezone. Wrong-hour invites are a common reason people go quiet after a “yes.”
- Defaulting to a booking page in a warm thread. In an existing conversation, a plain-text list of free times is usually clearer and keeps the reply in one place. ShareAvailability’s product path is clipboard text for the message you are already writing — not a share URL for them to open.
Frequently Asked Questions
How long should I wait before following up on a meeting request?
Three to four business days for a typical non-urgent work or client request. Wait a bit longer for networking favours, and a bit less when a recruiter is coordinating an interview panel. Same-day follow-ups are only appropriate when the meeting must happen this week.
What should I say in a follow-up email for a meeting?
Reply in the same thread, name the topic and duration in one line, and offer two specific times with a timezone. Ask them to pick one or suggest another window. A yes/no question gets answered where “any update?” does not.
How many times should I follow up on a meeting request?
Twice. Send a first bump with fresh options, wait another few business days, then one final short bump. If there is still no reply, stop. A third follow-up rarely helps and can damage the relationship.
Should I follow up with new times or ask when they are free?
Follow up with new times. If the first message was already open-ended, proposing two windows is how you fix it. Ask for their availability only when their calendar is clearly the hard constraint — for example, an interviewer lining up other people.
What if they reply but never pick a time?
Shrink again: offer one preferred slot plus one backup, or ask them to send two windows you can match. If the thread stalls after that, offer an async alternative or revisit later. Endless polite nudges without a smaller ask rarely book the meeting.
Is it okay to follow up on a meeting request in Slack instead of email?
Yes, if that is where the original request lived. Keep the same structure: short context, two times, clear ask. Do not bounce between email, Slack, and LinkedIn for the same ask unless they ask you to switch.
TL;DR
- Wait a few business days, then bump once in the same thread.
- Offer two fresh, real windows with timezone — do not resend “when are you free?”
- Make the ask answerable in one line; give an easy out.
- Stop after two follow-ups.
- Pull accurate free times with ShareAvailability before you paste the list.
Related Guides
- How to propose meeting times by email: structure for the first message so you need fewer follow-ups.
- How to ask for availability: when their calendar is the constraint and you should ask instead of propose.
- How to send availability in email: paste-ready patterns for Gmail and Outlook.
- How to reschedule a meeting: when the meeting already exists and you need a new slot.
ShareAvailability turns Google Calendar, Outlook / Microsoft 365, or Apple Calendar (public iCloud link) into a plain-text list of free times. Copy, paste, send. Free. The other person does not need an account.
Share your availability as plain text
No booking links. Generate availability as text from your calendar and paste into any email, Slack, or text.
Free · Read-only calendar access