MEETINGS
The meeting gets read back, not retold.
A bot joins the call, the transcript lands in your workspace, and it reads back from the record of the client it concerns.
Recording does not start on its own
The feature is off by default, and it stays off until somebody turns it on. A calendar connection carries its recording policy: no meetings, every meeting, or only the ones with someone from outside your organisation. It also requires the platform to be wired to a transcription vendor, without which nothing happens at all.
When the policy calls for it, a bot joins the call at the appointed time. It carries a name you choose and it shows up in the participant list, like anybody else. It is the only gesture in this whole piece that leaves your workspace, and it is visible.
What the transcript holds
The full text, and the same text cut into timestamped segments. Each segment carries the speaker's name when the vendor managed to attribute it, and nothing when it did not: the identification comes from them, not from something we built, and it is not guaranteed.
One transcript per meeting, whatever happens: the database enforces it, so there are never two versions of the same call to arbitrate between. Google Meet, Microsoft Teams and Zoom calls are covered, the join address being enough to tell which platform it is.
It reads back from the record
A view can carry a meetings tab, by naming the fields on the record that hold an address. The match is computed at read time, comparing those addresses against the participants': nothing is stored, so nothing goes stale the day a contact changes address.
The tab is declared on whichever object you want, a contact as much as a company or a deal. Meetings arrive newest first, and the reading pane opens the transcript beside the list.
What it is not
No write-up is drafted for you. The platform produces no summary, no record of decisions, no task list out of a call: it hands you the text of what was said, and that is where its promise stops.
Transcripts are not fed to workspace search either: you will not find one by typing a word into the search bar. An agent opens one when it knows the meeting, and that tool is only offered to it if a transcription vendor is configured.
How it works
A quarterly review with a client, where nobody has time to take notes.
You wire the platform to a transcription vendor, then set the connection's policy: every meeting, or only those with an outside participant.
At call time, the bot joins the conference under the name you gave it, and appears in the participant list.
Once the call ends, the vendor returns the full text and its timestamped segments, with the speaker's name where it could attribute one.
The transcript is stored on the event, one per meeting.
The meetings tab on the client record matches the addresses and surfaces the quarterly review.
You read back the passage you care about, or ask an agent to open that meeting's transcript.
The other pieces of this chapter
Agentic drive
Every record carries its files, and your agents read them.
Document reading
Your PDFs and scans become readable text.
Bulk import
Exports, databases and archives become typed records.
Inbox
Your exchanges surface on the records they concern.
Calendar
Your events next to your records, read-only.