Requesting a meeting email: templates that get a yes

A meeting request email gets a yes for three reasons, and none of them is luck. You give the reader a concrete reason the meeting matters to them, you propose specific times so saying yes is one click, and you keep the whole thing short enough to read on a phone. Most people get this backwards. They write a long, polite email that explains who they are, asks for "some time to connect," and leaves the reader to do the scheduling work. That email gets ignored, not because the request was unreasonable, but because it made replying feel like a chore.

This guide gives you the structure that works, the small amount of real data behind it, and copy-paste templates for the situations you actually face: a cold request to someone new, a warm request to someone you know, an internal meeting with a colleague, a follow-up after no reply, and a quick reschedule. The goal is not a clever email. The goal is a reply.

What a meeting request email actually has to do

A meeting request email has exactly one job: make it easy to say yes. Everything else is in service of that. The reader is skimming, probably on a phone, probably between two other things. If your email makes them stop and think "what does this person want, and when," you have already lost. If it tells them the point in the first line and offers two times to pick from, you have made the decision small.

That framing changes what goes in the email. You are not writing a pitch. You are not writing your life story. You are writing a request that the reader can grant in a few seconds. So the email needs a clear reason (why this meeting helps them), a specific ask (a short call, not "some time"), proposed times (so they pick, not propose), and an easy out (so a no is also easy). That is it.

The evidence: what actually moves replies

You will find a lot of confident advice about the perfect send time and the magic subject line. Most of it traces to vendor marketing, not measured data. The closest thing to a real first-party study is Boomerang's analysis of more than 40 million emails, and its findings are specific and a little humbling.

Three things are worth building your habit around:

• Length. Emails between 50 and 125 words got response rates above 50%. Around 500 words, that dropped to roughly 44%. A meeting request has no reason to be long, so this one is free.
• Subject lines. Subject lines of 3 to 4 words got the most responses, and as the subject grew longer, response rate fell. Sending with no subject line at all landed around 14%. "Quick call this week?" beats "Requesting a meeting to discuss our potential partnership opportunities."
• Questions. Emails that asked 1 to 3 questions were 50% more likely to get a reply than emails asking none. A meeting request that ends in a question ("Does Tuesday at 2pm or Wednesday at 10am work?") gives the reader something concrete to react to.

Notice what is not on this list: the magic send minute. Treat send timing as a tiebreaker once your content is right, not as the lever.

The five parts of a request that gets a yes

Every effective meeting request email has the same five parts, in roughly this order. You can compress them, but you should not skip any.

The piece people botch most is the reason. They write what they want from the meeting ("I'd love to pick your brain," "I want to learn more about your needs") instead of what the reader gets. Flip it. Before you send, read your email and ask: if I were the busy person on the other end, why would I give up 15 minutes of my day for this? If the answer is not in the email, the meeting will not happen.

Copy-paste templates

Use these as starting points, not as scripts to send verbatim. The bracketed parts are placeholders you fill in. The whole point is specificity, so a template you do not personalize will not work.

Cold request to someone you do not know

Subject: Quick call this week?

Hi [Name],

I'm [Your name] at [Company]. I saw [specific thing: their post,
their hiring page, a mutual contact's intro].

We help [their kind of company] [specific outcome], usually
[concrete result, e.g. "cutting reporting time from days to hours"].
I'd like 15 minutes to show you whether it'd work for [their team].

Do you have time Tuesday at 2pm ET or Wednesday at 10am?
If neither fits, just send a time that does.

Thanks,
[Your name]

Warm request to someone you already know

Subject: 20 min on [topic]?

Hi [Name],

Good to be back in touch. I'm working on [project] and I think
[their experience / their team] could really help shape it.

Could I grab 20 minutes to walk you through where it stands and
get your read? Thursday at 11am or Friday at 3pm both work for me,
or tell me what's easier.

Appreciate it,
[Your name]

Internal request to a colleague

Subject: 15 min on the launch plan

Hi [Name],

Before we lock the launch date, I want to align on [specific
decision: scope, owner, timeline]. Should be quick.

I'm free Wednesday 9-10am or Thursday after 2pm. I'll send an
invite once you pick. Agenda: [item 1], [item 2].

