Invites and reminders
What a booking sends: a calendar invite to the invitee, you and your other accounts, reminders by email, SMS, WhatsApp or Telegram, a reconfirmation, a thank-you, and the no-show button.
When someone books you, Venom Cloud emails a calendar invite to them and to you. When the booking moves or is cancelled, everyone who got the invite gets the update. Reminders, a reconfirmation and a thank-you go out on the channels you pick for each event type. Nothing here needs a setting to turn on: invites go out once a mail provider is connected, and reminders once you add them to an event type.
Invites
Invites go out through the mail provider connected in Support settings (SMTP, Postmark, SendGrid, Mailgun or Resend), from the support address, with your name as the sender.
| Change | Sent | To |
|---|---|---|
| Booked (confirmed), or a pending booking accepted | REQUEST |
the invitee, you, and your accounts set to receive invites |
| Moved | REQUEST with the same UID and SEQUENCE one higher |
everyone who got the first invite |
| Cancelled or declined | CANCEL with SEQUENCE one higher |
everyone who got an invite |
| Pending (manual confirm) | nothing yet |
Mail apps (Gmail, Outlook, Apple Mail) show the invite with Accept and Decline and replace the old version when an update arrives, because the UID stays the same and the sequence goes up (iTIP and iMIP, [R2111] in the research notes).
What each copy holds:
- The invitee's: the title, the time in UTC (their calendar shows it in their zone), where it happens, the description with the manage link (reschedule or cancel), you as the organizer, them as an attendee asked to reply, and an alert 10 minutes before.
- Yours: the same event, with you already marked as accepted and no alert. You don't get a copy when the booking was written into a Google calendar that already shows it.
- Your other accounts: when the event type has
invite_other_accountson, each of your connected accounts with a calendar set to receive invites gets the same copy as yours, except the account the booking was written into and disconnected ones. When that copy later comes back through the account's feed, busy time skips it (it has the booking's UID), so a booking never blocks its own move.
The email is multipart/mixed: a multipart/alternative with the plain text, the HTML and the text/calendar; method=REQUEST (or CANCEL) part, then the same calendar as an invite.ics attachment. Postmark, SendGrid and Resend
get the equivalent through their own APIs; Mailgun gets the full MIME message through its MIME endpoint.
No mail provider
Without a provider nothing is sent. The invite rows are kept as failed with the reason, and both the invitee's manage page and the Bookings page in the app say: "No email provider is connected, so no invite was sent." Connect one in Support settings; then Resend invite on a booking sends it.
Reminders
Add reminders to an event type (the app, or the reminders field in the API and MCP tools). Each entry is one message:
{
"reminders": [
{ "channel": "email", "before_min": 1440 },
{ "channel": "whatsapp", "before_min": 60, "template": "booking_reminder" },
{ "channel": "sms", "before_min": 15, "to": "owner" },
{ "kind": "reconfirm", "channel": "email", "before_min": 2880, "deadline_min": 1440 },
{ "kind": "thank_you", "channel": "email", "after_min": 60, "link": "https://example.com/next-steps" }
]
}| Field | Type | Default | Meaning |
|---|---|---|---|
channel |
email, sms, whatsapp, telegram |
required | how it is sent |
kind |
reminder, reconfirm, thank_you |
reminder |
what it says (below) |
before_min |
1 to 43200 | required, except for a thank-you | minutes before the start |
after_min |
0 to 10080 | 0 | a thank-you only: minutes after the end |
to |
invitee, owner |
invitee |
who gets it (a reconfirm always goes to the invitee) |
template |
text | none | WhatsApp only: the approved template to use |
deadline_min |
1 to 43200, below before_min |
half of before_min |
a reconfirm only: minutes before the start when you are told there was no answer |
link |
https URL | none | a thank-you only: a link to add |
message |
up to 1000 characters | none | a thank-you only: your own text |
An event type has at most 10. A reminder whose time has already passed when the booking is made is left out (book 30 minutes ahead and the 1-hour reminder is not sent). Every message gives the time in the reader's own zone (the invitee's from the booking form, yours from your profile) and, for the invitee, the manage link.
Reminders are queued when the booking is made, moved to the new time when it is rescheduled, and cancelled with the booking. A worker sends what is due every minute. Each message is sent at most once: a row is claimed before sending, and one interrupted mid-send is marked failed rather than sent again.
Channels and fallbacks
SMS, WhatsApp and Telegram go through Comms, so its opt-outs, quiet hours and WhatsApp template rules apply. The invitee's number is the one they gave for a phone call, else their answer to a phone question, else the phone or WhatsApp number on their People record. Yours is your verified phone in Comms. Telegram needs a Telegram chat id on their People record.
| Situation | What happens | Reason kept on the row |
|---|---|---|
WhatsApp with no template |
sent by SMS | WhatsApp reminders need an approved template and none was named |
| Template not approved | sent by SMS | the WhatsApp template isn't approved |
| Comms not set up for the org | sent by email | Comms is not set up |
| No phone number or chat id | sent by email | there's no phone number (or Telegram chat id) for the invitee or you |
| The number has opted out | nothing is sent | the number opted out (STOP) |
| Inside the org's quiet hours | held by Comms, sent when they end | held by the org's quiet hours |
| Email, and no mail provider | nothing is sent, the row fails | no email provider is connected |
The Bookings page shows a banner when invites or reminders cannot go out as configured.
Reconfirmation
A reconfirm asks the invitee "Still on?" with two links: Confirm (opens the manage page with a Confirm button)
and Reschedule. If they have not confirmed by the deadline, you get an email saying so. A booking is never
cancelled for want of an answer.
Thank-you
A thank_you goes after the meeting ends, with your message and link if set. It is not sent when you marked the
booking a no-show.
No-shows
After a booking has started you can mark the invitee as a no-show (Bookings in the app, or
calendar_booking_mark_no_show). That sets the booking's no_show, cancels its pending reminders and thank-you, and
raises the calendar.booking.no_show event (org webhook and in-process, with the same payload as the other
booking events). With rebook: true the invitee also gets a "Sorry we missed you" email with
a new single-use link for the same event type, valid for 14 days.
For builders and agents
| Tool | Console API | Does |
|---|---|---|
calendar_booking_mark_no_show |
POST /api/workspace/calendar/bookings/<id>/no-show |
mark a started booking a no-show; rebook and message optional |
calendar_booking_resend_invite |
POST /api/workspace/calendar/bookings/<id>/resend-invite |
send the current invite again to everyone who should have it |
calendar_reminder_list |
GET /api/workspace/calendar/reminders?booking_id=&status= |
invites and reminders, with whether mail and Comms are connected and the notice shown in the app |
The same tools are on the workspace REST API under /api/v1/calendar. The mark and resend tools need
calendar:write; the list needs calendar:read. Marking a no-show before the start, or twice, answers 409; so does
resending an invite for a pending booking or one never invited.
The invitee's manage link adds POST /meet/api/manage/<token>/reconfirm.