How to Write a Meeting Request Email That Earns a Reply

A meeting request email is far more likely to get a reply when it gives the recipient a reason they recognize and one low-effort way to say yes. The ones that get ignored do the opposite. They open with the sender, claim a result the reader has no way to check, and leave the time wide open with “when are you free?”

Most advice, and most AI drafts, will hand you a template and tell you to “state your value.” That is where meeting requests go wrong, because stating your value usually turns into claiming an outcome you have not earned yet. The guide below covers the short method that earns the meeting, seven templates matched to who you are writing to, how to propose a time, and how to follow up without nagging. The templates are grouped by situation further down, if you want to jump straight to yours.

What makes a meeting request get a reply

Three things carry a meeting request:

• A reason the recipient recognizes as theirs. A referral, a trigger (something that just changed on their side), or something you can see about them that they can confirm. Without one, the email is just a request for time from a stranger, and time is the one thing busy people guard.
• One clear ask. The meeting itself, and nothing else. One email that asks for a call, a document, and a referral stacks three decisions, and the added friction makes it likelier that none of them happen.
• A simple way to pick a time. A ready-to-pick time removes a step between interest and a booked slot. Offer two or three set times, or a booking link, so the reader can act the moment they read the email.

Get those right and most of the rest is packaging. Keep the whole thing short enough to read on a phone, and put the reason near the top, above any line about who you are.

Give a reason the reader can check

A reliable way to get ignored is to claim the result before you have earned it. “A quick call to show how we will boost your pipeline by 30%” is a number the reader cannot check, so they discount the whole email. The emails that work say what you can see or point to, and let the meeting be where you make the case.

Compare the two openers:

The first claims an outcome and gives the reader nothing to verify. The second leads with something they can confirm in one glance (they are hiring), then offers the connection as a conditional the reader can accept or wave off, rather than stating their situation as fact. The observation does the work; the read stays a read.

We use the same approach in our own outbound at Alore: lead with something the reader can check and let the meeting carry the pitch. One recruitment campaign opened with the arithmetic of agency fees rather than a pitch. Hire five engineers, apply a one-month-salary fee to each hire (around 8.33% of annual salary), and you get a specific number on the page; a flat fee changes that number without changing the roles you need to fill. The email then asked, “would it be useful to run the math against your current mandates?” The reader can redo that sum in their head, so the request for a conversation rides on a reason they can check.

Keep the line between what you observed and what you are guessing. The observation is theirs to confirm; your read of it is yours to offer, and you hold it as a read rather than state it as fact.

The right request by situation

Who you are writing to changes what earns the meeting, so match the opener to the relationship first, then to the scenario. A cold prospect needs a reason and a low-pressure out. A referral needs the referrer’s name in the first line. An internal ask needs the shared goal rather than a pitch. The seven templates below are written to be sent with only the bracketed parts changed. Fill the brackets with something real about the recipient, because that is where the reply comes from.

Cold prospect (you have never spoken)

Filled in with real details, that cold template reads like this:

Close every template the same way: a quick thanks, your name, and a one-line role and company, so the recipient knows who is asking.

Warm lead (they engaged before)

Referral (a mutual contact pointed you there)

Internal or your manager

For an internal request, lead with the decision you need, not just the topic you want to discuss. That tells the reader what the meeting is for and what they are being asked to resolve.

Existing client

Networking or informational

Interview request (you are the candidate)

The template above is for asking to be interviewed after you have applied. Two related situations use a different template: if you are nudging after an interview that already happened, the follow-up section below fits better, and if you are asking a practitioner for a learning conversation rather than a job, use the networking template above.

How to propose a time

Give the reader a low-effort way to say yes: two or three exact slots, or a booking link, and always your timezone. “When are you free?” hands the work back to them, so the thread stalls while they think about it later and forget.

Which option fits depends on the situation:

• Two or three set times work best when you have no scheduler, or the recipient is senior or formal, where a booking link can read as presumptuous. Offer real slots a few days out, not “anytime.”
• A booking link works well for volume, for peers, and when you want one tap to settle it. It lets them book the moment they read your email, including the evenings when people catch up on their calendars. With a senior or formal recipient, weigh it against set times, since a link can read as putting your calendar ahead of theirs.
• “Reply with a time that suits you” is fine only when the relationship is warm and you trust they will reply.

