ICAN inside Tetra

Meetings stop being ephemeral.

ICAN is the meeting capture and transcription layer built natively inside Tetra. Press record. The audio is captured, transcribed automatically, and posted into the thread it belongs to. The recording, the transcript, the action items, the decisions — all live where the rest of the work lives.

Recording
23:14 · transcribing
Live transcription

Pavani: —so the timeline is tight, but the integration spec is locked. Srinivas: Agreed. I will own the API mapping by Friday and post it back into this thread.

The follow-up problem is the meeting problem. A meeting happens, decisions get made, action items get committed verbally — and then somebody has to remember what was said, write it down, attribute it to the right person, and chase the right people to act on it. This is where most meetings stop creating value. The decisions exist only in human memory until somebody puts them on paper. Often, somebody does not.

ICAN solves this without adding another tool. The recording happens inside the thread the meeting was already attached to. The transcription happens automatically. The action items can be tagged to the right people in the same thread. The handoff from "what we discussed" to "what we are doing" stops being a manual exercise.

For a 5,000-person enterprise, this changes how meetings get followed up. Less rework, less he-said-she-said, less time spent reconstructing what was decided. The recording is searchable along with everything else in the thread, so future questions about "what did we decide on this six months ago" have a real answer.

How ICAN works

Four steps. One thread.

From "press record" to "the recording is in the thread, transcribed, with action items tagged" — with no separate tool to log into.

01

Press record in the thread

Inside any project thread, press record. ICAN starts capturing audio. Single-device control prevents accidental duplicate recordings across desktop and mobile.

02

Audio captured to the cloud

Audio streams directly to encrypted cloud storage. Up to 500 MB per recording. No local file on anyone's device. If the app is closed, the recording stops.

03

Automatic transcription

The audio is transcribed automatically. Editable transcript title so it surfaces under a meaningful name in search and the thread feed.

04

Posted into the thread

The recording and the transcript appear in the thread as a first-class message. Searchable, replayable, taggable. Action items can be assigned in the next message.

ICAN capabilities in production

What ICAN ships today.

Conservative list. Each capability below runs in production today and is documented in the public Tetra release notes. Future capabilities will appear in release notes when shipped, not as roadmap promises here.

01
In-thread recording
ICAN recording is initiated from inside any project thread. The recording is bound to that thread and posts back to it on completion. Available on desktop and mobile.
02
Single-device recording control
A user can only have one ICAN recording active at a time across their devices. Prevents the accidental dual-recording from happening when someone opens the app on phone and laptop simultaneously.
03
Auto-stop on app closure
If the desktop app is closed or the mobile app is terminated, the recording stops automatically. No background recording continues unintentionally. Privacy default, not configuration.
04
Automatic transcription
Recordings are transcribed automatically and posted alongside the audio. The transcript is searchable along with all other thread content.
05
Editable transcript titles
Users can edit ICAN transcript titles to give the recording a meaningful name. Surfaces in search and thread feeds under whatever name makes the recording findable.
06
Recording size optimisation
Recordings are size-optimised to stay within practical limits per recording. Audio fidelity preserved at the cost of file size, not the other way around.
07
Thread-type isolation
ICAN is available in project threads. Not available in private threads or read-only threads — recording in private discussions is intentionally disallowed for confidentiality reasons.

See ICAN capture a real meeting.

The best ICAN demo is on a real meeting your team is going to have anyway. Book a demo and we will set up the recording flow with one of your actual project threads.