Scheduler
Send a link. Get a meeting.
Booking pages on your domain that check your real calendar, guard your buffers and notice periods, and open a CRM contact before the call starts. Confirmations, reminders and reschedules handle themselves.
01Availability
Slots that respect your week.
01 / The engine
Rules first, then the calendar
Weekly hours per day — split ranges included — with date overrides on top. Then the guardrails:
- Buffers before and after every booking
- Minimum notice and a booking horizon, 1–365 days
- Slot spacing of 15, 30 or 60 minutes
- Daily and weekly booking caps
02 / Calendar sync
Checks before it offers
Busy times pull from Google Calendar before a slot is shown; confirmed bookings land back on it, Meet link included. And it fails open — if Google is unreachable, booking never breaks.
03 / Timezones
Your hours, their clock
You define availability once, in your timezone. Guests browse in theirs, detected automatically, and the daylight-saving edges are handled — a 9:00 slot means 9:00 on both sides of the switch.
02The booking
From link to CRM contact.
04 / Intake
Ask before they arrive
Nine field types beyond name and email, each mappable to CRM contact fields — the booking creates the contact with the answers attached. Meetings happen where you say: in person, phone, Google Meet, Zoom, a custom spot, or wherever the invitee asks.
05 / Approval & outcomes
You keep the last word
Turn on approval and bookings wait as pending until you confirm — the slot stays blocked either way. Afterwards, mark completed or no-show; both are triggers the automation engine can act on.
06 / Guest self-service
Reschedules without the thread
Confirmations, reminders and reschedule notices go to everyone — additional guests included — with a calendar invite attached. Guests cancel or reschedule themselves from the email, inside notice windows you set; the old booking stays chained to the new one.
03Teams
One link for the whole team.
07 / Assignment
Round-robin, owner, or by hand
Bookings rotate fairly across the team — the owner included — or stay with the owner, or wait for manual assignment. Team members see their own bookings; managers with the right permission see everything.
04After the booking
The meeting is a trigger.
08 / Automations & webhooks
Seven moments to build on
Every lifecycle event — created, confirmed, cancelled, declined, rescheduled, completed, no-show — fires the automation engine and your webhooks, deduplicated at the database level so nothing runs twice.
09 / Analytics
Know your calendar
Booking trends, popular days and hours, no-show and cancellation rates, average lead time and top referrers — per scheduler, computed from real bookings.
Every confirmation locks the scheduler row and re-checks the slot inside a transaction — two guests can't win the same minute.
Honeypot plus reCAPTCHA, Turnstile or hCaptcha, with booking attempts rate-limited per IP.
Iframe embedding with exact or wildcard domain allowlists and theme overrides.
Timed reminders before every booking — 60 minutes by default, calendar invite attached.
“No-shows dropped the week we turned on reminders. The calendar just fills itself now.”
Stop trading calendars over email.
Booking pages, round-robin and Google Calendar sync on every plan — on your domain, under your brand.
Flat price. No usage charges. Ever.