Meeting Request Email: Structure, Templates

What goes into a meeting request email?

A meeting request email asks one person for one specific meeting. Indeed's career guide puts it this way: the sender usually suggests a day, a time and a place, and says what the meeting is about. One of the top-ranking Google guides adds a limit for the subject line: nine words at most, ideally three to five. Google's AI overview for this search names two to three proposed time slots and a single call to action. Everything else follows from one rule. The reader should be able to say yes without writing back to ask what you mean.

1. 1 Subject line: the topic plus a word that signals a meeting, e.g. "Quick call on your onboarding rollout".
2. 2 Opening line: why this person, written for them. A trigger such as a role change, a job post or a product launch, not "I hope you're well".
3. 3 Purpose: one sentence on what you'll cover and what they get out of it.
4. 4 Format and length: call, video or in person, and how long it takes.
5. 5 Time slots: a few options with the date, the time and the time zone written out.
6. 6 One ask: "Does Tuesday at [time, time zone] work?" One question, not three.

Common mistakes: no time zone, so the recipient has to guess whether the time is yours or theirs. An open question like "when are you free?", which hands the scheduling work to the recipient. And an agenda so long that the meeting itself looks like a chore.

How do I politely request a meeting?

Being polite in a meeting request comes down to making it easy to decline. Give a specific duration so the recipient knows the cost. Offer slots instead of demanding one. Add a line that leaves a way out, such as "if someone else on your team owns this, a name is just as helpful." Skip any phrase that assumes the answer is yes, like "I've already put time in your calendar". Sending a calendar invite before anyone has agreed puts an entry in the recipient's calendar that they never asked for, and that reads as pushy, not polite.

The tone should match how well you know them. With a colleague, "Can we grab a few minutes on the budget this week?" is fine. With a stranger you need the reason before the ask, because they have no context for why you're writing.

Meeting request email templates

Cold meeting request to a prospect

