Documentation

01What is ION Align

ION Align is real-time meeting intelligence. Instead of producing a summary after the fact, it captures decisions, tasks, and topics while the meeting is still happening — attributed to the person who actually said them, using the meeting platform's own participant roster rather than guessed voice labels.

Most note-taking tools read a transcript after the call and try to reconstruct what mattered. ION Align works the other way: a bot joins your call as a visible participant, streams a live transcript, and an AI model reads it continuously — so decisions, blockers, risks, and action items show up on your screen within seconds of being said, not minutes after the call ends.

The deeper idea is that not all meetings are the same kind of event. A standup and a board meeting need different things watched for, different questions answered, and different records kept. ION Align's protocols teach the AI what a given meeting type is actually for — so a committee meeting gets governance tracking (motions, seconds, votes, quorum) while a retrospective gets sentiment and improvement tracking, from the same underlying engine.

02High-level capabilities

Nine capabilities work together across the life of a meeting — before, during, and long after it ends.

03Starting a meeting

The primary way to use ION Align is to send a bot into a call you're already having.

1. 1

   Paste the meeting link

   From the ION Align home page, paste a Zoom, Google Meet, or Teams link into Start Meeting. A title is optional but makes the meeting easier to find later.

2. 2

   Choose a protocol

   Open the protocol dropdown and pick the meeting type that matches what you're about to run. Each option shows its own description right underneath, so the choice explains itself. If nothing fits, leave it as General — you'll still get standard topic/decision/task extraction, just without a protocol's extra signal detection.

3. 3

   Confirm before you send it

   Sending the bot opens a confirmation dialog showing the link, the title, and the protocol you picked (still editable right there) — so a meeting never starts on the wrong protocol, or by accident. If a prior meeting of the same protocol had open items, you'll also see a carry over N open items option here — accepting it seeds this meeting's goals from what was left unresolved last time.

4. 4

   The bot joins

   Within moments the bot appears in your call as a participant. You're redirected straight to the live meeting dashboard, where the transcript starts streaming immediately.

04The live meeting

Once the bot is in the call, everything happens on one page — the meeting dashboard — which offers two ways to watch a meeting unfold.

Dashboard

The dashboard is the analytical view: a full transcript in the center, with panels for topics, decisions, and tasks docked at either edge. Each panel collapses behind a labeled tab with a live count badge — so you can keep the transcript full-width and still see at a glance that there are, say, three open decisions, without a panel standing open the whole time. Your layout is remembered the next time you open a meeting.

If a protocol is selected, a row of metric chips replaces the default topic timeline — each chip is that protocol's own scorecard, computed live from what's been captured so far (see Protocols for what each one tracks). Underneath, a protocol signals strip lists every typed event detected so far — click one to jump straight to that moment in the transcript.

A compact minutes readiness indicator sits alongside the chips whenever the protocol defines required captures — for example Minutes 6/8 · 2 missing — and expands into a checklist showing exactly what's covered and what isn't yet.

The Conductor

The Conductor is a full-screen live command view, meant to be the only thing on screen for whoever is actually running the meeting. It reads from the same live data as the dashboard, laid out for facilitation rather than analysis:

• Now / Next — the topic currently being discussed, and the next open goal, so you always know where the meeting is.
• Live signal feed — protocol moments, decisions, and action items as they land, newest first, unowned actions flagged.
• Voice equity — a live bar per speaker showing share of the conversation, so a quiet voice or a dominating one is visible at a glance.
• Minutes readiness ring — the same readiness score as the dashboard, as a glanceable gauge.
• Context cards — when connected to org memory, relevant decisions from other meetings or organizational documents surface automatically as the topic shifts.
• Ask the org — a search box to pull an answer from past meetings or org documents without leaving the call.

Open it from the 🎛 Conductor button on the dashboard; press Esc to return.

05Protocols, in detail

A protocol is not a cosmetic theme — it changes what the AI actually pays attention to. Selecting one does three things: it steers the live analysis toward what matters for that meeting type, it turns on detection for a small vocabulary of signals unique to that meeting type, and it defines what a complete record of that meeting looks like (fed into minutes readiness and the generated report).

Nine protocols ship built in. Below, each one lists what it's for, the exact signals it watches for, the live chips you'll see on the dashboard, and anything else worth knowing about it.

06Building your own protocol

The Protocol Builder (under Tools → Protocol Builder) lets anyone in your organization describe a meeting type in plain language and get back a working protocol — no code, no configuration file.

1. 1

   Describe the meeting

   Write a few sentences about how the meeting actually runs and what a complete record of it needs to include. Be concrete — name the events that matter (a vote, an acknowledgement, a scored review) and what "done" looks like.

2. 2

   ION Align compiles a draft

   The description is compiled into a full spec: a name and icon, guidance for the AI analyst, a small set of signal types specific to this meeting, and the required-captures checklist that will drive its minutes readiness.

3. 3

   Review and tune

   Everything is editable before publishing — rename a signal, adjust the guidance, add or remove a required capture, change the accent color. The editor validates as you go (for example, a required capture that references a signal type must reference one that actually exists).

4. 4

   Publish

   Once published, the protocol appears in the picker everywhere alongside the built-ins — live analysis, signal detection, minutes readiness, chips, and reports all pick it up immediately, for every future meeting that selects it.

07Reports

Any meeting can generate a polished, self-contained HTML report — styled and structured according to its protocol.

A General meeting gets a balanced report covering topics, decisions, tasks, and effectiveness. A protocol meeting gets a report shaped around what that protocol cares about: a standup report leads with blockers and per-speaker updates; a retrospective leads with sentiment and what to change; a committee meeting produces formal minutes with attendance, quorum, a motions-and-votes table, and action items. Wherever a required capture wasn't recorded, the report says so plainly rather than guessing.

Reports can also be generated with a themed awards section — a lighthearted, optional flourish that turns per-speaker analytics (signal density, engagement, moderation) into fun recognitions, in a theme of your choosing.

08Meeting Synthesis

A single meeting report tells you what happened in one conversation. Synthesis reads across several meetings at once, and surfaces what only becomes visible when they're held side by side.

From the Synthesis page, select two or more past meetings, choose one of six synthesis types below, optionally add a one-sentence focus, and generate. The result is a narrative report citing the specific meetings and decisions it draws from.

09Action Hub

Meetings end; commitments shouldn't disappear with them. The Action Hub lists every action item extracted across every meeting in one place.

Each action shows its owner (unassigned items are called out), due date (overdue and due-soon items are highlighted), and meeting of origin. Mark an item Done, Dismiss it if it's no longer relevant, or Reopen it later — status is tracked independently of the meeting's own analysis, so re-running analysis on a meeting never silently resets what you've already closed out. Filter by status or by owner to see, for example, everything still open and assigned to one person across every meeting they've been in.

10Org memory & search

Where connected, ION Align maintains a searchable memory of your organization's meetings — and, where available, its documents.

Every finalized meeting has its distilled record — decisions, actions, topics, protocol signals — indexed for search. From the Org memory panel (on the Synthesis page) or Ask the org inside the Conductor, a single query searches across that meeting history and returns ranked, cited results linking back to the meeting they came from.

When your organization also runs a connected knowledge base of its own documents, the same query searches those documents too — so a question mid-meeting like “what does our safety manual say about this” can be answered from official policy, not just recalled from memory.