Meeting Scheduling
The booking is saved here first, and the video room and the calendar entry go out after it. That order is why a meeting agreed on a call is never lost because somebody else's service was slow at the wrong moment.
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 booking is saved before anything leaves the building
It is checked, it is written down, and only then does anything go out to a third party. Nobody loses a meeting they agreed on the phone because Zoom or Google was having a bad afternoon.
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 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 answer still reports the saved booking and names what did not happen, so nobody re-enters a meeting that already exists.
Move the meeting and the reminders move with it
Undelivered reminders are thrown away and rebuilt from the current time and settings, while the ones already sent stay as history. Pushing a call an hour later pushes its reminders too.
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 canceled first, then the row goes
- Canceled 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 mailbox connections, tracking, calendar and meetings.
The thread and the lead it belongs to are one screen apart, not one tab apart. Snooze, send later, and a reading pane that runs nothing the sender wrote.
Mail is here without anybody pressing refresh or forwarding anything, filed against the lead holding the address. Google knocks the moment something changes.
The mailbox stays connected, and a message somebody moved is not sitting here twice. Outlook and Microsoft 365 over Graph, picking up only what changed.
A Microsoft mailbox brings its diary and address book with it, and whether it sits in Microsoft 365 or on a server in your building is worked out for you.
The connection for a mailbox nobody hosts for you. We sign in for real before saving the hosts and ports, so a typo is caught while you are still at the form.
Templates with merge variables, organized into groups and granted per team, so the answer your best rep writes becomes the answer everybody sends.
Regulated copy stays with the people allowed to send it. Filing a template into a group is what shares it, so there is no second step for anybody to forget.
What does not count is the useful part: a rep opening their own message, a crawler, the same person twice in five minutes. A figure a supervisor can act on.
Park a thread and it comes back at the hour you named, unread, so nobody walks past it. Hold a send and it leaves at the hour you named, once, never twice.
Nobody retypes their sign-off. It is held once per mailbox and added on the way out, so mail from the platform arrives looking like mail from a person.
Mail files itself against the lead, on a rule short enough to print: the addresses on the lead, matched exactly. No domain guessing, and nothing to dispute.
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