Meeting request email templates for sales that get a yes

You’re asking a stranger for thirty minutes of their time. They’ve never heard of you, they get dozens of these a week, and most of them read like a template with the names swapped in. So why would they say yes to yours?

A meeting request email earns that yes. It doesn’t ask for attention, it proves why the attention is worth giving. That means answering why you, why them, why now, in about six lines, before the reader even thinks about scrolling.

In this guide, I’ll show you the exact structure that makes a meeting request easy to say yes to, plus a template for every situation you’ll run into: cold outreach, LinkedIn connections, referrals, event follow-ups, and the awkward re-request after silence. I’ll also cover when to propose time slots versus a booking link, and how to follow up without sounding needy.

Get the structure right, and the rest of your outbound motion (targeting, personalization, sequencing) actually pays off.

What a sales meeting request email needs to do

A sales meeting request email is a short message asking a prospect or contact to get on a call. Its job is to answer three questions fast: why you (credibility), why them (relevance), and why now (timing).

Most meeting requests fail on the second question. They explain what the sender does, pitch a product, then ask for thirty minutes. The prospect has no reason to care. A good meeting request flips that order. It leads with something specific to the reader, connects it to a problem worth solving, and makes the next step small enough to say yes to.

If you’re building your first cold emailing motion, the meeting request is where all the upstream work (targeting, enrichment, personalization) either pays off or doesn’t.

The structure of a meeting request email

Every meeting request email has six parts. Each one earns you the next line of attention.

• •

  Subject line. Short, specific, tied to the reason you’re reaching out. More on this below.

• •

  Opening line about them. One sentence that proves you did your homework. A trigger event, a recent post, a company move.

• •

  Reason for the meeting. What you want to discuss and why it matters to their business. One sentence.

• •

  What they get. The outcome of the conversation for them, not for you. A benchmark, a framework, a second opinion on something they’re already working on.

• •

  The ask. A question, two time slots, or a booking link depending on warmth. Keep it to one line.

• •

  Sign-off. Clean close, no filler. If you want to sharpen this part, here’s a guide on how to end an email that converts.

That’s it. Six lines, maybe seven. If any part runs longer than two sentences, cut it.

Subject lines

Your subject line decides whether the email gets opened or archived. The best ones are short, specific to the recipient, and connected to the reason you’re writing.

Here are five patterns that work:

• •

  A question tied to their role: “How does {{company}} handle {{process}}?”

• •

  A mutual contact: “{{referrer name}} suggested we connect”

• •

  A trigger event: “Congrats on the Series B”

• •

  An outcome: “Cut {{painPoint}} by half”

• •

  A meeting purpose: “Quick call on {{topic}}?”

Avoid vague lines like “Meeting request” or “Quick question.” They give the reader nothing to work with. For a deeper breakdown of what gets opened, check out this guide on cold email subject lines.

The ask

The ask is where most reps either push too hard or stay too vague. There are three versions, and each fits a different moment.

In a cold email, a question lowers the commitment. Two time slots work when there’s some warmth because they remove the back-and-forth. A booking link is best once someone has already said yes in principle.

Meeting request email templates by situation

Below are seven templates built for specific outbound situations. Each one follows a different structure because the relationship, the goal, and the reader’s mindset are different.

1. Cold first touch

Saw that {{company}} just {{trigger event}}.

Most teams in {{industry}} hit {{pain point}} when they’re scaling that fast. We helped {{similar company}} solve it in {{timeframe}}.

Worth a quick conversation?

2. After a LinkedIn accept

Thanks for connecting, {{firstName}}.

I noticed you’re leading {{initiative / role focus}} at {{company}}. We’ve been working with similar teams on {{relevant topic}} and I think there’s an overlap.

Would Tuesday at 10 am or Thursday at 2 pm {{timezone}} work for a 15-minute call?

3. Referral

{{Referrer name}} suggested I reach out.

They mentioned you’re working on {{challenge}}, and that’s exactly where we’ve been helping teams like {{similar company}}.

Open to a short call this week?

4. Event or webinar follow-up

Good to connect at {{event name}}.

The session on {{topic}} stuck with me, especially the point about {{takeaway}}. We’ve been seeing the same pattern with our customers.

Would a 15-minute call make sense to compare notes?

5. Executive ask

