Cal.com + AI for Conflict-Aware Auto-Rescheduling

A hot lead hits your Cal.com page and picks a Wednesday 2 PM slot. They get the confirmation. You see it on your calendar. Then you realize you already had something at 2:15 you forgot to block.

You email them. They miss the email. You miss them. Two days of back-and-forth, momentum dies, lead disappears.

This pattern prevents that scenario.

The setup

Cal.com supports webhooks on every booking event. We use the `BOOKING_CREATED` webhook plus a daily cron to catch: - Bookings that conflict with manually-added calendar events Cal.com didn't know about - Bookings on days the booker doesn't realize are unavailable for actual deep-work reasons - Bookings during travel windows

When a conflict is detected, the system doesn't reject the booking. It proposes alternatives via the booker's preferred channel.

The pipeline

Step 1: BOOKING_CREATED webhook fires. n8n Webhook trigger receives it.

Step 2: Re-check the actual calendar. Hit Google Calendar API (or whatever calendar you use). Pull events for the booking window plus a 30-min buffer on either side.

Step 3: Conflict detection. If any actual calendar event overlaps with the new booking, flag.

If no conflict, the pipeline ends and the booking stands.

Step 4: Claude generates the alternative proposal.

``` The booker just scheduled a meeting at {time} for {duration} but there's a conflict with {conflicting_event}.

Look at the rest of the week and propose 3 alternative times that: - Are at least 2 hours from any existing meeting - Are within typical business hours - Avoid back-to-back stacks - Match the booker's likely time zone preference based on their email domain

Generate a warm, brief email that: - Apologizes lightly - Offers the 3 alternatives - Has clickable booking links (Cal.com one-click) - Closes with "or pick any other time at {cal_link}"

Voice: peer-to-peer, not transactional. ```

Step 5: Reschedule the original. Cal.com API call to cancel the conflicting booking with a polite reason.

Step 6: Send the alternatives email. Email the booker via Resend or Gmail API.

Step 7: Slack notification. Ping yourself in Slack so you know a reschedule happened.

The clickable booking links

Cal.com supports URL parameters that pre-select a time slot. Build them like:

``` https://cal.com/your-handle/intro?startDate=2026-05-22T14:00:00Z&duration=30 ```

The booker clicks, gets a one-click confirmation. No going back to the calendar.

What broke

Time-zone misreads. Some bookings come in with UTC timestamps, some with the booker's local time. We standardized everything to UTC internally with an explicit conversion at presentation.

Cancellation emails from Cal.com confused bookers. Cal.com sends its own cancellation email when you cancel via API. Combined with our reschedule email, the booker got two emails. We disabled the default Cal.com cancellation email for this specific event type and only sent our combined version.

The "no good alternatives" edge case. Sometimes the next 3 days have no good 30-min slots. We added a fallback: if the system can't find 3 alternatives that meet the criteria, it proposes 2 alternatives and a "let's find another week" option with a different cal link to a wider availability calendar.

What it caught

In 4 months at a consulting practice:

• -11 conflicts proactively rescheduled before either party noticed the original was a problem
• -Estimated 8 of those would have resulted in a missed meeting or a chaotic last-minute Zoom shuffle
• -Zero complaints from rescheduled bookers (we asked in a follow-up)

The rescheduled-with-alternatives pattern is materially smoother than the discover-conflict-later pattern.

What this isn't

Not a substitute for keeping your calendar clean. If you don't block focus time, recurring meetings, and personal stuff on your shared calendar, this system can't see those conflicts.

Not a replacement for Cal.com's own buffer-time settings. Use those for the routine spacing rules. This system handles the edge cases Cal.com can't.

What to build first

If you don't have Cal.com booking conflicts now, you don't need this. Most solo practitioners hit this once a month or less.

If you DO have this problem (people booking on top of unsynced events, travel windows, deep-work blocks), the pipeline pays for itself the first time it saves a hot lead.

Total build: 45-60 minutes. Lifetime savings: every "shit, I have to email them" moment that turns into a chaotic reschedule.