How to Write a Meeting Request Email (Templates + Examples)

What every meeting request email needs

Skip any of these and you usually get silence or another round of “does Thursday work?”

1. A subject that names the meeting. Include the topic and, when useful, “times inside” so it is obvious in a crowded inbox.
2. One sentence on purpose and length. “30-minute project sync” or “45-minute intro” sets expectations before they open their calendar.
3. A bounded window. Next week, the week of the 22nd, or before Friday — not “sometime soon.”
4. Two or three concrete options. Day, date, time range, and timezone. Ranges beat single points when the other person needs a little flexibility.
5. A clear ask. “Reply with a preference and I will send a calendar invite.”
6. An escape hatch. “If none work, suggest a window and I will make one fit.”

That checklist is the difference between a professional meeting request and a vague ping that never books. After they pick, confirm the meeting in one line and send the invite the same day.

---

Subject lines that get opened

Name the meeting. Soft subjects like “Quick question” or “Circling back” hide the ask and get deferred. If times are in the body, saying so in the subject helps people who only skim.

---

Meeting request email templates (copy and send)

Paste into email. Keep each day on its own line so the list survives mobile clients. Soft line breaks inside a paragraph look fine in your draft and break on phones.

General business meeting

Subject: [Meeting topic] — a few times that work

Hi [Name],

Would you have [duration] for a [meeting topic] sometime [window]?

A few options on my side (all times [timezone]):
[Day (Date)]: [time range]
[Day (Date)]: [time range]
[Day (Date)]: [time range]

Reply with a preference and I will send a calendar invite. If none of these work, suggest a window and I will make one fit.

Thanks,
[Your name]

Filled-in example:

Subject: Q2 campaign sync — a few times that work

Hi Sarah,

Would you have 30 minutes for a Q2 campaign sync sometime next week?

A few options on my side (all times EST):
Wed (3/18): 10am–12pm or 2–3pm
Thu (3/19): 9–11am
Fri (3/20): 1–4pm

Reply with a preference and I will send a calendar invite. If none of these work, suggest a window and I will make one fit.

Thanks,
Alex

First outreach (intro or networking)

Keep it short. Lead with why you are asking, then the times.

Subject: Quick intro — times that work next week

Hi [Name],

I would love [duration] to [purpose]. A few windows that work on my side (all [timezone]):
[Day (Date)]: [time range]
[Day (Date)]: [time range]
[Day (Date)]: [time range]

Happy to take whichever is easiest for you, or adjust if none fit.

Best,
[Your name]

Filled-in example:

Subject: Quick intro — times that work next week

Hi Jordan,

I would love 20 minutes to compare notes on marketplace onboarding. A few windows that work on my side (all PST):
Tue (3/17): 10am–12pm
Wed (3/18): 1–3pm
Thu (3/19): 9–11am

Happy to take whichever is easiest for you, or adjust if none fit.

Best,
Sam

Client or stakeholder check-in

Subject: [Project] check-in — 30 min options

Hi [Name],

Could we find [duration] for a [project] check-in [window]? Agenda: [one-line agenda].

Times that work on my side (all [timezone]):
[Day (Date)]: [time range]
[Day (Date)]: [time range]
[Day (Date)]: [time range]

Reply with a preference and I will send the invite. If none work, send two windows that do.

Thanks,
[Your name]

Filled-in example:

Subject: Acme redesign check-in — 30 min options

Hi Priya,

Could we find 30 minutes for an Acme redesign check-in next week? Agenda: review homepage wireframes and lock feedback deadlines.

Times that work on my side (all EST):
Mon (3/23): 9–11am or 2–4pm
Tue (3/24): 10am–12pm
Wed (3/25): 1–3pm

Reply with a preference and I will send the invite. If none work, send two windows that do.

Thanks,
Alex

When their calendar is the hard constraint (they coordinate other people), ask for two or three windows instead of proposing — see how to ask for availability. If they ask you first, use how to reply when someone asks for your availability.

---

How to format the times inside the request

Example block:

All times EST
Wed (3/18): 10am–12pm or 2–3pm
Thu (3/19): 9–11am
Fri (3/20): 1–4pm