{{firstName}}, {{company}} is growing fast in {{area}}. Teams at that stage usually run into {{outcome-level problem}}.

Would Tuesday at 9 am or Wednesday at 3 pm {{timezone}} work for 15 minutes?

6. After a positive reply

Great, looking forward to it.

Here’s a link to grab a time: {{lemcal link}}

I’ll plan to cover {{agenda item 1}} and {{agenda item 2}} so we make the most of the 15 minutes.

7. Re-request after no reply

{{firstName}}, different angle.

I put together a short breakdown of how {{similar company}} handled {{specific challenge}}. Happy to share it on a 10-minute call, or I can just send it over.

Which works better?

Notice the pattern: the colder the contact, the softer the ask. The warmer the relationship, the more specific and direct you can be.

Should you propose times or send a booking link

A booking link in a cold first touch feels like a demand. You’re asking a stranger to do admin work for you before they’ve decided the conversation is worth having. It also adds a URL to your email, which can hurt deliverability.

Once someone has replied with interest, the calculus flips. Now the link removes friction. They pick a time, it lands on both calendars, done.

The rule is simple: use an interest question or two time slots for cold outreach. Switch to a booking link once the prospect has shown they want to talk.

Follow up on a meeting request with no reply

Most meeting requests don’t get a reply on the first send. That’s normal. The average email reply rate is 2.72%, with a median campaign sitting at 1.13% (lemlist internal data). One email is rarely enough.

A good follow-up plan has three qualities: each touch adds a new angle, the ask stays small, and you mix channels.

Here’s a simple structure:

• •

  Day 3. Follow-up email with a new angle (a relevant stat, a case study, a different pain point).

• •

  Day 5. LinkedIn profile visit or connection request with a short note.

• •

  Day 8. Second follow-up email, shorter, with a smaller ask (send a resource vs. book a call).

• •

  Day 12. LinkedIn message referencing the email.

Adding LinkedIn to an email sequence makes a measurable difference. It multiplies replies by 2.6x in France, 3x in the rest of the world, and 3.9x in the US (lemlist internal data). If you’re only emailing, you’re leaving replies on the table.

For ready-to-use sequences, check out these follow-up email templates. And if you want to go deeper on combining channels, here’s a guide on LinkedIn and email outreach.

Mistakes that kill meeting requests

Six things that consistently tank reply rates:

• •

  Asking for thirty minutes from someone who doesn’t know you. Start with fifteen, or better, just ask if they’re open to a conversation.

• •

  No reason for them. If the email is all about your product and your company, the reader has no incentive to reply.

• •

  A vague subject line like “Quick question” or “Touching base.” It tells the reader nothing.

• •

  A booking link as the only content. No context, no reason, just a calendar URL. That’s an email with no value.

• •

  An apologetic tone. “Sorry to bother you” and “I know you’re busy” signal low confidence. State your reason and ask.

• •

  Long paragraphs. If the reader has to scroll on mobile to find the ask, they won’t.

Every one of these mistakes has the same root cause: the email is written for the sender, not the reader.

How to send meeting request emails in lemlist

Here’s how to put this into practice inside lemlist.

Build your meeting request and follow-ups as a single multichannel sequence. Add email steps for the initial ask and follow-ups, then layer in LinkedIn steps (profile visit, connection request, message) between them. The sequence runs automatically and stops when the prospect replies.

For emails sent after a positive reply, add a lemcal booking link. You can set up different meeting types in lemcal for different use cases (intro call, demo, strategy session) so the prospect picks the right one.

Use the timezone-based sending schedule to land emails during local working hours. A meeting request that arrives at 7 am in their timezone gets read. One that arrives at midnight gets buried.

A/B test the ask itself. Create two versions of your meeting request step: one with an interest question, one with two time slots. Let reply rate decide the winner. Most teams test subject lines and ignore the ask, which is the part that actually drives the reply.

If you want to go deeper on the full workflow, here’s a guide on how to book more meetings with a structured outbound process.

Final takeaway

A meeting request email works when it gives the reader a reason to say yes. Lead with relevance, match the ask to the relationship, and follow up across channels with a new angle each time.

The templates above cover the situations you’ll hit most often. Pick the one that fits, adapt it to your prospect, and test the ask.

Build your first signal-based sequence in lemlist.