A meeting request email asks for a specific slot of someone's calendar and succeeds in proportion to how little work the reader has to do to say yes: two concrete times in their timezone, a stated length, a stated purpose, and a lighter fallback such as a one-page note. It is used at any stage of a cold or warm thread when the next step is a conversation. Teams report that two offered times book 1.5 to 2 times more meetings than "do you have time next week", and that the fallback captures replies the meeting ask alone would lose.
"Do you have 30 minutes sometime next week?" asks the reader to open their calendar, find a slot, consider whether the meeting is worth it, and write back with options. Four tasks, and the email gets deferred. Two concrete times reduce it to one task: pick one, or say neither.
The length and the purpose matter as much as the times. "20 minutes to see whether {problem} applies at {company}" tells the reader what they will get and what it costs. A meeting with no stated outcome is a meeting people decline.
The fallback is for the reader who is interested but cannot meet. A one-page note, a two-line summary, a recorded walkthrough. It keeps the reply coming and often turns into the meeting a week later.
Subject: {purpose_short}: {time_one} or {time_two}?
Hi {first_name},
To see whether {problem} applies at {company}, 20 minutes is enough. Two options in {their_timezone}:
{time_one}
{time_two}
If neither works, send one that does. If a call is more than this deserves, reply "note" and I will send a one-page version instead.
{sender_name}
{sender_title}, {sender_company}
If this is not relevant, reply "no" and I will not write again.
{time_one} / {time_two} Day and time, in the reader's timezone, at least a day apart{purpose_short} The purpose in four wordsSubject: 20 minutes on {topic}
{first_name},
Two slots that are open on my side: {time_one} and {time_two} ({their_timezone}). If neither fits, this link shows the rest: {scheduling_link}.
The purpose is {purpose_one_line}; the outcome is a yes or no on whether it is worth a longer conversation.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{scheduling_link} The only link; offered after the two times, not instead of themSubject: {topic}: you and {colleague_name}?
Hi {first_name},
Thanks for the reply. Since {colleague_name} owns {adjacent_area}, it may save a second meeting to have them in the first one.
Two times that could work for both, {their_timezone}: {time_one} or {time_two}. Thirty minutes, and I will send a one-paragraph agenda the day before so nobody arrives cold.
If it is easier to meet one at a time, say so.
{sender_name}
If this is not relevant, reply "no" and I will not write again.
{adjacent_area} What the colleague owns that touches the decision{colleague_name} Named only if the prospect mentioned them or they are publicTwo times on the same afternoon is one option. Offer different days, and state the timezone.
A bare link makes the reader do the work the email was meant to remove. Two times first; the link is the third option.
Twenty or thirty minutes, and what the reader gets at the end. A meeting with no stated outcome is declined.
A meeting request that bounces is a thread that dies. In cold threads the list was verified before the opener; in warm threads, one check through the free verifier before the first send.
| Metric | Healthy range (industry) | If missed |
|---|---|---|
| Reply rate to the meeting ask | 10 to 20% in a warm thread; 3 to 6% cold | Purpose or length missing |
| Booking rate from replies | 50 to 70% | The two times were too close together or in the wrong timezone |
| Fallback requests | 3 to 8% of recipients | Fallback missing; add the note option |
| No-shows | Under 15% | Send the one-paragraph agenda the day before |
| Lift from two times versus open-ended | 1.5 to 2x bookings | Measure it once on 200 sends; it is the cheapest test in outreach |
Subject: List quality at Northgate: Tuesday 10:30 or Thursday 14:00?
Hi Priya,
To see whether export verification applies at Northgate, 20 minutes is enough. Two options in London time:
Tuesday 14 October, 10:30
Thursday 16 October, 14:00
If neither works, send one that does. If a call is more than this deserves, reply "note" and I will send a one-page version instead.
{your_name}
{your_company}
If this is not relevant, reply "no" and I will not write again.
Four tasks for the reader. Two concrete times is one.
It hands back the work. Times first, link third.
That is one option. Different days, stated timezone.
A meeting with no stated outcome is declined.
The same structure, two times and a fallback, changes length and purpose depending on where the thread is.
| Stage | Length to request | Purpose line | Fallback |
|---|---|---|---|
| Cold opener | 15 to 20 minutes | "To see whether {problem} applies at {company}" | One-page note |
| After a positive reply | 20 to 30 minutes | "To walk through how {outcome} would work for {company}" | Recorded walkthrough |
| After an introduction | 20 minutes | "To hear what {introducer} thought we had in common" | Two-line summary |
| Bringing a second stakeholder | 30 minutes | "So {colleague} does not need a separate meeting" | One at a time instead |
| After a no-show | 15 minutes | "Shorter this time; same two options" | The note, and no third attempt |
The full set
When the meeting ask gets no reply
The meeting ask after an introduction
Where meeting asks fit in sequence performance
Booking and show rates as sequence metrics
The openers that lead to the ask
State the purpose and the length, offer two concrete times a day apart in the reader's timezone, and give a lighter fallback such as a one-page note. The reader's only task is to pick one, name another, or ask for the note.
After the two times, as a third option, not instead of them. A bare link hands the reader the work the email was meant to remove. Teams that test it find two offered times book 1.5 to 2 times more meetings than a link alone.
Twenty minutes for a cold thread, thirty when a second stakeholder joins. State it in the email with the outcome: a yes or no on whether a longer conversation is worth it. Short, defined meetings get accepted; open-ended ones get declined.
Reply the same day with two new times and the fallback. Interested-but-busy replies often need the note first; send it and propose the meeting again a week later with reference to something in it.
A one-paragraph agenda the day before, the calendar invite sent within an hour of the booking, and a meeting short enough not to be the first thing cut. Teams that do all three hold no-shows under 15%.
A meeting request that bounces ends the thread. Verify the list before the opener, or one address before a warm send. 100 free checks a month, unknowns refunded.
Ayoub built BounceZero's 5-stage validation pipeline, its dedicated BGP-announced IP infrastructure, and the Patroni HA PostgreSQL cluster behind every verification. Previously built high-volume email delivery infrastructure. Trained at 1337 Benguerir (École 42 network, 2019). Open-source: bgp_analyzer.
Templates by trigger and stage, each with the deliverability rules that apply
Four sales prospecting email templates, one per prospecting method
A warm introduction email template for the two warm moments in outreach
Twenty-four cold outreach email templates organised by trigger (funding, hiring, new role, tech change),...
A funding round cold email template with two variants and merge fields
A hiring trigger cold email template that uses open roles as the signal
A new role cold email template for job-change triggers
Continue through related topics