How to write a meeting request email (templates to get a yes)

Why is a meeting request email so hard to get right?

On paper, asking for a meeting is the simplest email there is. You want thirty minutes of someone's time; you send a note; they say yes; the calendar invite goes out. In practice, the meeting request is one of the most quietly failed emails in any inbox. It gets ignored, it gets a "sure, send me some times" that starts a four-message ping-pong, or it gets a polite "things are busy right now" that means no. The request itself was reasonable. The way it was written is what cost you the call.

The reason is structural. When you ask for a meeting, you are asking the recipient to do three things at once: decide whether the conversation is worth their time, figure out when they are free, and write back. Most requests make all three of those steps harder than they need to be. They bury the purpose, they leave the timing wide open, and they hand the recipient a blank scheduling problem to solve on your behalf. A busy person reads that, feels the friction, and moves on to an email that asks less of them.

A meeting request email is a short, specific message whose entire job is to make saying yes the path of least resistance. It tells the reader exactly why a conversation is worth having, exactly how long it will take, and exactly when it could happen — so the only thing left for them to do is pick a slot and hit reply. That is the whole craft. Everything in this guide bends toward that single outcome: collapsing the decision down to one easy choice.

The stakes are higher than the email's length suggests. The meeting you are requesting is usually the gateway to something bigger — a deal that only closes on a call, a mentor who can change your career, a client relationship that needs a human touch, a decision your team can't make over Slack. The email is small, but it is the door. Write it like a busy person will read it in eight seconds on their phone between two other meetings, because that is exactly what happens.

This guide walks through what actually makes a meeting request get a yes, gives you a reusable structure and a step-by-step build, then hands you 14 copy-paste templates for the situations you face most: sales discovery calls, requests to a busy executive, internal team syncs, client check-ins, intro calls, product demos, one-on-ones, partnership outreach, and interview availability. You will get a subject-line table, a section on proposing times without starting an email war, the mistakes that quietly tank your reply rate, and a look at how an AI email client like AI Emaily can propose times and book the meeting for you.

What makes a meeting request email get a yes?

Every meeting request that works does the same four things, regardless of whether you are emailing a CEO or a teammate two desks over. Miss any one of them and you add friction; nail all four and you make the yes almost automatic. Before you reach for a template, internalize these — they are the reason the templates work.

1. 1

   A clear, single purpose

   The reader should know why you want to meet within the first sentence, and the meeting should have exactly one reason for existing. "I'd like to walk you through how we cut onboarding time for teams like yours" is a purpose. "I'd love to connect and explore some synergies" is noise. A vague purpose forces the recipient to guess what they are agreeing to, and people don't say yes to things they can't picture. One meeting, one job — if you have three things to discuss, say so explicitly and let them weigh the time against the agenda.

2. 2

   Specific proposed times

   Do not ask "when are you free?" — that hands the recipient a blank scheduling problem and guarantees back-and-forth. Propose two or three concrete slots with dates, times, and a time zone. Offering options shows you respect their schedule while still removing the work of generating times from scratch. Two well-chosen slots usually beat five: too many options creates decision fatigue, and a wall of times reads as if you have nothing but availability. Give them a real choice, not a calendar dump.

3. 3

   A short agenda or expected outcome

   Tell the reader what the meeting will cover and what they will walk away with. Two to four bullet points, or a single sentence describing the outcome, is enough. An agenda does three things at once: it proves the meeting has substance, it lets the recipient prepare, and it reassures them the call won't sprawl past its booked length. "We'll cover your current setup, where the gaps are, and whether this is even a fit — 20 minutes" tells a busy person everything they need to decide.

4. 4

   Easy, frictionless scheduling

   Make the reply a single action. Either propose times they can confirm with one word, or include a scheduling link so they can self-book without writing anything back. Name the meeting length up front — 15, 30, or 45 minutes — so they can assess fit instantly. If an assistant manages their calendar, copy that person. The goal is that the recipient never has to compose a sentence to say yes; they pick a slot, or click a link, and it's done.

What is the anatomy of a meeting request email?

Almost every effective meeting request is built from the same six parts, in roughly this order. You won't always use every one — an internal request can drop the introduction; a warm contact may not need the value line — but if you can fill in these blanks, you have a complete, sendable email. The templates later are just this skeleton dressed for different occasions.

