Most meeting requests fail for boring reasons. The reader can't tell what the meeting is for, how long it will take, or what they are supposed to do next, so the email sinks under everything that is easier to answer. A good request removes every one of those reasons in about a hundred words. This guide breaks the request into its parts, gives you subject line formulas and fifteen templates for the situations that come up most, from a cold prospect to your own manager, and covers how to offer times, how to follow up without nagging, and how to stop time zones from wrecking the whole thing.
Quick answer: A good meeting request email is under about 125 words and does five things: says who you are or how you're connected, gives a reason that matters to the reader, asks for a specific length and format, offers two or three specific times in their time zone (or a booking link when they asked to meet or book with you often), and makes saying no easy. Follow up twice, three to seven days apart, then stop.
Key takeaways
- Lead with why the meeting matters to them, not to you, and say exactly how long it will take.
- Keep it under about 125 words with one clear ask. The subject line should carry the topic and the size of the ask.
- When you are asking a favor, offer two or three specific times in their zone. Send a booking link when they asked to meet or book with you regularly.
- Follow up twice in the same thread, three to seven days apart, adding something new each time. Then stop.
- Write times with a city or offset attached, and watch the weeks when daylight saving time changes on different dates in different countries.
What is a meeting request email?
A meeting request email is a short message that asks a specific person for a specific amount of time, for a stated reason, with an easy way to say yes. It is not the same as a calendar invitation. An invitation is the event itself and assumes the meeting is already agreed. Sending one to someone who hasn't agreed, such as a prospect, a senior leader or a stranger, skips the step where they get to decide, and plenty of people decline or ignore unsolicited invites on principle. Ask first, invite second.
The encouraging part is that people say yes more often than askers expect. In a 2008 series of studies in the Journal of Personality and Social Psychology, Francis Flynn and Vanessa Lake found that people underestimated by as much as 50% the likelihood that others would agree to a direct request for help. Those studies mostly involved small favors asked in person, but the lesson travels: a clear, direct ask beats a hedged one.
The less encouraging part is specific to email. A later study by Mahdi Roghanizad and Vanessa Bohns, summarized by the Association for Psychological Science, found that people asking strangers for a favor by email were about as confident as people asking face to face, yet their emailed requests worked far less well. Recipients trusted and empathized with face-to-face requesters more, and found it easier to say no to an email. So a request to someone who doesn't know you has to earn that trust in its first two lines: who you are, and why you are writing to them in particular.
What should a meeting request email include?
Every effective request has the same seven parts. Some take a single phrase, and none should need more than two sentences.
| Element | Purpose | Example |
|---|---|---|
| Subject line | Tells them the topic and the size of the ask before they open it | "20 min on your Q1 onboarding plan?" |
| Connection | Answers "who is this, and why me?" | "Priya Shah suggested I contact you about the vendor review." |
| Reason | Shows what the meeting does for them | "I'd like your view on the two shortlisted vendors before we sign." |
| The ask | States length and format so they can judge the cost | "Could we do a 20-minute video call?" |
| Times or link | Removes the back-and-forth | "Tuesday 10:00 am or Thursday 2:00 pm, your time (Eastern)." |
| Easy out | Lowers the pressure and makes any reply more likely | "If email is easier, I can send the two questions instead." |
| Signature | Gives name, role and organization | "Sam Lee, Operations Lead, Northwind Logistics" |
The two parts people skip most are the reason and the easy out. "I'd love to connect" is not a reason. "I'd like your view on the two vendors before we sign on Friday" is. And the easy out is not weakness. A reader who can say "not now" in one line is far more likely to reply at all, and "not now" is information you can act on.
The one-sentence test
Before writing anything, finish this sentence: "I want [length] with [person] so that [outcome], and the next step is for them to [pick a time / reply / pass this to someone]." If you can't finish it, the email isn't ready, and the meeting may not be needed. Sometimes the honest answer is a two-line question by email instead.
How long should a meeting request email be?
Short enough to read on a phone without scrolling: roughly 50 to 125 words for most requests. One frequently cited set of public data comes from Boomerang, which makes an email plug-in and published an analysis of its users' messages in 2016. It found that messages of 50 to 125 words all had response rates above 50%, that subject lines of three to four words drew the most responses, and that emails asking one to three questions were 50% more likely to get a response than emails asking none.
Treat those numbers as a guide, not a law. They come from one vendor's users, they count any reply rather than a booked meeting, and the data was not limited to cold outreach, so a first email to a stranger may well do worse. But they match what experienced senders find: one screen, one ask, one question.
There are two exceptions. A request to an executive can be shorter still, because the reader is skimming between meetings. And a request that needs context before anyone could answer it, such as a student asking a professor about a specific research problem, can run longer, as long as the ask sits in the first paragraph rather than the last.
What subject line should you use for a meeting request?
The subject line decides whether the email is opened now, later or never. The strongest ones carry the topic, the size of the ask and often a question mark, in a handful of words. "Meeting request" on its own does none of that.
| Formula | Example | Use it for |
|---|---|---|
| Topic + length + question | "15 min on the Q1 launch plan?" | Most requests, internal and external |
| Mutual contact | "Priya Shah suggested we talk" | Introductions and referrals |
| Their work + ask | "Your onboarding talk: a 20-min question?" | Networking, mentors, experts |
| Decision + deadline | "Decision needed on the vendor by Friday" | Executives and approvers |
| Specific day | "Coffee next Thursday?" | Warm contacts |
| Change of plan | "Move Tuesday's review to Wednesday?" | Rescheduling |
| Urgent + time | "Urgent: 15 min today on the billing outage" | Genuine emergencies only |
Three rules apply to all of them. Front-load the useful words, because phone inboxes cut subject lines short. Never fake a reply with "Re:" or a forward with "Fwd:"; it buys one open and costs the relationship. And keep it honest. If your email is a commercial message, the US CAN-SPAM Act prohibits deceptive subject lines, and the FTC's compliance guide points out that the law makes no exception for business-to-business email.
How do you write a meeting request email, step by step?
- Decide whether it needs a meeting. If a reply could answer the question, ask the question. People notice and appreciate it.
- Name the outcome. A decision, a recommendation, an introduction, a plan. "Catch up" is fine for a friend, not for a busy stranger.
- Pick the shortest realistic length. Fifteen or twenty minutes for a first conversation, thirty for a working session, an hour only when the agenda needs it. A short meeting is easier to fit and can always run longer by agreement.
- Choose how they will pick a time. Specific times, a booking link, or a one-off link with hand-picked slots. The decision table below helps.
- Write the first two lines for a stranger. Who you are, how you found them, why them. Assume those two lines are all they will read.
- Put the ask and the times in the same paragraph. The reader should be able to reply "Tuesday works" without scrolling back up.
- Add the easy out, then sign off with your full name, role and organization. For commercial outreach, include whatever the law where you operate requires, such as a postal address and an opt-out.
- Write the subject line last, using one of the formulas above, once you know exactly what you are asking.
- Schedule it for their morning. Gmail's schedule send and Outlook's delay or schedule sending option both let you write now and choose when the email is delivered, so you can time it to land around 8:30 am in their time zone, near the top of the inbox rather than under a night's worth of newer mail.
Should you propose specific times or send a scheduling link?
It depends on who is doing whom a favor. A scheduling link is a URL to a booking page where the other person picks a slot from your live availability. A one-off link is a single-use booking page that shows only the handful of times you hand-picked for one person. Proposing times means typing two or three options into the email itself.
| Situation | Best option | Why |
|---|---|---|
| You are asking a favor of a stranger or someone senior | Two or three specific times, link as a fallback | You do the work; they only have to pick |
| Someone senior where only certain slots will do | One-off link with hand-picked times | Reads as "I chose these for you" and can't be booked twice |
| They asked to talk, or came in through your website | Booking link | They want speed and choice, not a negotiation |
| Existing client or contact who books regularly | Booking link | Familiar, and saves both sides an exchange |
| Colleague on the same calendar system | Check free/busy, then propose one time or send the invite | Their calendar is visible; a link adds a step |
| They already offered a time | Accept it, or counter with one specific time | Replying with a link ignores their effort |
| Five or more people at different organizations | A meeting poll, or one person coordinating | A booking page lets each invitee pick a slot; it can't find the one time that suits everyone |
| An urgent problem today | A specific time today, plus a call or chat message | Email alone is too slow |
The etiquette behind this table is covered in detail in is it rude to send a scheduling link? The short version: the link is neutral and the framing decides. Offer it as a convenience ("if it's easier, grab any time here"), keep a human alternative in the same sentence, and never answer a time someone offered with your link.
One case deserves its own note. When a prospect has asked you for a meeting, the reply is a race, and a fast answer with a booking link tends to do more than a polished one sent an afternoon later. The guide to speed to lead explains why the first response time matters and how to measure yours.
How to propose times well
- Offer two or three options on different days and at different times of day, so at least one is likely to fit.
- Write them in the reader's time zone first, then yours: "Tuesday 9:00 am your time (2:00 pm for me in London)."
- Include the date for anything more than a few days out: "Tuesday 3 November", not just "Tuesday".
- Check every calendar you use before offering a slot. If you run work and personal calendars, or two work accounts, preventing double booking across multiple calendars shows how to keep them in step.
- Hold the offered times on your calendar until they reply, so you never have to withdraw one.
- Add a fallback: "If none of these work, send me two times that do and I'll fit around you."
15 meeting request email templates
The templates below are grouped by situation: prospects, clients and vendors; your manager, executives and other teams; networking, mentors and recruiting; and rescheduling and follow-ups. Each body is roughly 130 words or fewer. Replace everything in square brackets, and delete any sentence that doesn't apply rather than leaving a generic one in. The specific detail is what makes a template stop reading like one.
How do you ask a prospect, client or vendor for a meeting?
1. Cold prospect you have never spoken to
Subject: 20 min on [their team]'s [problem area]?
Hi [first name],
I saw that [specific, checkable fact, such as "you're opening a second warehouse in Reno"]. Teams at that stage often run into [specific problem], which is what we work on at [company].
Would a 20-minute call be useful to see whether it applies to you? I could do [Tuesday] at 10:00 am or [Wednesday] at 2:00 pm, both Central time. If neither works, here's my calendar: [link].
If this isn't a priority this quarter, a one-word "no" is completely fine, and I won't follow up.
[Name], [role], [company]
Why it works: one checkable detail proves this is not a mass email, the ask is small, and the times are in their zone. Add the sender details and opt-out your local rules require. If the call turns into a demo, the guide to running a sales demo covers what to do with the time.
2. After an event or an introduction
Subject: [Introducer] suggested we talk about [topic]
Hi [first name],
Thanks for the introduction, [introducer] (moving you to bcc). [First name], I'm [one line on who you are]. [Introducer] mentioned you're [working on X], and I'd value 20 minutes to [specific purpose, such as "compare notes on moving support in-house"].
I could do [day, date] at [time] or [day, date] at [time], your time, or pick anything that suits here: [link].
Looking forward to it,
[Name]
Event variant: replace the first paragraph with "We spoke briefly after [session] at [event] about [topic]. You mentioned [specific detail], and I'd like to pick that up properly."
Why it works: the introducer's name does the trust-building a cold email can't, and moving them to bcc spares their inbox. Send it within a day or two while the introduction is still fresh.
3. Existing client
Subject: 30 min to plan [next quarter / the renewal / phase two]?
Hi [first name],
Now that [milestone, such as "the rollout to the Denver office"] is live, I'd like to book 30 minutes to review what's working and agree priorities for [next period]. I'll bring [a usage summary and three recommendations]. It would help if you could bring [one thing, such as "the list of open requests from your team"].
Pick any time that suits on my calendar: [link]. If it's easier, reply with a couple of times and I'll send the invite.
Thanks,
[Name]
Why it works: clients already trust you, so a booking link is a convenience rather than a demand, and the agenda tells them the meeting is worth having. For regular check-ins, a dedicated event type on your booking page, such as "Quarterly review", saves writing this email every quarter.
4. Vendor (when you are the buyer)
Subject: [Your company] evaluation: 45-min call on [two use cases]?
Hi [first name],
We're evaluating [category] tools for a team of [number], and [product] is one of three on our shortlist. We plan to decide by [date].
Could we book a 45-minute call focused on [use case one] and [use case two]? We've already seen the overview video, so please skip the general tour. On our side will be [roles].
We can do [day, date] at [time] or [day, date] at [time], [your time zone]. If possible, please send pricing for [number] users before the call.
Thanks,
[Name], [role], [company]
Why it works: buyers get far better meetings by setting the agenda, the deadline and the attendees up front. A vendor who knows the decision date and the use cases can bring the right person.
How do you ask your boss, an executive or another team for a meeting?
5. Your manager
Subject: 20 min this week about [topic] (nothing urgent)
Hi [manager's name],
Could we take 20 minutes this week to talk about [taking on the Q1 reporting work / my development plan / workload on Project X]? Nothing is wrong. I'd like your input before [date or decision].
I'm free [Wednesday after 2:00 pm] or [Thursday morning]. Happy to use part of our regular one-on-one instead if that's easier.
I'll send a short list of points the day before.
[Your name]
Why it works: "nothing urgent" removes the dread a vague "Can we talk?" creates, and offering the existing one-on-one respects their calendar. The guide to effective one-on-one meetings covers how to run the conversation once you are in the room.
6. Senior executive
Subject: 15-min decision on [topic] before [date]?
Hi [name],
I lead [team or role]. We need a decision on [specific choice] before [date], and [their direct report or a colleague] suggested you're the right person to make it.
In 15 minutes I'd walk through two options and my recommendation. The short version is below if you'd rather decide by email.
Would any of these work, your time? [Day, date, time], [day, date, time] or [day, date, time]. If [assistant's name] manages your calendar, I'm happy to arrange it with them.
[Name], [role]
[Three-line summary: option A, option B, recommendation and why]
Why it works: executives respond to decisions, deadlines and brevity. Three hand-picked times show you did the work, the decide-by-email option respects their time, and naming their assistant shows you know how their calendar actually runs.
7. Another team in your company
Subject: [Your team] + [their team]: 30 min to agree on [handoff / ownership / design]?
Hi [name],
My team is [doing X], and it touches [their system or process] at [specific point]. Before we commit to a design, I'd like 30 minutes with you, and anyone on your side who owns [thing], to agree [specific outcome, such as "who owns the data migration step and by when"].
Proposed agenda: current flow, proposed change, owner and date.
Your calendar looks free [day] at [time] and [day] at [time]. If a meeting is overkill, add comments to the doc here instead: [link], and we'll skip it.
Thanks,
[Name]
Why it works: a cross-team request competes with that team's own priorities, so the outcome and the agenda have to be explicit. The "skip it" option often gets you the answer faster than the meeting would. If you are writing the agenda now, the guide to meeting agendas that work has formats for working sessions.
8. Urgent issue
Subject: Urgent: 15 min today on [issue] (decision needed by [time])
Hi [name],
[One sentence on the problem, such as "Last night's invoice run failed and [number] customers weren't billed."] We need your decision on [specific choice] before [time] today.
Can you join a 15-minute call at [time] or [time]? Link: [video link].
If you can't make either, reply "yes" or "no" to [the proposed fix] and we'll proceed on that basis.
I'm also messaging you on [chat tool] because this is time-sensitive.
[Name], [phone number]
Why it works: it states the problem, the decision and the deadline in the first three lines, offers an email-only path, and doesn't rely on email alone. Keep "Urgent" for genuine emergencies, or people learn to ignore it.
How do you ask for a networking, mentoring or recruiting meeting?
9. Networking or coffee chat
Subject: Coffee near [place] or 20 min on a call?
Hi [name],
I [read your article on X / heard you speak at Y], and your point about [specific idea] stuck with me. I'm [one line on who you are], and I'm working on [specific question or decision].
Would you be open to a 20-minute coffee or call in the next few weeks? I'd love to ask you two things: [question one] and [question two]. I'm flexible and happy to work around you, or you can grab any time here if that's easier: [link].
Either way, thanks for [the article / the talk].
[Name]
Why it works: two named questions turn "Can I pick your brain?" into a request with a clear end. Offer to go to them, pay for the coffee, and keep to the time you asked for.
10. LinkedIn message version
Hi [name], I enjoyed your post on [topic], especially [specific point]. I'm working on [related thing] and would value 15 minutes of your view on [one question]. Open to a quick call in the next couple of weeks? Happy to work around your calendar.
Why it works: LinkedIn messages are read in a small window, often on a phone, so the whole request has to fit in three lines. Leave the link out of the first message, reply in the same thread when they answer, and move to email or a booking page only once they've said yes.
11. Professor, adviser or mentor
Subject: Question about [topic] from [course or program]: 20 minutes?
Dear Professor [surname],
I'm [name], a [year] student in [program or course]. I'm working on [project] and I'm stuck on [specific point]. I've already [read X / tried Y], which got me as far as [where you are].
Could I have 20 minutes during your office hours or at another time that suits you? I'm free [two windows], or I can come to your [day] office hours if that's simpler.
Thank you for considering it.
[Full name], [student ID if your institution uses them]
Mentor variant: swap the first paragraph for one line on how you know their work, and add "I'm hoping to make a decision about [X] by [date], and your experience with [Y] is exactly what I'm missing."
Why it works: showing what you have already tried proves you are not asking them to do your homework, and pointing at existing office hours makes yes easy.
12. Recruiter to candidate (and the reverse)
Subject: [Role] at [company]: 25-min intro call?
Hi [name],
I'm [name], recruiting for a [role] on the [team] at [company]. Your experience with [specific skill or project] is close to what the team needs for [specific work].
Would a 25-minute call be worth your time to hear more? It's an informal conversation, not an interview, and I'll share the salary range and the process up front. Choose any time that suits you here: [link]. That includes early mornings and evenings if daytime is hard around your current job.
Best,
[Name], [company]
Candidate variant: "Hi [name], I applied for [role] on [date] and I'm very interested in the team's work on [X]. Would 15 minutes be possible to understand the next steps? I'm free [two windows], or happy to fit around your schedule."
Why it works: candidates who are already employed need out-of-hours slots and an honest description of the call. The interview scheduling guide covers the rest of the process, and the recruiting solution page shows how candidate self-scheduling and recorded interviews work for a hiring panel.
How do you reschedule or follow up on a meeting request?
13. Rescheduling a meeting you already agreed
Subject: Can we move [Thursday's] call to [Friday]?
Hi [first name],
I'm sorry, something has come up and I can't make our [meeting] on [day] at [time]. Could we move it to [day, date] at [time] or [day, date] at [time], your time? If neither works, pick anything that suits here: [link], and I'll fit around you.
Apologies for the shuffle, and thank you for being flexible.
[Name]
Why it works: it owns the change, offers specific replacements immediately and skips the long excuse. Send it as early as you know, and if you booked through a scheduling tool, use its reschedule link so the old calendar event and video link are cleared rather than left behind.
14. Follow-up #1 (three to four business days later)
Subject: none needed; reply in the original thread so your first email sits underneath
Hi [first name],
Bringing this back to the top of your inbox. [One new, useful thing, such as "Since I wrote, we published a two-page summary of [topic], linked here" or "The call would also cover [new point]".]
Would [new day and time] or [new day and time] work, your time? If now isn't a good time, just say so and I'll check back next quarter.
[Name]
Why it works: it adds something instead of "just bumping this", offers fresh times in case the first ones passed, and gives a polite route to "later".
15. Follow-up #2 (closing the loop)
Subject: none needed; reply in the same thread again
Hi [first name],
I haven't heard back, so I'll assume the timing isn't right and won't email about this again. If [problem or topic] comes up later, my calendar is here: [link], and I'd be glad to help.
Thanks for reading,
[Name]
Why it works: a clear, friendly close removes the awkwardness of not replying, and people who were simply busy sometimes answer this one. Mean it: if you say you'll stop, stop.
What follow-up cadence should you use?
We know of no rigorous public research on the ideal number of follow-ups for meeting requests, so treat this as a sensible default rather than a formula. The principle is simple: each touch adds something, each one is shorter than the last, and the sequence ends.
| Touch | Cold or external contact | Internal colleague | What changes |
|---|---|---|---|
| Original request | Day 0 | Day 0 | The full request, with times or a link |
| Follow-up 1 | 3 to 4 business days later | 1 to 2 business days later | Same thread, one new detail, fresh times |
| Follow-up 2 | About a week after follow-up 1 | Switch to chat or a quick word in person | Smaller ask, easy no |
| Stop | After follow-up 2 | Escalate only if real work is blocked | Note a date to try again next quarter |
Two adjustments. If the request is time-bound, such as a decision needed before a deadline, compress the gaps and say why. And if the person replied "not now", that isn't a no-reply case: put a reminder in your calendar for the time they named and write a fresh request then.
How do you request a meeting across time zones?
A time-zone slip is one of the easiest ways to turn an accepted meeting into a missed one, and it is almost entirely preventable. Five habits cover it.
- Lead with their time. "Tuesday 9:00 am your time (2:00 pm for me in London)." They should never have to convert anything.
- Use city names or UTC offsets, not abbreviations. IST can mean India, Ireland or Israel, and CST can mean US Central or China. "New York time" or "UTC−5" can't be misread.
- Write dates unambiguously. 03/11 is 3 November in London and March 11 in New York. Write "Tuesday 3 November".
- Mind the daylight saving gap. Countries change their clocks on different dates. In the United States, daylight saving time runs from the second Sunday in March to the first Sunday in November, according to NIST, which also notes that Hawaii and most of Arizona don't observe it. In the UK, the clocks change on the last Sunday in March and the last Sunday in October. For a few weeks a year, the usual gap between two cities is an hour different.
- Let software do the conversion. A booking page that shows every slot in the visitor's own time zone removes the arithmetic, which is the main argument for a link when you work across regions.
Here is what the daylight saving mismatch does to the London to New York gap over the next year:
| Period | London | New York | Gap |
|---|---|---|---|
| Until 25 October 2026 | BST (UTC+1) | EDT (UTC−4) | 5 hours |
| 25 October to 1 November 2026 | GMT (UTC+0) | EDT (UTC−4) | 4 hours |
| 1 November 2026 to 14 March 2027 | GMT (UTC+0) | EST (UTC−5) | 5 hours |
| 14 March to 28 March 2027 | GMT (UTC+0) | EDT (UTC−4) | 4 hours |
| 28 March to 31 October 2027 | BST (UTC+1) | EDT (UTC−4) | 5 hours |
Some zones never change. India stays on UTC+5:30 all year, so a 10:00 am New York call is 7:30 pm in Bengaluru in the summer and 8:30 pm in the winter. When you are always the one asking someone to stay late or start early, offer to take the inconvenient slot next time. The guide to time-zone management for global teams covers overlap windows and rotating meeting times in more depth.
What mistakes make people ignore meeting requests?
- No reason. "I'd love to connect" or "pick your brain" asks the reader to work out why they should bother. Name the outcome.
- Making them do the scheduling. "Let me know what works for you" hands them a task. Offer times or a link.
- Asking for an hour by default. A first conversation rarely needs more than 20 minutes. A large ask from a stranger is an easy no.
- The life story. Three paragraphs about you before the ask. Move the ask up, cut the rest.
- Several asks in one email. A meeting, a referral and feedback on a deck. Pick one.
- Times without a zone. "3 pm Thursday" to someone in another city is a coin toss.
- A bare link to someone senior. "Here's my calendar" with nothing else reads as "you work around me". Hand-pick times first.
- Attachments and multiple links in a cold email. To a stranger they look like risk, not value. Put the essential point in the body.
- An invite before agreement. A calendar invite to a prospect who hasn't said yes is presumptuous, and many people decline it unread.
- Guilt in the follow-up. "Did you see my email?" helps nobody. Add something new, or close the loop.
What should you do once they say yes?
Confirm quickly and properly. Send a calendar invitation with the video link or address on the event itself, a one-line purpose and, for anything longer than a quick chat, a short agenda. Reply to their yes in the same thread so the context stays together. If the meeting is more than a couple of days away, a reminder the day before and again shortly before keeps it on their calendar; the guide on how to reduce no-shows covers reminder timing and what each email should say. After the meeting, the work moves to the follow-up, which the guide to follow-up emails after a sales meeting covers with templates.
How do you send meeting requests with PepoSmart?
PepoSmart is an AI scheduling and meeting-intelligence platform, and two of its scheduling tools map directly onto the decision table above. Both are available on every plan, including Free.
A booking page for people who are happy to pick
Each event type gets its own booking page with a title, a short description, a duration and the times your availability rules allow. Slots are checked against your connected Google and Outlook calendars, up to six accounts, so busy times are not offered, and every time is converted into the invitee's local time zone automatically. Intake questions (single line, multi-line, radio, checkbox, dropdown or phone number) tell you what the meeting is about before it starts, and invitees can add up to ten guests. Confirmation and reminder emails go out automatically, with reminder timings set per event in hours before the meeting, and every booking email carries reschedule and cancel links.
The same page can sit on your website through website embeds, and each event has a QR code for slides, posters or a business card. The guide to embedding a booking calendar explains inline and popup options.
A one-off meeting for one person
For the senior-person or favor-asking case, a one-off meeting lets you pick a handful of specific times for a single conversation. The link is single use: once one of the offered times is booked, the meeting can't be booked again. The optional "Reserve times" setting holds the offered slots on your calendar until one is chosen, so you never promise the same hour twice, and "Copy times" pastes the options into your email as plain text, labelled with the time zone you selected. That gives you both halves of a good request: specific times in the body for people who prefer to reply, and a one-click way to confirm for people who prefer to book.
After the meeting
If you record the call with PepoSmart's AI notetaker on Zoom, Google Meet or Microsoft Teams, a draft follow-up email is ready for your review afterwards; the AI follow-up emails page shows what it contains. AI meeting notes are part of Starter and above, and every plan, including Free, includes 2 AI recordings for the lifetime of the account so you can try the notetaker first. For teams, a round-robin event gives prospects one link that books whichever teammate is free; team events need team seats, which start on Starter.
When is PepoSmart the wrong tool for a meeting request?
- The first email is still yours. PepoSmart does not find prospects or write your outreach. The request should come from your own inbox, in your own words, and the templates above matter more than any tool.
- Some meetings need a person, not a page. A board member, an upset client, a sensitive conversation with someone on your team: propose times yourself or pick up the phone. Even a one-off link can be the wrong tone.
- Booking pages are built for one invitee choosing a slot, or for several people joining a group session you've set up. When five people at three organizations must agree on one time, a meeting poll or a single coordinator works better.
- It only sees calendars you connect. A conflict on a calendar you haven't connected is invisible to it, and a new conflict or a change to which calendars are checked can take about two minutes to show on booking pages.
- A booking is not consent to marketing. Someone who booked a meeting has not agreed to your newsletter. If you add booking contacts to email broadcasts or sequences, which are on Professional and above, you need your own lawful basis for doing so.
Summary
A meeting request gets a yes when the reader can see, in a few seconds, who you are, why the meeting matters to them, how long it takes and how to say yes or no. Keep it under about 125 words, put the topic and length in the subject line, and offer two or three specific times in their zone when you're asking a favor, or a booking link when they asked to meet. Follow up twice with something new, then stop, and write every time with a city or offset attached. If you want the link half handled for you, create a free PepoSmart account: booking pages with automatic time-zone conversion, one-off meetings with hand-picked times, intake questions and reminder emails are included on every plan, and the pricing page sets out what the paid plans add.
