Zoom
The conferencing account whose room Adoptiv amends and withdraws as well as creates. Move a meeting an hour and the Zoom room moves with it; delete the booking and the room is gone 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 stored 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 re-read afterwards because it does not change. Nobody has to be sent a new link.
The credential rotates on every use
Zoom issues a fresh long-lived credential each time the short-lived one is renewed, and the replacement is written back straight away. Holding the old one would strand the account silently.
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 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.
Connect Teams and a booking makes the meeting through Microsoft's own interface, carrying its joining address into the invitation the guests receive.
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 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