Thanks,
[Your name]

Follow-up after no reply

Do not just bump the thread with "checking in." Add something and re-offer times.

Subject: Re: Quick call this week?

Hi [Name],

Following up in case my note got buried. Since I last wrote,
[new, relevant detail: a case study, a new feature, a change on
their end].

Still happy to keep it to 15 minutes. Does Monday at 1pm or
Tuesday at 4pm work? And if this isn't a priority right now,
just say so and I'll stop nudging.

Thanks,
[Your name]

Reschedule

Subject: Re: [original meeting]

Hi [Name],

Something came up and I need to move our [day/time] meeting.
Apologies for the short notice. Would [new option 1] or
[new option 2] work instead? Same agenda, same 30 minutes.

Thanks for being flexible,
[Your name]

If you want a deeper treatment of the after-no-reply case specifically, the follow-up email guide and our sales follow-up templates go further on cadence and chasing non-responders.

A few rules that quietly raise your reply rate

These are small, and they compound.

• Propose times in the reader's time zone, with the zone stated. "2pm ET" removes a round trip. Never make the reader convert.
• Offer two or three options, not your whole calendar. A wall of times is its own kind of work. Two or three says "I've thought about this; just pick."
• Write at a plain reading level. The Boomerang data found third-grade-level emails got a 36% lift in responses over college-level writing. Short words, short sentences. This is respect for a skimming reader, not dumbing down.
• End on the question. The last line should be the thing you want them to answer. Do not bury the ask above a paragraph of sign-off.
• Match the channel to the relationship. A cold prospect gets email. A close colleague might get a Slack message and a calendar hold. Do not send a formal request email to someone who sits ten feet away.

Where the meeting record comes in

The request email is the start of the loop, not the end. Once the meeting happens, the follow-up you send afterward is often what actually moves the deal or the project. And the strongest follow-ups are grounded in what was actually said, not in your half-remembered notes. That is the link between a good request and a good outcome: book the meeting cleanly, then capture it accurately so your recap and next ask write themselves.

That is where having an honest record of the conversation helps. If your meetings are on Google Meet, Scribbl records, transcribes, and summarizes them from your browser with no bot joining the call, so the next email you send after the meeting can quote the real commitments instead of "as discussed." It is free for individuals, and the desktop app adds Zoom and Microsoft Teams if your calls span tools. For sales teams especially, that accurate record is what turns a meeting into a follow-up that books the next one.

But be honest about scope: you do not need any tool to write a good request email. The structure above and 60 seconds of personalization will do more for your reply rate than any software. The tool earns its place after the meeting, not before.

Frequently asked questions

How long should a meeting request email be?

Short. The largest first-party study (Boomerang, 40M+ emails) found response rates stayed above 50% for emails between 50 and 125 words, then declined as length grew. A meeting request has no reason to run long: a line of context, a reason, an ask with times, and an easy out. If it does not fit on one phone screen, cut it.

What should the subject line be?

Three to four plain words that state the ask, not the topic. "Quick call this week?" or "15 min on the Q3 plan?" beat long, formal subjects, and they crush no subject line at all (which landed around 14% in the same study). Skip your company name and skip jargon; the subject's only job is to get the email opened.

Should I include proposed times or ask for their availability?

Include specific times. Asking "when are you free?" pushes the scheduling work onto the reader and adds a round trip. Offer two or three concrete options in the reader's time zone and let them pick. If none fit, your easy-out line ("or send a time that works") covers it. This is the single change that most often turns a no-reply into a yes.

How many times should I follow up if I get no response?

One well-aimed follow-up that adds something new is worth more than three "just checking in" nudges. Re-offer times and give the reader a painless out. If you are still silent after two follow-ups spaced several days apart, move on or change the channel. For a full cadence, see the follow-up email guide.

Is it better to email or use a scheduling link?

A scheduling link is great once someone has agreed to meet; it removes the back-and-forth. But leading a cold or first-touch request with only a link can read as "do my work for you," especially with someone senior. Propose two or three times in the body and offer the link as a fallback ("or grab any slot here"). With warm contacts and people who already know you, a link up front is usually fine.