Booking

Booking inside the thread.
No 'click my link.'

Cal.diy is built into every reply. When a prospect says yes, they pick a time without ever leaving the conversation — round-robin for team practices, time-zone aware, and qualified before the meeting lands on your calendar.

See it on this page vs. send-a-link

Cal.diy embed Round-robin Time-zone aware Google & Outlook sync

An open leather appointment book with a single date circled in deep ink, fountain pen resting beside it — The page where a 'yes' becomes a kept appointment.

The meta-demonstration

This page is the demo. Pick a time below.

No new tab, no link to remember, no “does this work for you?” back-and-forth. The calendar you’re about to use is the exact embed your prospects see when they reply yes inside a thread.

Calendar pending setup

The booking widget loads here once PUBLIC_BOOKING_PUBLIC_ID and PUBLIC_BOOKING_BASE_URL are set in .env. In the meantime, write to us directly.

Email us instead

Two paths after 'yes'

Send a link, hope.
Or pick a time, done.

The friction isn’t the calendar. It’s the handoff — the leap from a warm thread to a stranger’s booking page. We removed the leap.

The link approach

Send link → hope

Prospect leaves the conversation to a third-party page.
They see a brand they don’t recognize.
They get distracted, close the tab, mean to come back.
You follow up three days later. Maybe.

The in-thread approach

Pick a time → done

Calendar renders inline as the next message in the thread.
Prospect sees your name, your context, your warmth.
One tap on a slot. Confirmation lands in both inboxes.
You go back to your day with a meeting on the books.

For team practices

Round-robin, without the awkward handoff.

Two-advisor team. Five-advisor practice. Cal.diy rotates the next available slot across whoever is on call — weighted by current load, holiday calendars, and which advisor introduced the prospect on LinkedIn.

Calendar pulls from each advisor’s real availability, not a static rota.
If the prospect already met someone on the team, the request routes back to that advisor.
Out-of-office? Their slots vanish from the pool until they’re back.

Time-zone intelligence

“Tuesday at 10:30” means their Tuesday at 10:30.

The embed reads the prospect’s browser zone, translates your availability into their morning, and ships the calendar invite with both timezones written into the body. No mental math, no “wait, is that EST or PST?”

You set your hours once. Cal.diy handles the math for every visitor — including the prospect who flew to Zurich for the week and forgot to update their laptop.

EST

10:30 AM

New York

GMT

3:30 PM

London

SGT

11:30 PM

Singapore

A small brass desk clock showing 10:30 in soft window light

Before the meeting lands

Qualifier questions, buffers, then the slot.

A “yes” in a thread is the start, not the end. Three small frictions, applied in the right order, mean the meetings on your calendar are the ones worth taking.

01 · Qualifiers

Three short questions before they pick a slot.

Asset range, current advisor situation, why they reached out. Prospects who don’t fit your book see a polite "we’ll be in touch" instead of a calendar.

"Roughly how much are we discussing today?"

02 · Buffers

Fifteen minutes of breathing room around every meeting.

Your slots show as 10:30 to your prospect, 10:15–11:00 to your calendar. No back-to-back wall, no joining late from the parking lot.

15-min before · 15-min after

03 · Reminders

A note the night before, a nudge an hour out.

Both go through your domain, signed in your name. The prospect sees you, not Cal.diy — right up until the meeting starts.

T−24h email · T−1h SMS

Questions advisors ask first

Booking, in seven plain answers.

No. The Cal.diy embed loads inside the message thread itself. They see your available slots without ever clicking out, and the confirmation lands as the next message in the same conversation.