Calendar Sync
Book a slot while the customer is still on the line and the invitation is in their inbox before you say goodbye. What they change at their end comes back when somebody presses sync, not on its own.
A slot booked, and the trip back
writing out- 1validated and storeddone
the local row is written first, so the booking exists whatever Google does next
- 2written to the accountdone
inside the same operation, against the primary calendar on it
- 3guests are emaileddone
by Google, because the write asks it to notify everyone
- 4the identifier comes home
what Google returns is put on the local row, so a later edit patches that same entry
- 250 per page, up to twenty
thirty days behind to a hundred and eighty ahead
- canceled entries are asked for
deliberately, so the matching local row can be deleted rather than left greyed out
- a series arrives flat
occurrences are expanded before storage, and the rule rides along on the row as text
Product figures from the platform’s own defaults - not customer averages
How it works.
Out on save, back when you ask
Saving the meeting puts it on the Google calendar in the same breath and has Google email the guests, so nobody sends a follow-up with the details in it. Changes made over in Google come back when somebody presses sync, not on a timer.
One meeting, not two
Google hands back its own name for the entry and we keep it, so moving the time later changes the meeting the customer already has instead of leaving them holding a second one.
Called off there means gone here
Canceled entries are asked for on the way in so the local one can go with them. A meeting called off at the other end disappears from the day rather than sitting there grayed out.
A standing weekly call arrives as weeks
A repeating series is stored as the individual meetings it actually is, so looking at next Tuesday shows next Tuesday instead of working it out from a rule. The rule rides along on the row as text.
Two moments in every message.
Every message passes through the same seven. Calendar Sync is the lit ones, 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.
7 facts- Provider
- Google Calendar, and only the primary calendar on that account
- Direction
- Writes leave immediately on save. Reads are pulled when requested and are not scheduled
- Window
- Thirty days behind to a hundred and eighty ahead, two hundred and fifty per page, twenty pages
- Invitations
- Sent by Google, because the write asks it to notify everyone
- Recurrence
- Series are expanded into occurrences; the first rule is carried on the row as a string
- Outlook Calendar
- Carried by the Microsoft connection instead, which brings the diary over Graph. Exchange Sync is the page for it
- Not the same as
- Exchange Sync, which pulls a Microsoft calendar into a store of its own that this screen does not read
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.
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.
Pick Teams on a booking and the join link is written into the invitation guests receive, so nobody chases it in a follow-up. A room you own travels too.
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 calendar sync on your own floor.
Thirty minutes, your numbers and your data. We will set calendar sync up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included