> For the complete documentation index, see [llms.txt](https://docs.maiagent.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.maiagent.ai/maiagent-user-guide/maiagent-user-guide-en/meeting-records/create-meeting.md).

# Create a Meeting Record

## Create a New Meeting

1. Go to the "Meeting Records" page
2. Click "New Meeting"
3. Fill in the following information:

| Field                               | Description                                             | Required |
| ----------------------------------- | ------------------------------------------------------- | -------- |
| **Meeting Name**                    | The meeting title for easy searching and identification | Yes      |
| **Participants**                    | List of meeting participants                            | No       |
| **Speech Recognition Engine (STT)** | Select the speech-to-text engine                        | Yes      |
| **Recognition Language**            | Languages used in the meeting (up to 3)                 | Yes      |

## Select a Speech Recognition Engine

The system provides multiple STT (Speech-to-Text) engines, each with different language support and recognition quality:

| Engine          | Features                                                             |
| --------------- | -------------------------------------------------------------------- |
| **Deepgram**    | High-quality real-time transcription, supports multiple languages    |
| **Azure**       | Microsoft Speech Services, excellent Chinese and English recognition |
| **AssemblyAI**  | High accuracy, ideal for English scenarios                           |
| **WhisperLive** | Based on OpenAI Whisper, supports a wide range of languages          |
| **Bronci**      | Customized engine                                                    |

Different engines support different languages and quantities. After selecting an engine, the system automatically displays the available language list.

## Configure Real-time Translation (Optional)

If participants speak different languages, enable real-time translation:

1. Turn on the "Enable Translation" toggle
2. Select target translation languages (up to 3)
3. Select the LLM model for translation

Translation occurs simultaneously with transcription, and the transcript displays both the original text and translation results.

## Link Knowledge Base (Optional)

You can specify a knowledge base to link when creating the meeting. After the meeting ends, you can upload the transcript to the knowledge base with one click, allowing the Agent to access meeting content.

## Manage Meeting Records

On the meeting records list page, you can:

* **Search**: Search by meeting name
* **Filter**: Filter by status (Pending, Recording, Processing, Completed, Failed)
* **Date Range**: View records within a specific time range
* **Edit**: Modify meeting name, language settings, translation settings, and knowledge base links
* **Delete**: Remove unwanted meeting records


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.maiagent.ai/maiagent-user-guide/maiagent-user-guide-en/meeting-records/create-meeting.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.