Meetings

Book across a whole team without a scheduling thread.

Pooled availability that respects every person's own working hours, their real calendar and their own timezone — then writes the meeting into the calendar they already use.

Join early access

Meetings are planned, not built. The availability engine underneath them runs today, and the changelog says what changed when.

Planned

The scheduling parts that are actually hard

Per-person working hours

Each host's own schedule, not one team-wide window

Pooled and collective

First available across a pool, or everyone required in the room

Buffers and notice

Before and after each meeting, minimum notice, daily caps

Two-way calendar sync

Microsoft Graph and Google Calendar, busy time both directions

Video links

Generated by the calendar itself — Teams or Meet — so no video vendor sits in the middle

Rescheduling

A single link, no thread, with the reminder queue re-derived rather than duplicated

Time

Shipped

A meeting is an instant, not a number on a clock.

Two production scheduling products shipped daylight-saving defects this year: one displayed booking slots an hour off across a transition while storing the correct instant, and another shifted multi-day services by a full day from midnight anchoring. Our launch footprint spans both cases — the Gulf has no daylight saving and Europe changes twice a year — so this was designed in rather than patched.

Stored

A UTC instant, the IANA zone identifier, and the zone the booking was made in

Rendered

From the zone name — never from a saved numeric offset

Rules

Merchant-entered hours are validated strictly, so a schedule starting in a skipped hour is rejected at entry rather than silently moved

Tested

Both switchover weekends per launch region, plus a sub-hour-offset zone and a half-hour-offset zone

Planned

Microsoft first, Google when the review clears

Microsoft Graph needs one permission to both write the event and generate a Teams link, and no external review. Google requires an OAuth verification for calendar scopes, which is free but takes weeks in practice, and until it clears an application is capped at 100 test users with credentials that expire every seven days. We are building Microsoft first and submitting Google in parallel, and this page will say which is live.

Microsoft 365 and Outlook

Planned first

Google Calendar

Planned behind OAuth verification

Apple iCloud

Not planned — no OAuth, no webhooks, credentials cannot be issued programmatically

Everything else

Subscribe to an ICS feed, or attach an .ics file to the confirmation

Planned

Reminders that survive a reschedule

The most common failure in this category is a reminder that says a meeting is in one hour for a meeting that moved to next week. Bookesto will derive reminders from the booking rather than queue them once, cancel and re-derive on every change, and choose the delivery channel at send time so that a WhatsApp reply inside Meta’s free window is used when it is open.

Meetings are next after routing.

Join early access and the changelog will tell you the day it ships.

Join early access See the roadmap

No card. Merchant access is invite-only — you get the build log and first access.