How Calendar works
What Venom Calendar does, how it compares with Calendly and Google appointment schedules, how bookable times are computed, and the safety and privacy rules it keeps.
What it does
You connect every calendar you have. Venom reads the busy time from all of them, and you create event types such as "30 min intro": weekday mornings in your time zone, a 10-minute buffer after each meeting, 4 hours' notice. A lead opens the link, sees only the times when every connected calendar is free, and books. The event goes into the calendar you picked for that event type (with a Meet link for Google). Your other accounts get an invite, so they show the time as busy too.
An example: you have three Google accounts (personal, company, a client's Workspace) and a TripIt feed. "30 min intro" checks all four, writes to the company calendar, and sends the other two accounts an invite. The lead gets a WhatsApp reminder an hour before, their Outreach sequence stops, and their deal moves to "Meeting booked".
Compared with Calendly and Google appointment schedules
| Venom Calendar | Calendly | Google appointment schedules | |
|---|---|---|---|
| Connected calendars | as many as you like | 6 on paid plans, 1 on Free | your own; secondary calendars only on paid plans |
| Several Google accounts | yes, each over its own sign-in | counts toward the 6 | only if shared with and subscribed by the host account |
| .ics feeds | yes | no | only Google's own subscriptions, which refresh slowly |
| Which calendars block time | per event type | one set for every event type | the host's |
| Where bookings are written | per event type, plus invites to your other accounts | one calendar for everything | the schedule's calendar |
| Reminders | email, and SMS, WhatsApp or Telegram from your own numbers through Comms | email, SMS from Calendly's number | |
| CRM | People, Funnel and Outreach update on booking | through integrations | none |
| API and agents | REST and MCP tools | REST API | none |
| Self-hostable | yes | no | no |
How bookable times are computed
The engine (lib/calendar/slots.ts) is pure: the booking page, the server and an agent all compute the same times.
- Working hours are per local date in the schedule's time zone, so 09:00 to 17:00 stays 09:00 to 17:00 when daylight saving time starts or ends. A date override replaces that day's hours; an empty override is a day off.
- Daylight saving time. A time the clock skips (02:30 on the spring-forward night in New York) is never offered. A time that happens twice (01:30 on the fall-back night) is offered once, at its first occurrence.
- Start times step from the start of each block of hours by the event type's increment, or by the meeting's length when there is none. With several durations, each time lists the durations that fit there.
- Buffers go around your bookings and around the new meeting. Busy time from your calendars blocks the meeting itself; an option applies the buffers to it too, for travel time.
- Minimum notice: nothing starts sooner than this from now.
- How far ahead: a number of days, a number of business days (Monday to Friday), or a fixed range of dates, counted in your time zone.
- Limits per day and per week (Monday to Sunday), counted in your time zone, for that event type.
- Per calendar: choose whether tentative events count as busy (yes by default) and whether all-day events do (no by default, since most are reminders). All-day events are read in that calendar's own time zone.
- Time zones: the invitee sees times in their own zone, or in yours when the event type locks it (in-person meetings).
Safety and privacy
- Nothing is contacted until you connect it. Venom doesn't call Google, Microsoft or a feed URL before you add the account.
- Tokens are sealed. OAuth tokens and feed URLs (a private feed URL works like a password) are sealed in your org's vault and never shown again.
- Busy blocks, not events. Venom keeps when you are busy. It keeps event titles only for your own week view; a booking page, an invitee and an agent booking for someone never see them.
- No double bookings. Selecting a time places a short hold. On submit, Venom checks your calendars again, and the database refuses a booking that overlaps another one (buffers included), so when two people race for the same time, exactly one gets it and the other is offered the next free times. A retried submit returns the first result.
- Invites keep their identity. A booking's calendar invite keeps one ID for its whole life, and each reschedule or cancellation updates it rather than sending a new one.
- Our own code. Calendar is written from scratch; no code is taken from AGPL schedulers.