Notifications
Who hears about a booking, and how.
By default, attendees and hosts get an email when a booking's confirmed, moved or cancelled, with a calendar invitation, and attendees get a reminder a day before. Webhooks always fire, whatever's on here.
Turn each one on or off in your settings, or per event type:
await ...({
: "appointments@example.com",
: "Acme Health",
: {
: { : false },
: { : true, : true },
},
});The events are confirmed, pending_approval, rescheduled, cancelled, declined and reminder. To
send everything yourself, turn them all off and use webhooks.
Emails come from email_from, on one of your verified domains. Without one, they come from coss.com on
your behalf. They use fixed templates with your event type's title and your brand name, and the only link
in them is the attendee's manage link. Titles, host names and brand names can't contain links, and in live
environments they're screened for abuse when you set them, rather than each email being screened.
An SMS reminder needs sms_from, one of your approved numbers, and the attendee's phone. Getting their
consent is yours to do, and a STOP is always honored.
Meeting links
An event type's locations say where it happens. google_meet and microsoft_teams create a link with the
calendar event, so they need a connected calendar from that provider: the confirmation waits briefly for it,
and it then appears on the booking with scheduling.booking.location_ready. For your own video vendor, use
link and set it after the confirmed webhook:
await ...(, {
: { : "link", : "https://video.example.com/room/abc" },
});On This Page