Always name your timezone, and for an international recipient offer a time in theirs or name two zones. A missed timezone is one of the quieter reasons a confirmed meeting falls apart.

Subject lines for meeting requests

A meeting-request subject line should name the reason or the ask in a few words: the referral, the trigger, or the decision on the table. It is one of the few things the recipient weighs before opening, alongside your name and the preview text, so spend it on something concrete about them. A subject that only announces you exist gives them little to go on.

Subject lines built around the reason:

• [Referrer] suggested I reach out
• quick question about [their specific work]
• [specific trigger] at [Company]
• 20 minutes on [specific decision]?
• [Project] next step

What to avoid: “Meeting request,” “Let’s connect,” “Touching base,” “Quick chat?” with no topic, and anything that leads with your company name. They signal a pitch and show no homework.

How to follow up without nagging

If the first email gets no reply, follow up on a spaced cadence and let every message carry something new. How many touches and how far apart depends on the stakes and the relationship, not on a fixed number. The rhythm we tend to use at Alore is a nudge around day 3, then day 5, day 7, day 10, and a final one near day 30, which usually lands at three to five touches. Treat that as a starting point rather than a rule. What carries it is that each message adds a reason to reply: a new time, a relevant example, a different angle on the original one.

Know when to stop. The moment your only remaining reason to write is that they have not replied, you have run out of road. Send one clean closing note and move on. The reason to stop is respect for the relationship and their inbox, not a last trick to force a response. For the wording of that last message and the reply lines that work, see our guide on what to send when you haven’t heard back.

Mistakes that sink a meeting request

Ignored meeting requests tend to fail for a few avoidable reasons. Five come up again and again, and fixing any one of them lifts your odds of a reply:

• Leading with yourself. Your company and your history do not register until the reader sees why the meeting matters to them.
• Claiming an outcome. A number you cannot back up yet (“we will double your demos”) reads as noise. Point at something real instead.
• No specific time. “Let me know when you’re free” adds work and stalls the thread.
• More than one ask. A call, a document, and an intro in one email stacks decisions, and the added friction makes a reply less likely.
• Emailing a generic inbox. A named decision-maker usually gets past the routing that swallows info@; our guide to finding and verifying an email address covers how to reach one.

When not to ask for a meeting

A meeting is the right ask only when a conversation is the next step. Often it is not, and asking anyway is what makes you easy to ignore. Skip the meeting request when:

• one email would settle the matter on its own,
• you cannot yet name a reason this person would care,
• the meeting would mostly be you doing research you could do first,
• the real next step is simply sending information they can read on their own time,
• you do not have enough context to make the time worth their while.

In those cases, send the shorter thing, or wait until you have a reason worth a slot on their calendar.

Frequently asked questions

How do you politely ask for a meeting in an email?

Open with a reason the recipient recognizes, state clearly that you would like a short meeting, keep it to one ask, and offer a couple of set times or a booking link. Politeness lives in the brevity and the clear next step. Extra flattery does nothing.

How long should a meeting request email be?

Short enough to read on a phone in a few seconds. Put the reason near the top, keep the ask to one line, and save the detail for the meeting itself.

What is the best subject line for a meeting request?

One that names the reason or the ask, such as “[Referrer] suggested I reach out” or “20 minutes on [specific decision]?” Avoid “Meeting request” and “Let’s connect,” which say nothing specific.

How do I ask someone senior for a meeting?

Be shorter and sharper than usual. State the decision or the reason in one line, name the exact time you need (often 15 to 20 minutes), and make the time simple to confirm. Senior people receive many requests, so yours has to justify itself fast.

The one thing to remember

It comes back to the same two things: a reason the reader can check, and a yes that costs them almost nothing. Drop the claimed outcome, lead with something they can confirm, ask for one thing, and make the time a single tap. The template changes with the relationship, but the move does not.

If you are sending these at any volume, the hard part is rarely the wording of one email. It is the timing and tracking: who is due for a follow-up, what you said last, and when to stop. That coordination is what an outbound engine like Alore is built to handle, so the thinking you just did about one meeting request holds up across a whole list.