Meeting Scheduling
The platform's own event table is what a booking really is, and the conferencing and the calendar are two write-throughs hanging off it. That order is why a booking survives an outage at either one.
Saving a booking
saved- 1Validatea title is required, both ends must parse, and the end may not come before the start
- 2The local rowwritten first. Five hundred characters of title, two hundred and fifty-five of location
- 3The conferenceleaves the buildingcreated ahead of the calendar write so its joining details can ride inside the invitation
- 4The calendar entryleaves the buildingwritten to the connected account, which emails the guests
- 5Remindersrebuilt from the current time and settings, in the app and by mail together
Product figures from the platform’s own defaults - not customer averages
How it works.
The local row is written first
Validation runs, the row is created, and only then does anything leave the building. A booking is never lost because a third party was slow or down.
The conference is made before the invitation
Where a room has to be booked with an outside service, Zoom being the one that does, it is booked ahead of the calendar write so its joining details ride inside the invitation. Google Meet is the exception and needs no such ordering, because its link is asked for inside the calendar write itself.
Failure comes back as a warning, not an error
If the conference or the calendar write fails, the response still reports the saved booking and names what did not happen, so nobody re-enters a meeting that already exists.
Reminders are rebuilt on every edit
Undelivered reminders are discarded and regenerated from the current time and settings, while ones already sent are kept as history. Moving a meeting an hour later moves its reminders along with it.
One moment in every message.
Every message passes through the same seven. Meeting Scheduling is the lit one, and everything either side of it is a different page in this category.
- 01Connect
the account it syncs with
- 02Compose
writing it, and from what
- 03Send
leaving now, or on a schedule
- 04Arrive
landing, and what it lands as
- 05Attach
pinning it to the right record
- 06Book
the meeting that comes of it
- 07Govern
who may use what, and see what
The specifics.
8 facts- Source of truth
- The platform's event table. Provider events share it, distinguished by which connection wrote them
- Validation
- A title is required, both ends must parse, and the end may not precede the start
- Limits
- Five hundred characters of title, two hundred and fifty-five of location, the same for a recurrence rule
- Reminders
- Eight choices from none through to a day before, delivered in the app and by mail together
- On delete
- The calendar entry is withdrawn and the conference cancelled first, then the row goes
- Cancelled events
- Filtered out of the range the calendar screen asks for rather than deleted outright
- Guest replies
- A non-empty guest list coming back from the calendar overwrites the one held here. An empty answer is treated as no news and the local list stands
- Not the same as
- Calendar Sync is the traffic between this table and Google. This is the act of creating the booking in the first place
What this sits beside.
Mail and diary are one surface with several parts. These are the ones a person passes through in the same minute.
More in Email & Calendar
11 capabilitiesWebmail, four sync providers, tracking, calendar and meetings.
A full mail client inside the CRM, with snooze, send later, eight system folders and a reading sandbox that never runs a single thing the sender wrote.
Connect Gmail on one scope and mail arrives by push rather than polling, filed against the lead holding the address, with nobody having to forward anything.
Outlook and Microsoft 365 sync through Graph with delta queries and subscriptions, so large mailboxes stay current without re-reading themselves.
A Microsoft mailbox brings its calendar and address book over Graph, on subscriptions that renew themselves, with a ten-minute pass running underneath.
Any mailbox that speaks IMAP and SMTP connects with a form and a live login test, so a provider nobody built an integration for is still a real inbox here.
Templates with merge variables, organised into groups and permissioned per team, so the answer your best rep writes becomes the answer everybody sends.
Grant a whole template folder to particular roles and teams, so regulated copy stays with the people allowed to send it. Filing is the act of sharing here.
Opens and clicks recorded against the record, with signed link identifiers so the tracking endpoint never trusts a parameter it was handed.
Put a thread out of sight until it matters and schedule a send for the morning, with the parked thread coming back unread so you cannot walk past it.
One signature per connected mailbox, added by the send path to new messages and forwards, so mail from the platform arrives looking like mail from a person.
Inbound mail attaches to the lead holding any address on it, sender or recipient, matched exactly once lowercased. Two columns, one query, no resemblance.
The rest of the platform.
Five more categories, all on the same record and the same bill. Each card names three of its capabilities, so you can tell from here whether it is worth opening.
Email & Calendar
See meeting scheduling on your own floor.
Thirty minutes, your numbers and your data. We will set meeting scheduling up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included