Subject: [Topic] at [Company]. Hi [First name], I saw [specific trigger, e.g. you're hiring SDRs in Berlin]. We help [type of team] with [one problem]. Would a short call make sense to see whether that applies to you? I could do [Day, Date] at [Time, Time zone] or [Day, Date] at [Time, Time zone]. If this isn't on your desk, who should I ask instead? [Name]

Warm request to an existing contact

Subject: Quick sync on [project]. Hi [First name], before [deadline or milestone] I'd like to go through [two items] with you. [Duration] should be enough. Are you free [Day] at [Time] or [Day] at [Time]? If neither works, send me a slot and I'll fit around it. [Name]

Internal meeting invitation

Subject: Decision needed: [topic], [date]. Hi team, we need to settle [decision] by [date]. I've booked [time, duration, room or link]. Please read [document] beforehand. If you can't make it, reply with your input by [time] so it still counts. [Name]

How to write an email inviting someone to a meeting

An invitation is not the same thing as a request. A request asks whether someone will meet. An invitation confirms a meeting that is already planned. The invitation needs the facts someone would put in their calendar: date, start and end time with the time zone, location or video link, who else is coming, the agenda, and anything to prepare. If you send it as a calendar invite, the time and link sit in the invite itself. The email body only has to carry the agenda and say why the meeting exists.

How do I request a meeting via Outlook?

1. 1 Open the Calendar and choose New event (in classic Outlook: New Meeting).
2. 2 Add the attendees' addresses in the Required or Optional field.
3. 3 Use the Scheduling Assistant to check free/busy times. For people outside your organisation it usually shows no availability, so pick a time you've already agreed.
4. 4 Enter the title, the location or Teams link, and the agenda in the body.
5. 5 Click Send. Each attendee gets an invite with Accept, Tentative and Decline options.

This works well inside a company. For a cold prospect, ask by email first and send the Outlook invite only once they've agreed to a time.

How to reply to an email with a meeting request

Reply in the same thread and answer the actual question. Accepting: "Tuesday at [time] works. Send the invite to this address." Proposing another time: "Tuesday's full for me. Could we do Wednesday or Thursday morning, [time zone]?" In Outlook, Propose New Time does the same job from inside the invite. Declining: "Thanks, this isn't a priority for us right now. Please take me off the follow-ups." A clear no saves both sides from a chain of reminders. If you're the sender and you get a no, stop the sequence for that address before the next scheduled email goes out.

Follow-up sales email: when and how to send one

Many meeting requests don't get an answer the first time, so plan the follow-up from the start. Send it as a reply to your original email, not as a new message. A real reply carries the In-Reply-To and References headers, which mail clients use to show it in the same conversation, with your first request quoted underneath. Typing "Re:" on a new email doesn't set those headers, so it lands as a separate conversation, and recipients can tell. Each follow-up should add one new thing, like a short example, a different time slot or a different person to ask, and the sequence should end after a fixed number of touches you set in advance.

Sales follow-up email template

Hi [First name], picking this back up in case it got buried. Since my last note, [one new fact, e.g. we published how teams like yours handle X]. Still worth a short call? I have [Day, Time, Time zone] open. If the timing's wrong, a one-word "later" is fine and I'll check back next quarter. More variations by situation are collected in our sales follow-up email template examples.

Booking link, proposed slots or calendar invite?

There are three ways to set the time. You can name slots in the text, add a self-service booking page from a scheduler such as Calendly, Microsoft Bookings or Google Calendar's appointment schedules, or send a calendar invite straight away. Which one fits depends on how well you know the recipient.

Method	How it works	Fits	Where it stops
Proposed slots in the email	You write a few times; the recipient replies with one	Cold and warm requests; the recipient only types one word	Slots can expire before the reply; you need to hold them or re-offer
Booking page link	Recipient picks a free time from a page synced to your calendar	Warm contacts and inbound leads who already want the meeting	In a first cold email it asks the stranger to do the scheduling work; an extra link also adds a domain the filter evaluates
Calendar invite (.ics / Outlook / Google)	Event lands directly in the recipient's calendar	Internal meetings and times already agreed	Unrequested invites to prospects create calendar entries they never asked for

Email prospecting: where the meeting request fits

Email prospecting means contacting potential buyers who haven't contacted you yet, in order to find out whether there's a fit. The meeting request is the ask at the end of that work. It isn't the whole message. If the research step is missing, meaning no trigger and no reason to pick this person, the request reads like a template sent to everyone, because that's what it is. Rules differ by market. Germany's UWG, section 7, requires prior consent for email advertising, and the requirement covers business recipients too. The US CAN-SPAM Act works on an opt-out basis. Check which rule covers your list before the first send. Our prospecting email examples show how research and ask sit together in one short message.

Cold email deliverability for meeting requests

The receiving server decides where a meeting request ends up, not the sender. What it checks is in your hands: SPF has to authorise the server that sends, DKIM has to sign the message with your domain, and DMARC tells the receiver what to do when either check fails. Common failures are a second SPF record on the same domain, which makes SPF return a permerror; DKIM signed with the sending platform's domain instead of yours, which fails DMARC alignment; and a sudden volume spike from a new domain. Our guide on cold email deliverability walks through each factor, and the SPF, DKIM and DMARC checker shows what your domain publishes right now.

What is a good email deliverability rate?

Delivery rate and inbox placement are two separate numbers. Delivery rate counts the messages the receiving server accepted, so it's sent minus bounces. Inbox placement counts how many of those accepted messages landed in the inbox and not in spam. A send can show near-total delivery and still end up mostly in spam, because the spam folder counts as delivered. That's why a single "good" percentage tells you little. Look at your hard bounce count to judge list quality, and at seed tests or Google Postmaster Tools to judge placement. Our article on email deliverability rate explains how each one is measured.

How EmailFlow OS sends meeting requests as personalised video

This section covers a EmailFlow OS product, separate from the comparison above. In EmailFlow OS you record one video, for example a short spoken version of your meeting request, and upload it. You connect your own Brevo account and sending domain and import your prospect list into EmailFlow OS. EmailFlow OS then turns that one recording into a separate personalised version for each recipient, not one per company. Each version goes out from your own inbox, through your Brevo account and your domain. No shared platform sender is involved, so your SPF, DKIM and DMARC setup and your domain's reputation stay under your control. How the per-recipient version is built is described in personalised video messages per recipient, and the product itself is on the EmailFlow OS home page.

Questions people ask

? How long should a meeting request email be?

Short enough to read without scrolling: a subject line, an opening line on why this person, one sentence of purpose, a few time slots and one question. One top-ranking Google guide recommends a subject line of nine words at most, ideally three to five. If the body needs a second paragraph to explain the reason for the meeting, the reason probably isn't clear yet.

? How many time slots should I offer?

Two or three. Google's AI overview for this search also names two to three proposed slots. A single slot turns the email into a yes-or-no on the time instead of the meeting. A long list sends the recipient back to their calendar to compare. Always write the time zone next to each slot, so nobody has to convert.

? Should I send a calendar invite instead of an email?

Only once the time is agreed or the meeting is internal. A calendar invite creates an entry in the recipient's calendar straight away, with Accept, Tentative and Decline buttons. For a prospect who hasn't agreed to meet, that entry is unrequested. Ask by email first, then send the invite to confirm the slot they picked.

? How many times should I follow up on a meeting request?

Set a fixed number before you send the first email and stop on any reply, including a no. Each follow-up should be a real threaded reply to the original, which carries the In-Reply-To and References headers that keep it in one conversation, and should add one new fact or a new slot. Repeating the same ask with no new information is a reminder, not a follow-up.