Send slots, not questions
Bookable link: client chooses type and slot, submits request. View-only link: partner sees open windows without self-booking.
Best practices
Replace "what works for you?" with a synced Awase link — and narrow choices with booking types.
The email chain persists because both sides lack information to commit. A link with real slots — or a view-only page with real open windows — answers the question before it is asked.
Real-world example
A recruiter stops proposing three times per candidate. They send a View only Awase link filtered to "Interviews" tagged calendars for internal coordination, and a Bookable "Screening call (20 min)" link for candidates. Candidates request; recruiting ops approves. No more "actually that slot filled" after three replies.
Bookable link: client chooses type and slot, submits request. View-only link: partner sees open windows without self-booking.
"Any time" links create bad bookings. Separate types — 15-min screen vs 45-min deep dive — with their own weekly windows reduce mismatches.
When a Google meeting cancels, Awase recomputes open slots. Polls and screenshots do not.
In Awase, no — requests are Pending until approved. That prevents wrong-fit bookings from auto-confirming.
Reading about private availability sharing is one thing. Connecting your Google calendars and sending a test link is the part that usually clicks.
Start free