1. 1

   1. A subject line that states the ask

   Your subject line should make the purpose and the request obvious before the email is even opened. "30-min call re: Q3 onboarding rollout?" works because it names the topic, the length, and the fact that you want a meeting. Keep it under about 50 characters so it doesn't truncate on mobile, and skip clickbait — straightforward, specific phrasing gets opened and respected. We cover subject lines in depth, with a copy-paste table, further down.

2. 2

   2. A brief, relevant opener

   Address the person by name and, if they don't know you, anchor the email in something real: a referral, a shared event, their recent post, or the specific problem you noticed. One sentence. With a warm contact, a quick "hope your launch went well" is enough. The opener earns you the next three lines — it is not the place to tell your whole life story or recite your company's mission.

3. 3

   3. The purpose and the value

   In one or two sentences, say why you want to meet and what's in it for them. This is where you make the case that the conversation is worth thirty minutes of a busy life. Frame it around their interest, not yours: not "I want to sell you our platform," but "I think we can cut the time your team spends on X, and I'd like fifteen minutes to show you whether that's realistic." Value first, ask second.

4. 4

   4. The proposed times

   Offer two or three specific slots with the time zone spelled out, or drop in a scheduling link. Lead with the recipient's local time when you know it. State the meeting length here if you didn't in the subject. This is the part most requests get wrong by leaving it open — be concrete, and the recipient's decision shrinks to a single pick.

5. 5

   5. A short agenda

   Two to four bullets, or one tight sentence, describing what you'll cover. This is optional for a casual fifteen-minute chat but close to mandatory for anything with a busy or senior recipient — it is what separates a request that respects their time from one that asks them to gamble it. The agenda also quietly sets the scope, which protects you both from a meeting that overruns.

6. 6

   6. A clear, low-friction close

   End with a single call to action: "Do any of these work, or is there a better time?" or "Grab whatever slot suits you here: [link]." Add a polite sign-off, your name, and a signature with your title so the reader knows who they're talking to. Don't stack three different asks — one CTA, clearly stated, then stop.

How long should a meeting request email be?

Shorter than you think. A meeting request is a transactional email, not an essay, and length is friction. Most strong requests land between 50 and 150 words. Internal notes to people who already know you can be 50 to 75 words — get to the point, propose times, done. A cold or formal external request to someone who doesn't know you may stretch toward 150 words because it has to do more work: establish who you are, why you're reaching out, and why the meeting is worth their time. Past 150 words, you are usually padding, and padding is where busy readers disengage.

The discipline is to make every line earn its place. Cut the windup. Cut the second paragraph that restates the first. Cut "I hope this email finds you well" if it isn't doing real work. A useful instinct: write the email you want to send, then delete the first sentence and the last sentence and see if it reads better — it usually does. The reader is skimming on a phone, and the faster they reach the proposed times, the faster you get your yes.

Formatting matters as much as word count. A request that is one dense paragraph forces the reader to hunt for the times and the ask; the same content with the proposed slots on their own lines, and the agenda as a short bulleted list, can be absorbed in a single glance. White space is not wasted space in a meeting request — it is what makes the email answerable in eight seconds.

14 meeting request email templates you can copy

Here are 14 templates for the meeting requests you actually send. Each one follows the structure above — purpose, proposed times, agenda, easy close — adapted to the relationship and stakes of the situation. Swap the bracketed details for your own, and always read the result once aloud before sending so it sounds like you and not like a form. Brackets like [Name], [day], and [link] are placeholders; replace every one.

A note on the proposed times throughout: pick slots that are genuinely open on your calendar, lead with the recipient's time zone when you know it, and feel free to replace the inline times with a scheduling link if you'd rather they self-book. The templates show the email-with-times approach because it works even for people who won't click a link, but a link is faster when the relationship allows it.

1. Sales discovery call request

For a cold or warm prospect where you want a first conversation to qualify fit. Lead with their problem and a credible result, keep the ask small (15–20 minutes), and make the agenda explicitly about whether it's even a fit — that lowers the pressure and raises the yes rate.

2. Request to a busy executive

When you're asking for time from a senior leader, brevity is respect. State the single decision or topic, propose one strong time plus a fallback, name a tight duration, and copy their assistant if they have one. Executives often prefer a single proposed time they can confirm or counter over a menu of options.

3. Internal team sync request

For pulling your team together on a project or decision. Internal requests can be short and direct — people already know you, so skip the windup. State the goal, list the agenda, and either propose a time or drop a poll so nobody has to negotiate.

4. Client check-in request

For a recurring or periodic review with a client. Frame it as something you do for their benefit — reviewing progress, surfacing wins, planning ahead — not as an obligation. Keep it warm and give them room to pick a window.

