> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/ai/capturing-meetings-automatically.md).

# Capturing Meetings Automatically

### Overview

Automatic capture reduces manual work and improves consistency.

Capture produces meeting records that can be searched and linked to delivery work.

### Key Concepts

* **Capture**: meeting recording and transcription (when enabled)
* **Processing**: time required to generate summaries and action items
* **Scope**: Organization and Project assignment for the meeting record

### How It’s Used

Use automatic capture for recurring governance and delivery meetings.

Use it for discovery sessions when requirements are expected outcomes.

### Benefits

* Reduced note-taking overhead
* Faster conversion to tasks and requirements
* Higher quality context for Console search

### Setup Steps

{% stepper %}
{% step %}

### Confirm capture prerequisites

1. Confirm Meeting Notetaker is enabled.
2. Confirm browser permissions allow microphone access when required.
   {% endstep %}

{% step %}

### Capture the meeting

1. Start capture using the Meeting Notetaker entry point.
2. Confirm capture status indicates recording is active.
   {% endstep %}

{% step %}

### Wait for processing

1. Allow processing to complete.
2. Open the generated summary.

Related: [Reviewing Meeting Summaries](/ai/reviewing-meeting-summaries.md)
{% endstep %}
{% endstepper %}

### Best Practices

* Capture a small set of high-signal meetings first.
* Use consistent meeting titles to improve search and retrieval.
* Convert outputs into tasks and requirements quickly to preserve context.

### Summary

Automatic capture produces meeting records that support traceability and search.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.transform.ai/ai/capturing-meetings-automatically.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.