In short
Below you'll find a template to copy, a worked time-zone example, a table for handling every kind of reply, and the invite steps for Google Calendar and Outlook.
- 1Write a specific subject line.
- 2Say why you want to meet and for how long.
- 3Offer 2–4 slots, one per line, each with day, date, start–end time and time zone.
- 4Ask for one reply that names a slot.
- 5Follow up once if there is no answer.
- 6Read the reply carefully, and ask a question if it is ambiguous.
- 7Recheck that the slot is still free, send the calendar invite, and confirm in the same thread.
What should a meeting request subject line say?
A meeting request subject line should name the topic, the meeting type and the date window, so the recipient knows what you want before opening it. "Intro call re: Q4 pilot, 30 min next week" does more than "Quick question". Keep the subject unchanged in replies so the thread stays together.
A simple formula works: topic, then meeting type or length, then time window. Some examples:
Vague subjects fail for a plain reason. The recipient can't tell whether your email needs five seconds or five minutes, so it waits. A specific subject lets them decide on the spot.
Gmail's conversation view groups an email and its replies into one thread. Keep the original subject, and your slot offers, the pick and the confirmation stay together in one conversation.
- Warm contact: "Catch-up on the partnership deck, 30 min next week"
- Cold contact: "Intro call re: invoicing for clinics, 20 min, week of 12 Oct"
- Internal 1:1: "1:1: hiring plan for Q1, 30 min Thursday or Friday"
- Client review: "October campaign review, 45 min, before 20 Oct"
How do you explain the purpose and length of the meeting?
State the purpose of the meeting and its length in the first two sentences of the email body. The recipient decides whether to accept based on why you want to meet and how much of their time it costs. Name one outcome and a duration, and offer a short agenda if there is more than one topic.
Write the purpose as an outcome, not a topic. "I'd like to agree the pilot scope so we can start in November" tells them what success looks like. "I'd like to chat about the pilot" does not.
Then give the length as a number: 15, 30 or 45 minutes. One decision fits in 15. A scoping conversation with three open questions probably needs 30.
If there is more than one topic, add a two- or three-line agenda under the first paragraph. If there is only one, the purpose sentence is the agenda.
Say the format too. A video link, a phone number, or an in-person venue with an address saves a reply asking which it is. A 25-minute call instead of 30 also leaves a gap before the next meeting.
How many time slots should you offer, and how do you write them across time zones?
Offer two to four specific time slots, each on its own line with the weekday, date, start and end time, and time zone. Two gives a real choice. More than four makes the recipient scan a grid. When the recipient is in another country, write every slot in both your zone and theirs, because daylight saving shifts the gap during the year.
"Tuesday afternoon" is not a slot. It forces a reply asking which hour, in whose afternoon. Write "Tue 13 Oct, 10:00–10:30 AM EDT" instead. Spread the options across different days and times of day, so one blocked morning doesn't knock out every choice.
Time zones are where cross-border scheduling breaks. According to the IANA Time Zone Database, Asia/Kolkata (IST) sits at UTC+05:30 all year with no daylight saving. The US and UK change their clocks, so your gap to them moves while yours stays put.
Worked example: three slots from Bengaluru (IST, UTC+05:30) to New York (EDT, UTC−04:00), week of 12 October 2026
The same 7:30 PM IST slot on Tue 3 November 2026 would be 9:00 AM in New York. That's because 19:30 IST is 14:00 UTC, and New York moves to UTC−05:00 once US daylight saving ends.
The dates matter. US daylight saving ends on the first Sunday in November, which is 1 November 2026. UK clocks go back on the last Sunday in October, which is 25 October 2026. From 25 October your gap to London widens from 4h30 to 5h30. From 1 November your gap to New York widens from 9h30 to 10h30. In the week between, London and New York sit 4 hours apart instead of 5. If you reuse slots from an old email across those dates, recompute every one.
| Slot | Your time (IST, UTC+05:30) | Their time (EDT, UTC−04:00) | Why this slot |
|---|---|---|---|
| Option 1 | Tue 13 Oct 2026, 7:30–8:00 PM | Tue 13 Oct 2026, 10:00–10:30 AM | Mid-morning for them, early evening for you |
| Option 2 | Wed 14 Oct 2026, 8:30–9:00 PM | Wed 14 Oct 2026, 11:00–11:30 AM | Different day and later in their morning |
| Option 3 | Thu 15 Oct 2026, 6:30–7:00 PM | Thu 15 Oct 2026, 9:00–9:30 AM | Start of their day, earliest evening for you |
Meeting request email template you can copy
This meeting request email template covers a subject line, a one-line purpose, a stated length, three slots written in both time zones, and a single clear ask. Replace each capitalised blank with your details. Below it is a short list of professional phrases for opening the request, proposing times and confirming.
Subject: TOPIC call, 30 min, week of 12 Oct Hi RECIPIENT NAME, ONE SENTENCE OF CONTEXT. I'd like to set up a call to OUTCOME YOU WANT. It would be a 30-minute video call, and I'll send the link with the invite. Would one of these work for you? - Tue 13 Oct, 10:00–10:30 AM EDT (7:30–8:00 PM IST) - Wed 14 Oct, 11:00–11:30 AM EDT (8:30–9:00 PM IST) - Thu 15 Oct, 9:00–9:30 AM EDT (6:30–7:00 PM IST) Just reply with the option that suits you and I'll send a calendar invite. If none fit, let me know a time next week that does. Thanks, YOUR NAME
Each slot puts the recipient's zone first, because they are the one choosing. Your own zone sits in brackets as a check for you.
If you send this kind of email often, save it. Gmail has a built-in Templates feature: once you turn it on under Settings > See all settings > Advanced, you can save a draft as a template and insert it into any new message.
### Professional phrases for scheduling a meeting by email
Opening the request
Proposing times
Asking for a reply
Confirming
Rescheduling
- "I'd like to find 30 minutes to agree the next step on OUTCOME."
- "Could we set up a short call about TOPIC?"
- "Would one of these work for you?"
- "I've listed times in your zone, with mine alongside."
- "Just reply with the option that suits you."
- "If none of these fit, let me know a time next week that does."
- "Great, Wednesday at 11:00 AM EDT it is. Invite on its way."
- "Something has come up on my side. Could we move to one of these instead?"
- "No problem at all. Here are two new options."
How do you follow up when nobody replies to a meeting request?
Follow up once in the same thread, after a few working days, with a short note that re-offers fresh slots. The original times may have passed or filled. Keep it to two or three lines, restate the purpose in a few words, and make the next step easy. Do not resend the whole first email.
Replying in the thread keeps your original context one scroll away. Swap out any slot that has expired, and keep the zone on each new one. A follow-up can be this short:
Hi Priya, bumping this in case it got buried. Still keen to agree the pilot scope. Would Tue 20 Oct, 10:00 AM EDT or Thu 22 Oct, 9:00 AM EDT work?
How long to wait is a judgment call. A cold contact may need a week. A colleague may need a day. After one or two nudges with no answer, stop. Try a different channel, or close the loop politely: "I'll leave this with you, and feel free to pick it up whenever suits."
The hard part is remembering who hasn't answered. Here's how to see every Gmail email still waiting on a reply.
What should you do with each kind of reply?
Every reply to a meeting request falls into one of five cases: a clear pick of a slot that is still free, a pick of a slot that has since filled, a counter-proposal, a decline, or an ambiguous answer. Only the first case should go straight to a calendar invite. Ambiguous replies like "Tuesday works" need one short clarifying question, not a guess.
Reply-handling matrix for meeting requests
Guessing on an ambiguous reply is how people end up waiting on a call the other person thinks starts an hour later. One closed question fixes it: "Great. Is that the 10:00 AM EDT slot on Tue 13 Oct?" They answer yes or no, and you're done.
The recheck column matters most. Days can pass between offering three slots and hearing back, and your calendar keeps filling in the meantime. A 30-second look before you send the invite prevents a double-booking that costs another full round of emails.
You can run this table by hand on any thread. Momo, which works in your Gmail and Google Calendar, follows the same logic: after you tap approve on its proposal card, it emails 2–4 free slots and sorts replies into pick, other, decline or unclear. It books a clear pick only if the slot is still free and sends anything unclear back to you. If you're comparing AI assistants for this, see what Gemini in Gmail can and can't do and our AI chief of staff tools comparison.
| Reply type | Example reply | What it means | Next action | Recheck calendar first? |
|---|---|---|---|---|
| Clear pick, slot still free | "Wednesday 11:00 AM EDT works." | One offered slot, named unambiguously | Send the calendar invite and confirm in-thread | Yes, immediately before sending the invite |
| Clear pick, slot no longer free | "Tuesday 10 AM is perfect." (you have since booked it) | They chose a slot you can no longer hold | Apologise briefly, offer the remaining slots or two new ones | Yes, which is how you catch it |
| Counter-proposal (other time) | "None of those work. How about Friday morning?" | They want a time you didn't offer | Check that window and reply with one or two exact times in both zones | Yes, for the window they suggest |
| Decline | "I'll pass for now. Maybe next quarter." | No meeting is wanted now | Thank them, release the held slots, and note a date to revisit if appropriate | No |
| Unclear or ambiguous | "Tuesday works." (two Tuesday slots offered) or "Any of those is fine." | No single slot can be identified, or the choice is left to you | Ask one closed question naming the exact slot, or pick one and say so explicitly before inviting | Yes, before confirming whichever slot is settled |
How do you confirm the time and send a calendar invite in Google Calendar or Outlook?
Confirm a meeting by checking the chosen slot is still free, creating the event in your calendar with the recipient as a guest, and replying in the email thread to say the invite is on its way. Google Calendar and Outlook both send a standard calendar invite, so the recipient can accept it in whichever calendar app they use.
That cross-app compatibility comes from RFC 5545, the iCalendar standard. An invite created in Google Calendar can be accepted in Outlook, and the other way round.
Start by rechecking the slot. Calendars fill while threads sit unanswered.
### In Google Calendar
Google's Create an event help page covers the full procedure. In short:
### In Outlook
Microsoft's Schedule a meeting or event in Outlook page has the steps for each Outlook version. The pattern is:
Then reply in the thread: "Invite sent for Wed 14 Oct, 11:00 AM EDT / 8:30 PM IST." That line gives both of you a written record of the agreed time in both zones.
- 1Click an empty slot or the Create button.
- 2Add a title, date and time, and check the event's time zone.
- 3Add the recipient's email address under guests.
- 4Add a video conferencing link if you need one.
- 5Put the purpose or agenda line in the description.
- 6Save, and choose to send the invitation to guests.
- 7Create a new meeting from the calendar.
- 8Add attendees by email.
- 9Set the start and end time, and the time zone.
- 10Use Scheduling Assistant, where your version has it, to check internal attendees.
- 11Add the agenda to the body and send.
How do you schedule a meeting with several people from different companies?
To schedule with several people from different companies, make one person the owner of the thread, put everyone in a single email, and offer slots you have already checked against every calendar you can see. Ask each person to reply to all with the slots that work, then confirm the overlap with one invite.
One owner and one thread prevents the classic failure where two side conversations settle on two different times. Ask people to list every slot that works, not just their favourite, because you need the overlap. With four attendees and three slots, a single "Option 2" from each tells you far less than a full list.
When attendees sit in different zones, write each slot in every zone involved, one slot per line. If an executive has an assistant, copy the assistant and say so.
Expect gaps in what you can see. Past five or six people, a poll or a booking link usually beats an email thread.
When should you skip the email and send a booking link or a direct invite?
Skip the email thread when you control the time or expect many bookings. Send a direct calendar invite to a close colleague whose calendar you can see. Send a booking link, such as a Google Calendar appointment schedule, when many people need slots with you. Use an email with proposed slots for senior, cold or external contacts, where a link can read as presumptuous.
Email thread, booking link or direct invite?
For high-volume inbound booking, the built-in tools are often the better fit than any email workflow. Google Calendar's appointment schedules create a booking page where people pick an open slot from your calendar. That help page sets out which account types can create one and which features need a paid plan, so check it against your own account. Outlook has its own scheduling features too.
| Situation | Best method | Why |
|---|---|---|
| Colleague whose calendar you can see | Direct calendar invite | You can already see a free slot, so an email adds a round trip |
| Many people need time with you (office hours, interviews, demos) | Booking link, e.g. Google Calendar appointment schedule | Each person self-serves without a thread per booking |
| Senior, cold or external contact | Email with 2–4 proposed slots | Proposing times does the work for them instead of handing them a link |
| Group across several companies | Email thread with one owner, or a poll | Free/busy is usually not visible across organisations |
| Recipient in a different time zone with little overlap | Email with slots written in both zones | You control which hours you offer and avoid late-night bookings |
Sources
Every number and claim above links to one of these.
- Gmail Help: Choose whether replies are grouped in conversations — conversation view groups replies into one thread
- IANA Time Zone Database — IST at UTC+05:30 with no daylight saving; New York offsets
- NIST: Daylight Saving Time — US daylight saving ends the first Sunday in November
- GOV.UK: When do the clocks change? — UK clocks go back the last Sunday in October
- Gmail Help: Create email templates — Gmail Templates feature and where to enable it
- RFC 5545: iCalendar — standard format behind calendar invites
- Google Calendar Help: Create an event — creating an event and inviting guests
- Microsoft Support: Schedule a meeting or event in Outlook — Outlook meeting invite steps
- Google Calendar Help: Appointment schedules — booking pages and account eligibility