Two or three windows usually beat a wall of options. Recruiter or client threads can use four to six across a couple of days. Formatting detail: how to list availability in an email. Cross-timezone threads: share availability across time zones.

---

Meeting request vs calendar invite vs booking link

Default to a meeting request with plain-text times. Send the calendar invite after they pick — not before — unless your culture already accepts tentative holds. Use a booking page only when that is already the expected path between you. ShareAvailability’s product path is clipboard plain text for the email you are already writing, not a share URL.

---

Pull real free times before you send

The fastest way to kill a meeting request is offering a slot you are not free. Before you hit send:

1. Check Google Calendar, Outlook / Microsoft 365, or Apple Calendar for the days you named.
2. Prefer ranges over single points so a small conflict does not wipe the option.
3. Include the timezone every time — even for people in the same city — so forwarded threads stay clear.
4. Copy the list into the email as plain text. Do not paste screenshots; they are hard to reply to on mobile.

ShareAvailability reads Google Calendar, Outlook / Microsoft 365, or Apple Calendar (public iCloud link) and copies plain-text free times to your clipboard — no booking link required. Paste into Gmail, Outlook, Slack, or Teams and send. The other person does not need an account.

---

After they reply

1. Confirm in one line. “Thursday 10am EST works — invite coming.”
2. Send the calendar invite promptly with location or dial-in, duration, and any agenda.
3. If none of your options work, ask for two windows on their side, or send a fresh shortlist — do not restart with “when are you free?”
4. If they go silent, one short bump after three or four business days with two fresh options is enough. Stop after two follow-ups. Templates: how to follow up on a meeting request.

When the meeting already exists and you need a new slot, switch to reschedule templates. When you are saying no to an invite you never accepted, use decline politely.

---

Common mistakes

• “Let me know when you’re free.” Unbounded — add a window and propose options.
• Subject that hides the ask. “Quick question” gets parked; name the meeting.
• One exact time or ten single slots. One feels rigid; ten gets skimmed. Prefer two or three ranges.
• Missing timezone or unchecked times. Wrong-hour invites and immediate reschedules kill trust.
• Sending the invite before they agree. Surprise holds create declines. Agree in email first.
• Defaulting to a booking link in a warm thread. Plain-text options usually get a faster pick.

---

Frequently Asked Questions

How do I write a meeting request email?

Name the purpose and duration, list two or three specific free windows with a timezone (one day per line), and ask them to pick one or suggest another window. Clear options beat an open-ended “when are you free?”

What should the subject line of a meeting request say?

Name the meeting topic and, when useful, that times are inside — for example, “Q2 campaign sync — a few times that work.” Soft subjects like “Quick question” hide the ask.

How many meeting times should I include in a request?

Two or three for a simple one-to-one. Four to six across a couple of days for recruiter or client threads. Prefer ranges over single points so small conflicts do not kill every option.

Should I send a calendar invite with the first meeting request?

Usually no. Agree on a time in email first, then send the invite the same day you confirm. Send a tentative invite only when your culture already uses holds that way.

Is a Calendly or booking link better than a meeting request email?

Only for high-volume inbound meetings where self-serve booking is already expected. In an existing thread, pasteable free times plus a normal calendar invite after they pick usually feel clearer and keep the conversation in one place.

What if none of my proposed times work?

Ask them for two windows that do, or send a fresh shortlist from later days. Keep the same plain-text format so the next reply can still be a single pick.

---

TL;DR

1. Write a meeting request that states purpose, duration, and timezone — then list two or three real windows.
2. Format as Day (Date): time range, one day per line.
3. Ask them to pick one; offer an escape hatch if none work.
4. Confirm in one line and send the calendar invite promptly — do not lead with a surprise invite.
5. Pull options from your real calendar with ShareAvailability so you do not propose busy slots.

---

Related Guides

• How to propose meeting times: deeper formatting and option-count guidance.
• How to ask for availability: when their calendar is the constraint.
• How to reply when someone asks for your availability: answering “when are you free?”
• How to follow up on a meeting request: short bumps when the thread goes quiet.
• How to confirm a meeting: locking the slot after they reply.

---

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.