Dana counted the eleven messages the following Sunday, mostly out of irritation. Three of them held a time. The other eight were the two of them passing one fact at a time, at roughly half a day per fact, about a week that had stood still since Wednesday.
Priya was in Chicago on the Tuesday. Priya wanted ten o’clock at the earliest. Priya’s work calendar was managed by somebody at her company for the internal half of it, and was her own the rest of the time. All three were true the moment Dana sent her first offer, and Priya would have said any of them for the asking. They came back one per reply instead, each one arriving the next morning.
That’s the thing worth taking out of it. A booking chain is a slow way of finding out what somebody’s week looks like. Its length is set by how much you learn per message. Three named times, checked against your own calendar, is the move that collapses the ordinary version of this. The message-by-message count behind it is scheduling without the email chain. It’s a good move, and Dana made it. The one thing it leaves out is a question.
Every reply carried one new fact
An offer of three times gets answered two ways. One of them ends the arranging. The other is a no, and it arrives empty, so your second offer rests on exactly the information you had for the first.
That’s the whole mechanism. It explains why a chain that starts well can still run six days. Dana’s three times were real, drawn from a calendar she had actually looked at. They were wrong for reasons that only Priya’s week held. So the second offer was another guess. The third was a guess made against one fact. By the time Dana knew enough to propose something that would land, it was the following Monday.
The repair is one clause, and it goes in the first message. Ask for the constraint in the offer itself. Then a no comes back with the reason attached.
Thursday at 8, or Friday at 5:30, both Mountain time, thirty minutes. If neither of those works, tell me which end of the day is easiest for you and I’ll fit around it.
That’s an ordinary sentence to write. It costs you one line and it changes the worst case. Without it, a no is the second message of eleven. With it, a no is the second message of three. Their reply now carries the one thing you were missing, so your next message is a time rather than another attempt.
A booking page has the same gap in it, for the same reason, and that’s worth knowing before you decide it solves the problem. A page is a very good closed offer. The calendar check and the confirmation travel with it. It re-asks the question at the instant somebody looks, rather than reporting what was true when you typed. For an inquiry that came to you, it carries no social cost at all. Whether a link reads as helpful or high-handed is settled entirely by who approached whom, and that judgment is worked through in booking links that show real availability. For a stranger who wrote to you first, you’re on the clean side of it.
A page hears a time. It can’t hear a constraint. If none of the times on it suit, the person closes the tab and writes you an ordinary email. Now you’re back where Dana was, a day later, and they’ve privately decided this is harder than they thought. So the link belongs under the sentence, not instead of it.
The hours a working client can actually give you
Here’s the part that’s specific to coaching. It’s the reason first calls are the hardest meeting in the practice to book.
The person buying from you is employed. They’re at a desk, probably near other people. The conversation they want with you is about whether they’re any good at the job those people can watch them do. That call happens somewhere private. An open-plan floor at two on a Tuesday is the wrong room. So is a meeting room with a glass wall, because somebody walks past.
So the ordinary business day is about the worst inventory you can offer this particular buyer. That’s the nine to five your calendar is mostly made of, and the hours a booking page will cheerfully publish. Their real availability sits at the edges. Before the office fills up, the middle of lunch, or after six. Quite often from a parked car, a spare room at home, or a walk around the block. Priya’s ten o’clock rule was about the hour the floor got busy.
Two practical things follow.
Hold a standing pair of slots for first calls, at the edges. Two thirty-minute blocks a week, one early and one late, kept permanently open for people you have yet to meet. It costs you two edges of two days. It buys you three things at once. An answer you can give in twenty seconds. An answer that’s always right. An offer aimed at hours the other person can actually use. You also stay responsive with the rest of your week still yours, and opening all of it to strangers is the trade most people think they’re being asked to make.
Say the call works from anywhere. One short line, and it answers an objection that almost nobody will raise out loud. “It works fine from a car or a walk if that is easier” does more for a 7:45 slot than any amount of flexibility further down the message. What stands between them and that slot is usually the room rather than the hour. They’re wondering where they’re supposed to be sitting.
Thirty minutes is doing quiet work here too, and it’s the length everybody picks without thinking about why. Half an hour fits inside a lunch break and inside a commute. An hour spills out of both, and it has to be explained to somebody.
Whether the times you publish are honest is a different question. That one is about your calendar rather than theirs, and it has its own well-known failure modes. Things agreed on the phone and never entered. Entries marked free that let a meeting land on top. The gap between an empty two hours and two hours you could actually give away. Those are covered properly in the same piece on booking links. If you keep client hours in one calendar and the rest of your life in another, that reconciliation is the first bottleneck to close, and it is two calendars.
What the invitation says on a screen at their office
Picking a time is the middle of the booking. It finishes when an event exists, and the event lands somewhere you don’t control.
Google Workspace administrators choose one of three internal sharing levels for everybody’s calendar. The options, in Google’s own words, are no sharing, “Only free/busy information (hide event details)”, and “Share all information”, the last of which it describes as: “All information is public unless users change their own settings. Users can also make individual events private.” Google adds that whichever level the organization sets “automatically apply if a user doesn’t customize their own calendar settings” (checked September 6, 2026). Microsoft 365 has an equivalent set of controls. Your new client usually knows as much about their employer’s choice as you do, which is to say very little.
So an event titled “Coaching call: Dana Reyes” can be a sentence about somebody’s career. Their manager can read it. You published it, on their behalf, and the two of you have yet to discuss it. Nobody sets out to do this. The invitation gets written by the person with nothing to hide.
Two habits cover it, and both cost seconds.
Ask where the invitation should go, inside the message that offers the time. One line, in the message you were already sending. Something like: “I’ll send the invitation to this address unless you’d rather I used a personal one.” It reads as consideration. It costs a clause rather than a round trip. For a good number of people, it’s a relief.
Title it plainly and let them widen it. “Intro call” and your first name will do. If the client would rather it said something specific, they’ll change it on their copy or tell you. The general case is writing a calendar invitation that arrives complete, which covers what an invitation has to carry so nobody writes back asking, and what a title is doing when it’s read out of context weeks later. The point here is narrower. For this one meeting, the title is a disclosure, and the default should be the quiet one.
There’s a version of this you’ll meet within a year, and it’s the one Priya had. The client’s calendar is run by an assistant for the internal half of the week. That assistant holds constraints your page can’t see and can’t pick from, so a link is the wrong instrument the moment one appears in the thread. When somebody says their calendar is managed, stop offering and start asking who to write to.
The message that ends it, written out
Everything above fits in five sentences. Part one of this series is a request for a call, and the day it lands, and it covers what the first reply to a stranger has to carry and what it must leave out. The short version is that you name the thing they told you, say yes to a call, and give them a way to take a time. What follows is the scheduling half of it, drawn out.
Four months into a director role is exactly the stretch I do most of my work in, and yes, I have room.
Thirty minutes to start. Thursday at 8am or Friday at 5:30pm, both Mountain time, and it works fine from a car or a walk if that is easier. If neither suits, tell me which end of the day is usually easiest for you and I’ll work around it. My calendar is also here if you’d rather pick your own slot.
I’ll send the invitation to this address unless a personal one is better.
That message carries four things. A decision. A request for the missing information. A fallback that runs without you. And the one question about the invitation. Your rates, your method, your certification and an intake form come later. This message is for getting a time on the calendar.
When the constraint comes back, the second message is shorter than the first, and it goes out the same hour.
Chicago on Tuesdays is easy to work with. Wednesday at 8am or Thursday at 5:30pm then, same length, and the invitation is on its way for whichever you take.
Two things about that second message. It offers rather than asks, because you now know enough to offer. And it says the invitation follows, so the acceptance is the last message rather than the second to last. Keep both of them on the one thread, under the subject line the request arrived under, for the reason part one gives. The record of how somebody came to you is the start of their file.
When one more exchange is the right price
Some of this is worth leaving long, and it’s worth being clear about which parts.
When the answer is no. A request that deserves a short, kind no skips all of this machinery. Turning down an unsuitable inquiry quickly is a different job with a different shape. Part one covers which requests those are.
When their calendar belongs to somebody else. The negotiation is between you and an assistant. It takes two or three messages, and those messages are the correct cost of getting it right. Trying to compress it with a link is the one move guaranteed to add a day.
When they ask to talk now. Occasionally a reply comes back saying they’re free this afternoon. Take it. A call that happens today beats a better-organized call next week by a wide margin.
When the thing being arranged is a longer commitment. A ninety-minute session. A package of six booked in one go. A conversation you need them to have read something before. Those have a decision inside them, and a decision needs more than a slot.
And one honest note about the whole subject. A discovery call that took six days to arrange still lands a client. Priya booked, and Priya may well have been a good one. The six days cost you something probabilistic, paid on the requests you never hear about again rather than on the ones you can point at. That’s why it stays invisible for years, and it’s also why the fix has to be structural rather than a matter of trying harder. You’re going to forget to ask for the constraint. The message has to have the clause in it already.
Where the arranging can happen without you
The gap Dana was paying for sits between a reply arriving and the next offer going out. Every one of those gaps was a night. That’s the part Point takes.
Say on the thread that a call needs arranging. Point checks your calendars, reconciles them, and puts real times into the reply. From there Point runs the correspondence rather than handing it back to you. When Priya writes back saying she’s in Chicago, that arrives to Point. The next offer goes out inside the hour instead of the next morning, which is where the six days actually lived. The legs that settle nothing stop reaching you. What reaches you is the point where somebody has to choose. The agreed time comes back for your approval, and approving it sends the invitation and puts the event on your calendar. If you’d rather people booked themselves, Point can publish a page from times that fit across all your calendars. The two standing slots you keep for first calls become takeable without a message in either direction. Email for business and executive coaches is the practice-shaped version of this, and everything Point does is the flat inventory.
Three limits, because they’re what a careful reader wants next.
Point learns that Priya is in Chicago on Tuesday when somebody says so, and so does everything else. What changes is the eleven hours between her saying it and anyone acting on it.
Scheduling carries its own autonomy setting, held separately from everything else Point does. It starts on review, so you read everything that goes to a client before it goes. You raise it after watching a handful of these threads settle. Set it to the top and the whole exchange is handled without you seeing it. The autonomy dial sets out what each position on it actually means.
And undo works from an ordered record of what Point did, with one limit worth saying in the same breath. A slot your client already accepted can be canceled. The fact that they were once offered it stands. Which is the same reason the invitation’s title is worth getting right the first time.
Three on the grid in April
The next one was a man named Owen, in April. He had heard about Dana from a former client, and he wrote on a Wednesday evening.
Dana answered in twenty minutes. Two edge-of-day times. The line about the car. The question about which address. And the sentence asking which end of the day was easiest if neither worked. Owen took Thursday at 7:45 and asked whether he could send over a couple of things beforehand. The whole thing ran three messages, and it was done before Dana went to bed.
She looked at the month afterward and counted three discovery calls sitting on the grid, each one booked inside a day, and let herself think that the front of the practice was finally solved.
Two of them happened.