Skip to content
Use case

Taking 1:1 requests through a booking link

Publish the hours you accept and people book a slot themselves. No back-and-forth, and no account needed on their side.

For
People who regularly take 1:1 requests
Expected outcome
Remove the back-and-forth by letting people pick a slot themselves.

The slot is gone by the time they reply

"How does next week look?" "Tuesday afternoon would work." "Sorry, that has just been taken." Two or three rounds of that and the slot you offered is genuinely gone. It is a familiar shape when 1:1 requests are handled one message at a time.

Where the other person keeps changing, proposing candidates each time is the wrong mechanism.

Taking bookings through a page

You publish a booking type: the length, the timezone, the days and hours you accept, and any buffer either side.

With a calendar connected, times you are already busy drop out of the options, so double bookings do not happen.

The other person opens the URL, picks from the open slots, enters a name and an email address, and it is done. They do not need an account, and you do not propose anything.

What arrives afterwards

You and the person who booked both receive the confirmed details with a calendar file (.ics) attached, so they can add it to their own calendar in one step.

Reminders arrive 24 hours and 1 hour before the start. Anything already past at the moment of confirmation is skipped.

These arrive whether or not a calendar or meeting tool is connected.

If you want an automatic meeting URL

With a meeting tool connected, a meeting URL is created as the booking lands and included in the notification.

If you choose the automatic meeting URL while nothing is connected, the booking still lands but no confirmation email is sent. For in-person or phone conversations, set the meeting method to none.

When several people share the duty

Use a group booking link. You choose whether every host must attend or whether any one of them is enough.

Back to the list