Every booking starts with a moment of intent. A customer picks a slot, hits confirm, and in that half-second they’ve told you what they want, when they want it, and that right now, they’re ready.
However many brands miss it. Not because they don’t care, but because the systems sitting behind their booking page were never built to catch it. The confirmation happens, the calendar updates, and then… nothing reaches the CRM for another hour. Or it reaches the CRM but skips the loyalty platform. Or it reaches both, minus the one field the marketing team actually needed, so someone has to go back and make three more API calls just to fill in the gaps.
That’s the gap between “customer booked” and “business acted on it”. It’s where the opportunity leaks out. Webhooks V2 was built to close it, and the event we’re most excited about is booking participant created, which is what we are calling Booked Intent®.
What Booked Intent® means
Booking participant created fires the instant a customer commits to a slot. Not on a delay, not in a nightly batch, and not after some queue clears - the moment it happens. And it doesn’t arrive as a bare notification telling you to go fetch the details yourself. It shows up enriched, carrying the customer, the service, the time, the location, the resource, and the works, already in one payload.
That distinction matters more than it sounds. Under Webhooks V1, integration teams told us they were making three to five follow-up API calls per event just to reconstruct what actually happened. The Booked Intent® event carries that context on arrival, which means the businesses on the other end can act on the booking while it’s still warm, not after it’s gone cold waiting on round-trip API calls.
Why the moment matters more than the record
A booking confirmation is useful. Booked Intent®, caught the second it happens, is a different kind of asset. It’s a live signal you can build a response around.
A retail chain can trigger a personalised prep email the second a fitting appointment is booked, not 20 minutes later once the customer’s already moved on to browsing somewhere else.
But that doesn’t work if the event shows up late, thin, or not at all. Which, under Webhooks V1, was happening often enough to be a problem we needed to fix.
The reliability work behind the headline feature
Booked Intent® is the story we’re leading with, but it only works because of what’s underneath it. Webhooks V2 was rebuilt for delivery you don’t have to babysit:
Every delivery attempt is logged, so if a payload doesn’t land, you can see the timestamp, the response code, and the failure reason without opening a support ticket. Failed deliveries retry automatically with exponential backoff, so a 20-minute outage on your endpoint no longer means 20 minutes of bookings vanish into the void. And the event catalogue itself is bigger: alongside booking participant created, V2 adds booking participant updated, booking participant cancelled, and invoice paid, so the workflows that depend on rescheduling, cancellations, and billing finally have something to hook into.
You can also route with more precision now. A global endpoint can catch everything, or specific event types can go to specific destinations, so your billing system only hears about invoices and your CRM only hears about bookings. If you’re managing webhooks across multiple accounts, the new Enterprise Management Console lets you configure and monitor all of it centrally, without logging into each account separately.
And if you’re not ready to switch over, you don’t have to. Webhooks V1 and V2 can run side-by-side while you migrate on your own schedule.
What this means if you’re already an Appointedd customer
If your team has ever asked “did that webhook actually fire?” and had no good way to answer, that’s the exact gap this closes. Your account manager can walk you through turning on booking participant created first, since it’s the fastest way to see the value: point it at your CRM or marketing platform and watch booking intent arrive in real time instead of on a lag.
If you’re evaluating Appointedd and integration reliability is part of that evaluation, this is worth knowing: the way we approached this rebuild, full audit trails, automatic retries, structured logging, is the same standard we’d want applied to any system a business depends on. Booking software that can’t reliably tell your other systems what’s happening isn’t infrastructure, it’s a liability waiting to surface at the worst possible time. Webhooks V2 is us closing that gap.
Try it
Webhooks V2 is live now via the Enterprise Management Console. Click here to try it.
Start with booking participant created if you want to see the fastest win, then layer in the others as your workflows need them. Full setup details are in our developer documentation and support article.
Have you got a webhook use case we haven’t thought of, or an event type V2 is still missing? Tell us. Better yet, join the Beta Club, and get first access to our upcoming releases.
.png)
