Arranging one meeting by email takes a little over eight messages, and it usually runs across days. Most of those messages settle nothing. The move that collapses it is to put the decision in the first message. Offer real times from a calendar you’ve already checked, so the only reply anybody owes you is a choice.
- The eight is a measured number. A year-long deployment that ran scheduling for 178 people handled 15,659 emails across 1,894 meeting requests.
- The typing is the small part. The cost is elapsed days, plus the work of picking the thread back up each time.
- One round trip runs most of a working day, even when the other person has nothing to write.
- Two of the eight messages carry a decision. The other six exist because the first one asked a question.
Eight messages, and what each one is for
The number comes from Calendar.help, a scheduling assistant built and deployed by Microsoft Research. Justin Cranshaw, Emad Elwany, Todd Newman, Rafal Kocielnik, Bowen Yu, Sandeep Soni, Jaime Teevan and Andrés Monroy-Hernández wrote it up in Calendar.help: Designing a Workflow-Based Scheduling Agent with Humans in the Loop, presented at CHI 2017. People cc’d an assistant called Cal on a meeting request, and Cal took the thread from there.
The final field study ran from April 5 to August 25, 2016. In it, 178 participants delegated 1,894 meeting requests involving 1,981 invitees. Cal sent and received 15,659 emails doing it. That’s a little over eight messages per request. It’s a real count of real correspondence, from an era of ordinary mail clients and ordinary calendars. The meetings were mostly small: 84% were one to one, and 15% had three or more people.
Eight is also what you get if you write out the ordinary version by hand.
- You ask whether they have time in the next couple of weeks.
- They say yes, and ask what suits you.
- You offer Tuesday or Thursday morning.
- They can do Thursday, but not before ten.
- You suggest 10:30.
- They confirm.
- You send the invitation.
- They accept it.
Read down that list and see where the information sits. Messages one and two establish that two people who already wanted to meet still want to meet. Message three is the first one with a time in it. Messages four and five negotiate around one fact about their morning. Six carries the decision. Seven and eight are bookkeeping.
The same paper puts a number on the effort inside all this, and it’s small. When a request went smoothly, the whole of it took 2.6 minutes of an assistant’s working time. Scheduling is quick work. What makes it heavy is the shape: two and a half minutes of attention, spread over eight arrivals across four days.
Why it takes days rather than minutes
A round trip in email takes hours, even when the reply needs no thought.
Doodle, the scheduling company, published the State of Meetings Report 2019 (checked August 19, 2026). It draws on a survey of 6,500 professionals in the US, UK and Germany, alongside 19 million meetings arranged on its own platform. Inside it sits the most useful measurement in the whole subject. Doodle looked at more than 19 million responses to invitations sent in 2018 and worked out how long people took to confirm or decline. The three fastest countries averaged between five and a half and six hours. The three slowest averaged between ten and eleven.
Hold on to what that measures. A Doodle invitation asks one thing of the recipient: tick the times you can make. A few clicks covers it. And the average turnaround is most of a working day. This is a vendor reporting on its own users. They opted into a poll and were already cooperating, which makes the number generous if anything.
Now put your eight messages on that clock. Four round trips at half a day each is two working days when everything lands cleanly. Things land the other way too. Message three arrives at four in the afternoon and gets answered the next morning. Message five arrives on a Friday. The Calendar.help engineers say it plainly in their implementation notes, explaining why the system kept old versions of its workflow running. Meeting requests, they write, “typically take days to complete”.
There’s a second cost, and it’s the one nobody counts. Each of those eight arrivals lands in a different hour of a different day. Each time, you have to remember what was proposed, what was ruled out and whose turn it is. The thread is a small piece of state you’re holding in your head across half a week. That’s why a scheduling chain feels heavier than its two and a half minutes. Three of them running at once feels heavier still.
The move: decide in the first message
One change does the work here, and everything else is detail. Tell them when you’re free.
- You: “Happy to talk this through. I have Thursday at 10:30, Thursday at 2 or Friday at 9, all UK time. Say which and the invite will follow.”
- Them: “Thursday at 10:30.”
Then the invitation goes out. It’s a record of what you agreed, and it does its job whether or not anybody writes back.
Here’s why it works. An open question can only produce information. “When are you free?” gets you their availability. You compare that against your own calendar. That produces a proposal, and they still have to accept it. Three round trips before anybody has agreed to anything, and it’s three even when both people behave perfectly. A proposal needs one. The gain is in the rounds you remove, where nothing was getting settled.
Three times is about the right offer. Jaeyoon Song at MIT, Zahra Ashktorab at IBM Research and Thomas W. Malone at MIT set out the constraint precisely in Togedule: Scheduling Meetings with Large Language Models and Adaptive Representations of Group Availability, published in Proceedings of the ACM on Human-Computer Interaction in 2025. They write that “the number of choices that can be effectively handled in a single email is limited, often resulting in multiple email threads going back and forth until an acceptable meeting time is agreed upon and details are finalized”. One option reads as an instruction and invites a counter-offer. Ten options reads as a spreadsheet, and their experiments found that people asked to consider a long list stop reading part way down. Three is wide enough that a yes is likely and short enough that it reads as an offer.
The hard part is making the proposal true. The moment you name three slots, you’re saying you’re free in all three. So you need to know what’s in your calendar. That includes the calendar you keep apart from work, and the appointment you agreed to on the phone and never wrote down. This is the one place a guess costs you. They accept a time you can’t make, you’re rescheduling, and the repair costs more messages than the offer saved. If your availability is spread across more than one calendar, that reconciliation is the real bottleneck, and two calendars is about closing it.
Two neighboring pieces carry the rest. The wording of the proposal, and what belongs in the invitation so nobody writes back asking, is writing the invitation. Naming times that survive the recipient being three time zones away is time zones.
Where the eight messages actually go
Here’s the part most advice about this leaves out. The eight messages move. Somebody still carries them.
Cal, in the field study, sent and received all 15,659 of them. What changed for the 178 participants was their share of the correspondence. The authors are direct about the design goal: “Although Cal may send many emails in the process of scheduling a meeting, individuals only see a small slice of the total communication.” The chain still happened. Somebody else was in it.
That gives you three honest options, and they differ in who absorbs the traffic.
You write a better first message. It costs nothing and works today. It rests on you knowing your own availability at the moment you write. This is the one that turns eight into two, and you can do it with no tool at all.
You publish your availability and let people pick. A booking page moves the negotiation out of the mailbox altogether. They see times you’re genuinely free and choose one. It’s the strongest version of deciding in the first message, because the decision mechanism travels with the message. It also carries a social cost that varies a great deal with who’s receiving it, and booking links is where that judgment gets made properly.
You delegate the thread. To a person, or to software that runs the correspondence for you. That’s what Calendar.help was, and it’s what a meeting scheduler working inside your mailbox is trying to be. The traffic stays roughly the same size. You stop being the one holding it.
Only the first of those is free. The other two hand the state-carrying to somebody or something else, and that’s the part that was expensive.
When somebody still has to arrange it by hand
Calendar.help was built by a competent team with a real budget, and it ran for eighteen months. Here’s the honest headline from the field study. Of the requests it received, 39% completed entirely inside its automated and structured workflows. The remaining 61% needed a human being to step in somewhere before the meeting was booked.
The reasons they recorded are worth reading.
- An attendee replied in a way the workflow didn’t expect, or replied more than once: 32%.
- None of the proposed times worked for everybody: 27%.
- The system timed out waiting for somebody to answer at all: 26%.
- The organizer’s calendar couldn’t be read: 7%.
Every one of those is a moment where a judgment is owed. If your three times work for nobody, somebody has to decide what gives: the week, the attendee list, the length of the meeting, whether it needs to be a meeting. If an invitee has gone quiet, somebody decides whether to nudge, wait or telephone. If a reply says “Thursday works but can we make it 45 minutes and can Sarah join?”, that’s three decisions arriving in one sentence.
The Togedule authors reach the same conclusion eight years later, with far better language models available. They give the reason: “there is yet no tool that fully automates the whole scheduling process since it is often difficult for agents to understand all the nuances and complexities of what people want”. Their more specific version will hold for a long while yet. “Online calendars may lack comprehensive information, such as unrecorded appointments or undisclosed preferences, necessitating human participation to finalize the meeting time.” Your calendar holds your meetings. It doesn’t hold the rule that client calls start after ten on a Monday, or the fact that this particular prospect gets the good slot.
So here’s the target. The ordinary case costs you nothing, and the awkward case arrives already worked out. Calendar.help measured that gap too. A request handled inside the workflow took 2.6 minutes of work. One needing a person took 19.3 minutes, roughly seven times as much. The seven-fold cases are the ones with a decision in them. Being handed those, with the constraints gathered and the options laid out, is the good outcome. It’s what a competent assistant does, and it’s what you’d want from a person.
What collapsing the chain does not do
A slow correspondent stays slow. If somebody takes three days to answer their mail, they’ll take three days to answer a well-formed proposal. What you’ve removed is the two further three-day waits behind it.
The meeting still has to be worth having. A proposal that lands cleanly can book something that should have been four sentences of email. The Doodle survey found professionals spending around two hours a week in meetings they considered pointless, and that’s a separate problem from scheduling.
A change of mind reopens it. An agreed time is a decision with a short shelf life. The messages you saved arranging it can all come back when it moves. That’s a different job with its own repair, covered in moving a meeting and, from the other side, when they ask to move.
The right form depends on the recipient. For a prospect deciding whether to work with you, three named times read as attentive. For somebody who has just been referred to you by a client, a bare link can read as though their time is the cheaper of the two. Same mechanism, different room.
How Point handles the back and forth
Point is a full email client. The thread and the calendar sit on one surface, so there’s nothing to reconcile by hand.
When a meeting needs arranging, you say so on the thread in plain words. Point checks your calendars and reconciles them. Point proposes times you’re actually free, so the first message out already carries a decision. From there Point runs the back and forth. The replies come to Point, and you come in when there’s something to settle. Once a time is agreed, you approve it. The invitation goes out with everyone on it, written to your real calendar. Point works across time zones. Point catches a request to move something even when it’s buried three paragraphs into a reply about something else.
If you’d rather people booked you directly, Point publishes a page showing times you’re genuinely free. A client picks a slot, and neither of you writes a message.
Scheduling has its own autonomy setting, separate from everything else Point does. The default is review. The times Point proposes and the invitation Point writes come to you first, and you raise the setting when you’ve watched a few threads run. At the top of the dial, Point handles the correspondence outright. Point records each step in order as the thread runs, and undo works from that record. An invitation already sitting in somebody else’s calendar gets withdrawn rather than erased, which is the ordinary limit. The benefits page covers what Point does across the rest of your mailbox.
Common questions
How many emails does it take to schedule a meeting?
A little over eight, on the only large public count of it. A Microsoft Research deployment arranged 1,894 meetings for 178 people in 2016 and handled 15,659 emails doing so. Write out the ordinary version by hand and you land in the same place. Two of those eight carry a decision. The other six exist because the opening message asked when somebody was free.
What is the fastest way to schedule a meeting without going back and forth?
Put the decision in the first message. Offer three specific times you’ve already checked against your calendar, and say the invitation will follow. Then the only reply needed is a choice. The gain here is structural. An open question can only produce information, so it costs three round trips before anything is agreed. A proposal costs one.
Should I propose times or send a booking link?
Both put the decision in the first message, which is the part that matters. A link does it more completely, because the calendar check and the confirmation travel with it. What differs is what the recipient reads into it. That varies with who they are and how the introduction happened, and it’s a real judgment rather than a preference.
Can a meeting scheduler work inside Gmail rather than as another app?
It has to, if the goal is to remove messages. Scheduling is a conversation. A tool that lives beside the conversation saves you the step of copying times out of one window and into another. It’s also the only place you’ll see the constraint sitting in paragraph three of somebody’s reply. A scheduler on a separate site can still publish your availability. Reading the thread takes a tool that sits in it.
Why do I still end up arranging some meetings myself?
Because roughly six requests in ten hold something a workflow can’t decide, and that’s the ordinary rate. In the Calendar.help field study, 39% completed entirely inside the automated workflows. The other 61% needed a person somewhere along the way. Usually an attendee replied unexpectedly, or the offered times worked for nobody, or somebody never answered. Those are decisions rather than defects, and the work reaches you at the point where your judgment is the missing piece.
Does this remove the eight messages or just move them?
Mostly it moves them. When a booking link or an assistant takes the thread, the correspondence still happens. It stops being yours to hold. The Calendar.help team designed for exactly that, writing that although their assistant sent many emails per meeting, people “only see a small slice of the total communication”. One version genuinely removes messages: a proposal that leaves nothing to negotiate.
The short version
Arranging a meeting by email costs about eight messages and a few days, and the cost sits in the elapsed time. Four round trips at half a working day each spread a two-minute task across a week, and you rebuild the thread’s state in your head every time it comes back. Six of those eight messages exist because the opening one asked a question. Replace it with an offer of three real times, drawn from a calendar you’ve actually checked, and say the invitation will follow. The ordinary case ends in two.
The rest is deciding who carries the messages you kept, and accepting that six requests in ten will still hold something with a judgment in it. Being handed those with the work already done is the goal. Which meetings turn awkward depends on the work. A first call with a prospect for a consultancy runs differently from a recurring session for a coaching practice, and the trades Point is built for each have their own version of it.