How to Write a Meeting Request Email (With Templates)

What a meeting request has to do

A meeting request asks someone for something scarce: half an hour of their attention. It works when the reader can answer three questions within a few seconds. Why me? Why now? What do I get from it?

Most requests fail one of those. They describe the sender's company at length, ask for "a quick call" with no stated purpose, or leave the reader to suggest a time. Each makes saying yes slightly harder, and slightly harder is usually enough for an email to sit unanswered until it is forgotten.

This guide covers everyday B2B meeting requests to prospects, customers, and partners. If you are booking meetings at a conference or trade show, our pre-event outreach guide covers the timing and templates specific to events.

The first line decides it

The inbox preview shows the subject and the first sentence or so. For most readers, that is the whole pitch.

• Make the subject specific. "Question about your Q1 rollout" or "Introduction from [mutual contact]" beats "Quick call?" or "Meeting request". A subject that names something only this person would recognise gets opened.
• Start with them, not you. The first sentence should be about their situation: something they said, published, or asked about. "I read your post about consolidating your event tools" is a reason to keep reading. "I'm an account executive at…" is not.
• Say what the meeting is for in the first two sentences. Name a specific topic and a specific benefit: "a 20-minute look at how other events teams handle late changes to expert schedules", not "a chat about how we can help".

Make the meeting easy to accept

• State the length. Twenty or thirty minutes is easier to agree to than an open-ended call. Our guide to how long a meeting should be explains why shorter defaults usually work.
• Propose two specific times, or offer a link. Two concrete options let someone reply with one word. A booking link suits people who asked you for time; for a first approach to someone senior, proposing times usually reads as more courteous. See when to send a booking link and when to propose times.
• Show the time zone. "Tuesday at 10:00 a.m. Eastern (3:00 p.m. London)" avoids a reply asking which ten o'clock you mean. The time zone converter helps, and so does our guide to scheduling across time zones.
• Say who will attend from your side. If you are bringing a specialist, name them and say why they are useful to this reader.
• Make it easy to say no. A line such as "If this isn't a priority right now, just say so and I won't chase" lowers the pressure, and often gets a more honest reply.

Template: a prospect you have not met

Subject: [Their initiative or something specific to them] — 20 minutes?

Hi [First name],

[One sentence about something specific to them: a post, an announcement, or a problem their role usually owns.]

We work with [type of team] on [specific problem]. I think a 20-minute conversation about [specific topic] would be useful to you even if we never work together. I would bring [what they get: an approach, a comparison, a checklist].

Would [day, time, time zone] or [day, time, time zone] work? If neither does, I'm happy to fit around you.

If this isn't a priority right now, just say so and I won't follow up.

[Name]

Template: an existing customer

Customers already know you, so the email can be shorter. Lead with their goal and say what the meeting will produce.

Subject: [Topic] — 30 minutes before [their deadline or milestone]?

Hi [First name],

Ahead of [their milestone], I'd like to [specific purpose: review how the rollout is going, agree the plan for next quarter, look at the issue your team raised].

I'll bring [what you will prepare]. It would help to have [who from their side] there too.

Would [day, time] or [day, time] suit? I'll send an agenda once we have a time.

[Name]

Asking for the right people from their side is part of getting more stakeholders into the conversation, which keeps a relationship from depending on a single contact.

Template: a partner or peer

Subject: [Shared customer, market, or event] — compare notes?

Hi [First name],

[How you know of them, or who introduced you.] We both work with [shared customer type], and I think there's a useful conversation to have about [specific overlap].

Would you be open to 30 minutes on [day] or [day]? I'm happy to come to you or do it by video.

[Name]

Following up without nagging

Silence usually means busy, not no. One or two follow-ups are reasonable; more rarely help and can damage the relationship.

• Wait about a week, then reply in the same thread so the context is visible.
• Add something new: a relevant article, an answer to a question their team has asked publicly, or a different time.
• Close the loop. A final note saying you will stop following up is honest, and it occasionally prompts a reply.

If they agree but later need to move the meeting, make that easy too. See how to reschedule a meeting politely. And when someone asks you for a meeting, answer quickly: speed matters most with inbound requests.

A quick checklist before you send

• The subject names something specific to the reader.
• The first sentence is about them.
• The purpose and the benefit are clear within two sentences.
• The length is stated.
• Two specific times are proposed with the time zone, or a link is offered.
• Anyone joining from your side is named.
• There is an easy way to say no.
• It fits on a phone screen without scrolling.

CallShark is being built to take the back-and-forth out of booking B2B meetings, with the context of each request attached to the booking. The product is temporarily down.