AI Meeting Summary & Q&A

Custom Summary Agent

The meeting records summary feature lets you select a custom AI assistant (Agent) to generate summaries. Different Agents can have different role instructions to produce summaries in different styles:

• General Summary Agent: Organize meeting highlights, decisions, and action items

• Technical Meeting Agent: Focus on technical decisions, architecture discussions, and technical debt items

• Business Meeting Agent: Focus on client requirements, sales progress, and opportunity tracking

Auto-generate Summary

1. Go to the meeting detail page

2. Switch to the "Summary" tab

3. Select the AI assistant to generate the summary

4. Click "Generate Summary"

The AI analyzes the complete transcript and organizes the meeting highlights, decisions, and action items.

Summary Version Management

Each time a summary is generated or edited, the system retains a complete version history:

• Add Summary: Each summary generation creates a new version

• Edit Summary: Modify existing summary content

• Version History: View all summary versions and their creation times

• Delete Summary: Remove unwanted summary versions

AI Q&A

In addition to the summary feature, you can ask questions directly about the transcript content:

1. Switch to the "AI Q&A" tab

2. Select the AI assistant to use

3. Enter your question (e.g., "What decisions were made in this meeting?" "What are the next action items?")

4. The AI finds relevant content from the transcript and provides an answer

This feature is especially useful for quickly reviewing specific content from long meetings without re-reading the entire transcript.

Agent Ticket Creation

After a meeting ends, action items and decisions usually need to be manually entered into a project management or ticketing system. You can let the AI assistant handle this step: in the AI Q&A tab, ask it to turn the items discussed in the meeting directly into tasks or tickets.

Meeting Records does not have a dedicated "Create Ticket" button. AI Q&A uses the full AI assistant conversation, so as long as the selected AI assistant is configured with tools that can create tickets, you can ask it to create tickets in the conversation — the ticket creation capability comes from the AI assistant, not from Meeting Records.

How It Works

Step	Details
① Meeting Transcript	Meeting transcription is complete, and the transcript has been uploaded to the knowledge base and parsed
② Select AI Assistant	In the AI Q&A tab, select an AI assistant configured with ticket creation tools
③ Issue Ticket Creation Command	For example, "Compile the action items from this meeting and create a ticket for each one"
④ AI Assistant Calls Tools	The assistant calls API tools or MCP tools based on the field mappings and ticket creation rules in its role instructions
⑤ Create Tickets	Tickets are written to your company's ticketing or project management system
⑥ Report Results	The assistant reports each ticket's number and link in the conversation

Prerequisites

Condition	Description
Meeting is linked to a knowledge base, and transcript parsing is complete	AI Q&A requires the transcript to be in the knowledge base before it can be used. You can link a knowledge base when creating a meeting; if not set at that time, you can also select a knowledge base in the AI Q&A tab and click Upload Transcript. See Download and Knowledge Base Integration for details
An AI assistant configured with ticket creation tools	The tool, not Meeting Records, is what actually calls the ticketing system. See the setup steps below
Ticketing system provides a callable API	MaiAgent communicates with external systems via API tools or MCP tools, without being limited to any specific vendor; as long as the other party provides an API for creating tickets, it can be integrated

Setup Steps

1. Create a ticket creation tool: On the Tools page, click Add API Tool and configure your company's ticketing system's "Create Ticket" API (you can paste a cURL command directly and the system will automatically parse the URL, headers, and HTTP method). See Create API Tool for details. If the other party provides an MCP server, you can also use MCP Tool instead.

2. Assign the tool to the AI assistant: Add the newly created tool to the AI assistant's available tools list. See Configure Tools for AI Assistant.

3. Define ticket creation rules in the role instructions: Whether the AI calls the tool at the right time and how fields are filled depends on the role instructions. Refer to the example below, and see the Role Instructions Design Guide for writing principles.

4. Use in meetings: Go to the AI Q&A tab on the meeting detail page, select this AI assistant, and issue a command directly, such as "Compile the action items from this meeting and create a ticket for each one."

Ticket creation writes to an external system. It is recommended to verify field mappings with a test project or test environment before switching to your production ticketing system.

Role Instructions Example

# Role
You are a meeting action item ticketing assistant.

# Task
Users will ask you to create tickets based on meeting transcripts. Follow this process:

1. Identify clear action items and decisions from the transcript; ignore pure discussions or items that haven't been finalized
2. Organize each action item into a ticket with the following field mappings:
   - Title: One sentence describing what needs to be done, under 30 characters
   - Content: Add the background and rationale mentioned in the meeting
   - Assignee: The person explicitly assigned in the transcript
   - Due date: The date explicitly mentioned in the transcript
3. Before calling the tool, present the compiled ticket list to the user for confirmation; only create after getting approval
4. After creation, report each ticket's number and link

# Constraints
- Only create tickets based on transcript content; do not add tasks that were not discussed
- If the assignee or due date cannot be determined from the transcript, leave blank and note it in the response; do not guess
- When the same item is mentioned multiple times in the meeting, merge into a single ticket

Verification and Troubleshooting

The parameters actually received by the tool and the returned results can be viewed in AgentOps' Tool Execution Records — this is the fastest way to troubleshoot ticket creation issues.

Issue	Cause and Resolution
AI Q&A is unavailable	The meeting is not linked to a knowledge base, or the transcript is still being parsed. Select a knowledge base in the tab and upload the transcript, then try again after parsing is complete
AI listed the action items but did not actually create tickets	The tool was not added to the assistant's tool list, or the role instructions do not explicitly require calling the tool. Check steps 2 and 3
Ticket creation failed	Check the error message in the tool execution records. Common causes include missing required fields, expired authentication, or insufficient permissions
Ticket field content is incorrect	Make the field mapping rules more specific in the role instructions, and explicitly instruct it to leave fields blank rather than guess when information cannot be determined
AI's response is unrelated to this meeting	The currently selected AI assistant may not be linked to this meeting's knowledge base; the interface will show a reminder. Switch to a linked assistant