> ## Documentation Index
> Fetch the complete documentation index at: https://klipy.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# How does meeting recording work?

> How Klipy Notetaker joins video calls, what it produces after each meeting, and how to control auto-join per meeting or globally.

**Klipy Notetaker** is an AI meeting bot that Klipy can schedule on your behalf. It appears in the participant list like any other guest—visible to everyone on the call—records audio, builds a live transcript while the meeting runs, and turns that conversation into structured outputs shortly after the meeting ends (typically within about five minutes). That visibility is intentional: everyone should know a notetaker is present, which makes it easier to align with your company’s policies and your customers’ expectations about recording and consent.

## How Klipy joins your calls

Klipy scans calendars you’ve connected and looks for upcoming events that include a supported video link (Google Meet, Zoom, or Microsoft Teams). For each qualifying event, Klipy schedules **Klipy Notetaker** to join at the scheduled start time. The bot records audio, maintains a real-time transcript, and uploads the session for processing when the call finishes.

**Languages:** transcription supports **99 languages**. Summaries and follow-up drafts are generated in the **language you chose during onboarding**, so outputs stay consistent with how you work.

Screenshot coming soon

Screenshot coming soon: Calendar view, event with a notetaker-scheduled badge

## What it produces

After processing, you get a structured package for each meeting—not just a raw transcript.

> [card] 1. Full transcript
>
> Complete transcript with **speaker identification** so you can scan who said what.

> [card] 2. Meeting summary
>
> **Key topics** and **decisions made**, distilled for quick review and handoff.

> [card] 3. Action items
>
> Commitments extracted **per speaker** (for example, “Alice will send the proposal by Friday”).

> [card] 4. Deal framework alignment
>
> How the call maps to your configured sales methodology (**MEDDIC**, **Sandler**, and other frameworks you enable).

> [card] 5. Follow-up draft
>
> A **ready-to-send recap email** for you to review and approve—never sent automatically.

> [card] 6. CRM updates
>
> **Contact and company records** updated with new information surfaced on the call.

Screenshot coming soon

Screenshot coming soon: processed meeting page with Transcript / Summary / Action items tabs

## Controlling the notetaker

**Default behavior:** Klipy adds the notetaker to **all** upcoming calendar events that include a supported meeting link on calendars you’ve connected.

**Per meeting:** Before the call starts, open the **Calendar** view in Klipy and **remove the notetaker** from any specific event where you don’t want a bot to join.

**Global:** Go to **Settings → Notetaker** and **disable auto-join**. With auto-join off, the notetaker won’t join by default; you can **manually invite** Klipy Notetaker to individual calls when you want coverage.

Screenshot coming soon

Screenshot coming soon: Settings → Notetaker, auto-join toggle

**During the call:** Host platforms let participants remove a bot from the meeting. If someone removes Klipy Notetaker, it leaves and stops recording—see the warning below for what happens to the recording.

> [!NOTE]
>
> **Transparency by design:** The notetaker joins as **Klipy Notetaker** and is visible in the participant list. Treat it like announcing a recorder—use your judgment and your org’s policies when sensitive topics, regulated industries, or regional recording laws apply.

> [!WARNING]
>
> If the notetaker is **removed from the call mid-meeting**, recording **stops** at that moment. Klipy still processes whatever audio was captured up to that point—your transcript and summaries may be **partial** rather than covering the full meeting.

## Supported platforms

| Service | Setup required | Auto-join conditions |
| - | - | - |
| **Google Meet** | None beyond your Google workspace connection | Calendar events on a connected Google account that include a **Google Meet** link. |
| **Zoom** | Connect **Zoom** with OAuth under **Settings → Channels** (org approval may apply). | Events include a **Zoom** meeting link and Zoom is authorized for your workspace. |
| **Microsoft Teams** | None beyond **Outlook / Microsoft 365** email and calendar access. | Calendar events include a **Teams** meeting link on a connected Outlook calendar. |

## Related guides

> [card] [Follow-ups](https://klipy.ai/docs/guides/follow-ups.md)
>
> How meeting recaps become drafts you review and send.

> [card] [What Klipy captures](https://klipy.ai/docs/guides/capture.md)
>
> Email, calendar, and messaging—what feeds Klipy beyond meetings.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.