5. Introductory call request (warm intro)

When someone has connected you with a new contact, or you're reaching out off a mutual connection. Lead with the name that earns you trust, keep the ask light, and make it clearly low-commitment — a first conversation, not a pitch.

6. Product demo request

For when a prospect is interested enough to see the product. The agenda should make clear the demo is tailored to them, not a generic tour — that's the difference between a demo people show up for and one they cancel.

7. One-on-one (1:1) request

For requesting time with a manager, a report, or a peer for a focused conversation. Keep it human and specific about the topic so they know whether to prepare anything. A recurring 1:1 request can be even shorter.

8. Partnership / business development request

For proposing a partnership conversation with another company. Be concrete about the specific opportunity you see and why both sides benefit — "explore a partnership" is too vague to earn a meeting, but a named, mutual upside earns a look.

9. Interview availability request

For a recruiter or hiring manager coordinating an interview, or a candidate proposing times back. Clarity on format, length, and who's involved removes the usual scheduling friction. This first version is from the recruiter's side.

10. Candidate proposing interview times

The flip side — when you're the candidate and the company asked for your availability. Be flexible, be specific, and make it easy for them to lock a slot. Offering several windows signals enthusiasm and consideration.

11. Follow-up when your request got no reply

When your first request went unanswered, a short, friendly nudge after two or three business days often does the trick. Don't guilt-trip — assume the email got buried, re-state the value in one line, and make the yes even easier by narrowing to a single concrete time.

12. Networking or informational interview request

For asking someone more senior or experienced for advice over a short call. The key is to make the ask small, specific, and flattering without being fawning — and to be explicit that you're not asking them for a job, just for fifteen minutes of perspective.

13. Request to move a recurring meeting earlier

For when you need to bring an existing or expected meeting forward because something changed. Give the reason briefly, propose the new time, and make it painless to confirm. This keeps a project from stalling while you wait on a calendar.

14. Group or multi-stakeholder meeting request

For getting several people — often across teams or companies — into one room. With multiple calendars in play, a scheduling poll or link almost always beats proposing fixed times, because the odds of one slot working for everyone drop fast as you add people.

What makes a good meeting request subject line?

The subject line decides whether your carefully written request gets opened or buried. For a meeting request, the job is simple: signal the topic and the ask clearly enough that the reader knows what they're agreeing to before they open it. Straightforward, specific phrasing — often with the meeting length or a topic baked in — gets opened and respected far more than clever or vague lines. Keep it under about 50 characters so it survives truncation on a phone, and resist the urge to bait; a meeting request is not the place for mystery.

A few patterns reliably work: naming the duration ("15 min on…"), referencing a mutual contact, posing the request as a light question, or stating the specific topic and outcome. Match the formality to the recipient — "Leadership meeting request: [topic] — 20 min" for a senior external contact, "coffee next week?" for a friendly peer. The table below pairs common situations with subject lines you can adapt.

How do you propose times without starting an email war?

Proposing times is where most meeting requests either land cleanly or spiral into a six-message thread. The principle is simple: do as much of the scheduling work as you can, so the recipient does as little as possible. That means offering specific slots rather than asking "when works for you?", being explicit about time zones, and naming the meeting length so people can assess fit instantly. Time-zone confusion is one of the most common causes of missed and rescheduled meetings — nearly a third of meetings now span time zones — so never assume the recipient knows your local time.

Lead with the recipient's time zone, not yours. "Tuesday at 11:00 a.m. your time" or "2:00 p.m. ET / 7:00 p.m. GMT" removes the mental math and the risk of someone showing up an hour off. State the duration up front — 15, 30, or 45 minutes — because a clear time commitment cuts hesitation and the follow-up questions that come with an open-ended ask. And when you offer slots, two or three is the sweet spot: enough to give a real choice, few enough to avoid decision fatigue and the impression that your calendar is wide open.

For anything with more than two people, or when you're scheduling across organizations, a scheduling link or poll beats manual proposals. A link lets the recipient self-book in one click without composing a reply, which is the lowest-friction path of all. Two cautions: don't open a cold email with a bare scheduling link before you've established any value — it reads as presumptuous — and if an assistant manages a key contact's calendar, copy them or send the scheduling email their way. Use links to remove work, not to push your scheduling burden onto someone who hasn't agreed to meet yet.

