Zoom
The one video room this product keeps up with after it is made. Move the meeting an hour and the Zoom room moves with it, on the link guests already have. Delete the booking and the room goes with it.
One room, across its whole life
created- 1Booking saved locally
the row exists before anything external is attempted
- 2Room created
a scheduled meeting, joining before the host allowed, no waiting room
- 3Length worked out
whole minutes between your start and end, with one minute as the floor
- 4Written into the invitation
joining address, room number and passcode go into the calendar entry body, so guests receive them in the invite
- joining addressmeeting_urlhttps://zoom.us/j/8412…
- passcodemeeting_password419276
- room numberconference_id841 2093 7714
- the host start addressmetadatahttps://zoom.us/s/8412…
Product figures from the platform’s own defaults - not customer averages
How it works.
Created before the invitation goes
The room is booked first so its joining address can be written into the calendar invitation the guests receive. Its length is worked out from the start and end of your booking, never assumed.
The booking remembers which room it owns
The account that made it, the room number, the host and the private start address are all kept on the booking. A later edit therefore reaches the same room instead of leaving an orphan and creating a rival.
Rescheduling reaches the room
Changing the time, the title or the description sends the change on, and the joining address is deliberately not read back, because it does not change. Nobody has to be sent a new link.
The connection does not quietly go stale
Zoom issues a fresh long-lived credential each time the short-lived one is renewed, and the replacement is written back right away. Holding on to the old one would strand the account without anybody noticing.
One moment in every message.
Every message passes through the same seven. Zoom 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- Consent
- Two scopes: writing meetings, and reading the account identity, so a room can be attributed to the host that owns it
- Meeting kind
- Scheduled, with joining before the host allowed and no waiting room
- Duration
- Derived in whole minutes from your start and end, with one minute as the floor
- Stored on the booking
- Six values: the joining address, the passcode, the room number, the host's private start address, the host identifier and which account made it
- Lifecycle
- Created on save, amended on edit, withdrawn on delete. An already-gone room is treated as success
- No account connected
- The booking still saves and comes back with a note that no Zoom account is attached
- Guests see it
- Because the joining address, room number and passcode are written into the calendar invitation body
- Not the same as
- Google Meet, whose link is minted by the calendar itself and cannot be edited independently
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
12 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.
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 zoom on your own floor.
Thirty minutes, your numbers and your data. We will set zoom up live and you can decide from the thing itself rather than from this page.
14-day trial · no card · migration included