It feels like the polite, low-effort thing to say. “Just send me your availability and I'll get something on the calendar.” One sentence, zero friction, problem delegated. Except the problem didn't go away — it just moved to the other person's desk, picked up interest, and is about to bounce back to yours.
That single line kicks off one of the most reliably wasteful rituals in professional life: two busy people manually negotiating a 30-minute slot over the course of three days and seven emails. It looks free. It is not free. It is one of the quietest, most recurring taxes on your week.
Here's what it actually costs — and how to stop paying it.
The most expensive sentence in your inbox.
On the surface, “just send me your availability” is a generous offer. You're saying I'll work around you. But you've also just asked the other person to do the single hardest part of scheduling: turn a living, changing calendar into a static list of times, in writing, in a format you can act on before any of them expire.
So they open their calendar. They squint at next week. They mentally subtract the meetings that haven't been declined yet, the lunch they're protecting, the focus block they hope survives. They type out four options. They guess at your timezone. They send it.
The hidden tax, line by line.
The cost isn't one big number; it's a dozen small ones that nobody bills you for. Add them up and the “quick” meeting was the most expensive part of the meeting.
1. The context-switch tax.
Reading the email, opening the calendar, decoding the proposed times, comparing them to yours, and replying is a 6–8 minute interruption that lands mid-task. The 30-minute meeting now has a 30-minute coordination overhead — split into tiny, momentum-killing fragments across both people's days.
2. The stale-data tax.
Availability emailed on Monday is a forecast, not a fact. By Wednesday two of the four slots have meetings on them. Now you're replying “ah, those don't work anymore, can you send some new ones?” — and the whole loop restarts from the top.
3. The timezone tax.
“Thursday at 2” is not a time. It's a riddle. One of you is going to do mental arithmetic, get it slightly wrong, and either show up an hour early or watch the other person no-show because the invite landed in the wrong slot.
Anatomy of a doomed thread.
You've lived this thread. It always rhymes. It starts with optimism and ends with a calendar invite sent out of sheer exhaustion.
Nobody decides to spend three days booking a 30-minute call. It happens one reasonable reply at a time — and every reply feels too small to be the problem.
Why a booking link only half-fixes it.
The obvious upgrade is a scheduling link: “grab a time that works for you.” It genuinely helps — it kills the stale-data and timezone taxes because the other person picks from your live calendar in their timezone. But it quietly creates new costs, and it outsources the awkwardness rather than removing it.
- You ask a person to do the work of an API.
- Times are stale the moment they’re typed.
- Timezones are a manual, error-prone translation.
- Every miss restarts the whole thread.
- Days of elapsed time for a 30-minute call.
- They pick from your live calendar — no stale slots.
- Timezones resolve automatically to the booker.
- No back-and-forth thread to maintain.
- But: it makes the other person do the choosing.
- And: a raw link can read as “book around me.”
A link solves the mechanics. It doesn't solve the relationship: you've handed someone a grid of empty rectangles and asked them to navigate your constraints alone. The best slot for both of you — the one that respects your focus time, their timezone, and the priority of the relationship — is still nobody's job to find.
What a scheduling agent does differently.
The real fix isn't a static list or a bare link. It's having something that can read both calendars, understand the context, and propose the actual best time — the way a great executive assistant would, without anyone having to ask for “availability” at all.
That's the difference between asking for availability and resolving a meeting. One is a request that creates work. The other is an answer that ends it.
It reads context, not just open time.
An open slot isn't the same as a good slot. A scheduling agent can weigh who you're meeting, how long the meeting should be, whether to protect a buffer, and which of your calendars actually governs the time — instead of treating every white rectangle as fair game.
It defends what the link would expose.
A raw booking link will happily let someone drop a call into the one hour you were saving for deep work. An agent that understands your rules proposes around your protected time by default — so saving the other person effort doesn't cost you your week.
A 4-step way to never send that line again.
You don't need to overhaul anything to stop paying the tax. Four changes, in order of impact.
Stop trading time to save time.
“Just send me your availability” is a trade that always loses. You spend real, fragmented, days-long effort to avoid the small effort of setting up a better mechanism once. The math has never worked — it just hides the bill across enough small emails that nobody adds it up.
Add it up. Then make it someone's job — ideally not a person's. The next time you want to meet, the most professional thing you can do is make the other person's part take one click, in their timezone, against a calendar that's actually true. That's not laziness. That's respect for both of your weeks.
Caliyo turns “send me your availability” into a single shared link backed by an AI scheduling agent: it reads your real calendar, defends your protected time, proposes the best mutual slot in the booker's timezone, and confirms it the moment they say yes — no thread, no stale slots, no timezone math. If you want to see what replacing that sentence feels like, start a free trial.