Cancellations, without the awkward email

Every scheduling tool nails the happy path: two people agree on a time, a calendar invite goes out, everyone shows up. The unhappy path — the meeting that needs to not happen — is where most tools quietly hand the problem back to you. Delete the event, remember who was on it, draft the "so sorry, something came up" message, hope they see it before they dial in.

We kept watching customers do this dance manually, and it never got less tedious. So we shipped a first-class way to call a booking off.

One action, both sides handled

Cancelling a booking is now a single action from the Bookings page, and the attendee is notified as part of the same step Cancel a Booking. No separate email, no forgotten follow-up, no ambiguity about whether the other person got the memo. The state of the booking and the communication about that state move together, which is how it should have worked from the start.

This matters more than it sounds. The worst outcome of a cancellation isn't the cancellation itself — it's the attendee showing up to an empty room because the notification lived in a different system than the calendar entry. Coupling the two closes that gap.

Why now

A cancel button is not a moonshot feature, and we're not going to pretend it is. But scheduling products accumulate a lot of almost-there workflows, and this was one of the loudest ones in our feedback. Building it properly — as an atomic action rather than a two-step delete-then-email — was worth doing before layering on anything fancier like rescheduling flows or cancellation reasons. Get the primitive right first.

What's next

With cancel as a real, observable event in the system, a lot of adjacent work gets easier: reschedule links, cancellation policies, attendee-initiated cancels, analytics on which meeting types churn. Those are on the roadmap. For now, if you need to call something off, it's one click from the Bookings page — and your attendee will know before they wonder.