Agreeing a date with a client without six messages
Why finding a slot costs a week, the four mistakes that stretch the exchange, and the only thing that genuinely shortens it.
You offer Tuesday or Thursday. Your client answers the next day that neither works, and suggests "next week instead". You offer Monday, Tuesday, Wednesday. They answer two days later. It is Friday, the date is not booked, and nobody has done anything wrong.
The cost is not the decision, it is the round trip. Choosing a date takes ten seconds; it is the wait between each proposal that takes the week.
The arithmetic nobody does
An e-mail exchange takes between twelve and twenty-four hours to complete one full turn, because you are not in front of your inbox at the same moment. Every rejected proposal therefore costs a whole day, whatever time the reply itself took to write.
Three turns is three days. And three turns is the ordinary case, not the bad day: the first proposal has a one in two chance of missing, and so does the second.
So what is slow is not your client. It is the format.
The four mistakes that stretch the exchange
Offering a single date. It looks decisive and it guarantees one extra turn if it does not work. A single date has only two possible answers, and one of them puts you back at the start.
Offering twelve. The opposite effect and a worse one: a list of twelve slots asks your client to do a comparison, so they set it aside for "when I have a moment". A choice that is too wide does not get settled, it gets postponed.
Between three and five options is where it gets decided in one reading.
Saying your own constraints late. "Whenever suits you this week" is a courtesy that costs: your client picks Friday at six, you reply that no, and you have just lost a turn while appearing to contradict yourself. Say your days and your hours in the first sentence. A constraint announced is a frame; the same constraint revealed afterwards is a refusal.
Letting the date be settled in a thread that settles other things too. The most expensive and the least visible. When the same e-mail covers the slot, the budget and the missing files, the reply waits for all three to be ready. The date had been sorted since the first paragraph.
One decision per thread. Always.
Minimum notice, the rule you learn once
Do not book an appointment for the next morning, even when it is possible.
A slot accepted at four in the afternoon for nine the next morning leaves you no time to prepare, none to travel, and none to absorb the overrun of the appointment before it. You will accept it anyway, because refusing feels awkward, and that is the one you will regret.
Twenty-four hours of minimum notice, announced in advance, settles this without your having to say no even once. The constraint does the refusing for you, and it is aimed at nobody.
What actually shortens it: handing over the choice
The only way to remove the round trip is to stop needing one. Which means giving your client your availability and letting them take a slot, rather than proposing one and waiting.
That changes three things at once.
- The exchange goes from three turns to zero. There is no longer a proposal to approve, there is a choice to make.
- The slot is taken the moment they click, so you no longer hold two dates "pending confirmation" in your head while offering others to somebody else.
- Your constraints live in the frame, not in the conversation. Your client only sees what is possible, so they cannot pick what you would have refused.
The price is real and worth saying out loud: your tool only knows about the appointments that go through it. If your calendar lives elsewhere, a slot taken over the telephone yesterday is not blocked on its own. That is the one thing to watch, and you watch it by closing the periods you already know are gone.
And writing it where the job lives
A date settled in a mail thread is a date you will go looking for in a mail thread, six weeks later, at the same time as you go looking for the material reference and the domain login.
The appointment belongs to the job, like the brief and the quote. Which means three concrete things: that it is visible without opening your inbox, that it reaches your calendar and your client's, and that an automatic reminder exists the day before. A client who does not turn up is almost always a client who forgot, not a client who backed out.
For what gets decided on a call rather than in writing: a kick-off call or a form, and in which order.
Frequently asked questions
How many dates should you offer a client?
Between three and five. A single one guarantees an extra round trip if it does not suit, and a list of twelve asks for a comparison your client will postpone. Three to five options get settled in one reading.
How do you avoid back and forth when booking an appointment?
By handing over the choice rather than proposing: give your availability and let your client take the slot themselves. The exchange goes from three turns to zero, and the slot is held the moment they take it, so you have no dates pending confirmation to keep in your head.
How much notice should you leave before a client appointment?
Twenty-four hours, announced in advance. A slot accepted for the next morning leaves no time to prepare, to travel, or to absorb an overrun, and it is the one you regret. A constraint announced does the refusing for you.
Should you state your working hours in the first message?
Yes, in the first sentence. "Whenever suits you" costs a full round trip the day your client picks a slot you then refuse, and it makes you look as though you are contradicting yourself. A constraint announced is a frame; the same one revealed afterwards is a refusal.
Where should the date be written once it is agreed?
Where the job lives, not in the mail thread that settled it. A date you find by digging through an inbox is a date you find badly, and it also has to reach both calendars, with a reminder the day before.
Is a client who does not turn up a client who has gone?
Almost never. It is a client who forgot. The automatic reminder the day before removes the large majority of no-shows, and it costs less than one wasted journey.
Kalepio asks these questions for you
You send one link, your client answers once, and you start with everything you need.
Read next
September 4, 2026
Keeping a client in the loop during a project
The update rhythm that stops a client from asking where things stand, without turning your day into emails.
5 minute read
September 4, 2026
Onboarding a new client after they say yes
The first week is where jobs drift, not the last. The four things to send before work starts, the one to refuse, and how to set the tone of the whole job in the first round.
9 minute read
September 4, 2026
A client comes back six months later and wants their files again
The most avoidable forty minutes in this trade, the question that costs more than the missing file, and the three things to decide before it happens.
7 minute read