• Offer two to three specific slots — not one (too rigid) and not five (decision fatigue).
• Always spell out the time zone, and lead with the recipient's local time when you know it.
• Name the meeting length — 15, 30, or 45 minutes — so they can judge fit at a glance.
• Use a scheduling link or poll for group meetings and cross-company scheduling.
• Don't drop a bare scheduling link in a cold email before you've earned the meeting.
• Copy the executive assistant if one manages the recipient's calendar.
• Give a couple of business days for a reply before a single, friendly follow-up.

What are the most common meeting request email mistakes?

Most failed meeting requests fail for the same handful of reasons. None of them are about effort — they're about friction and clarity. Here are the ones that quietly cost you the most calls, and what to do instead.

• Leaving the time open. "Let me know when you're free" hands the recipient a blank scheduling problem and guarantees back-and-forth. Propose specific slots.
• A vague purpose. "I'd love to connect" or "explore synergies" gives the reader nothing to say yes to. Name the single reason for the meeting in the first sentence.
• No agenda for a serious ask. Asking a busy or senior person for time without telling them what you'll cover reads as asking them to gamble their schedule. Add two to four bullets.
• Omitting the meeting length. People can't assess fit without it. State 15, 30, or 45 minutes so the time commitment is clear.
• Forgetting the time zone. The most common cause of a missed call. Spell it out and lead with the recipient's local time.
• Burying the ask. If the proposed times and the call to action are hidden in paragraph three, the skimmer never finds them. Put them on their own lines.
• Wrong register. Too formal with a peer feels cold; too casual with an executive feels presumptuous. Match the tone to the relationship.
• Too long. Past ~150 words you're padding, and busy readers disengage. Cut the windup and the restatement.
• Multiple competing asks. Three different questions in one email means none get answered cleanly. One meeting, one CTA.
• Dropping a cold scheduling link first thing. A bare link before you've established value reads as entitled. Earn the meeting, then make booking easy.
• Following up too soon — or too aggressively. Give it a couple of business days, send one gentle nudge, and don't guilt-trip.
• No signature or context. If a stranger can't tell who you are and why you matter, they won't reply. Include your name, title, and company.

Can an AI email client write and schedule meeting requests for you?

Most of the work in a meeting request isn't the writing — it's the coordination around it. You have to find times that are actually open on your calendar, translate them into the recipient's time zone, phrase the request so it gets a yes, and then chase the reply and send the invite. That's a surprising amount of overhead for a thirty-minute call, and it's exactly the kind of repetitive, rules-based work that an AI email client can take off your plate.

AI Emaily is an AI-native email client built around an assistant that lives in your inbox and acts on your behalf. Ask it to request a meeting and its scheduling agent reads your calendar, proposes times that are genuinely free, writes the request in your voice — purpose, slots, agenda, the works — and, when the recipient replies, can book the meeting and send the invite without you touching it. Because it learns how you actually write, the request sounds like you, not like a template; it handles the time-zone math so you don't show up an hour off; and it can nudge a non-reply at the right interval instead of letting the thread go cold.

It works the way you want it to. AI Emaily runs in three modes: Manual, where it just drafts and you send everything yourself; Copilot, where it proposes the request and the times and waits for your approval before anything goes out; and Autopilot, where you let it handle defined routines — like booking a slot once someone replies "any of those work" — on its own, always with undo and a full audit trail so nothing leaves your outbox that you didn't sanction. It connects to every major email provider, so you're not switching accounts to get the help. There's a Free plan at $0 to try it, and Pro runs $17.99/month billed annually for the full set of agentic features, including the scheduling agent.

Putting it all together

A meeting request email gets a yes when it does four things and gets out of the way: it states one clear purpose, proposes two or three specific times in the recipient's time zone, attaches a short agenda so the meeting has obvious substance, and makes saying yes a single reply or click. Everything in this guide — the structure, the 14 templates, the subject-line table, the scheduling tips — is just a way of reducing the recipient's decision down to one easy choice. The shorter and more concrete you make that choice, the more often you'll hear back.

Start from the template closest to your situation, fill in the brackets, and read it once aloud to make sure it sounds like you. Lead with value, name the length, spell out the time zone, and keep the whole thing under 150 words. Then send it and give it a couple of business days before a single, friendly nudge. Do that consistently and you'll book more of the conversations that actually move your work — and your relationships — forward.

And when the coordination overhead starts to add up — the calendar-checking, the time-zone math, the chasing — that's the moment to let an AI email client like AI Emaily propose the times and book the call for you, so you can spend your energy in the meeting instead of on arranging it.