What this meeting summary agent handles
Reps finish calls and meetings with a short window to get context into the CRM before the next one starts. Manual summaries either get skipped or turn into multi-paragraph narrative blocks that do not map cleanly to fields.
A Salesforce meeting summary agent turns raw transcripts and notes into structured, actionable updates:
- Structured summary extraction. The agent reads the meeting transcript or notes and extracts next steps, open questions, stakeholder changes, objections, timeline updates, and decision blockers.
- Proposed CRM updates. The agent maps the extracted summary to CRM fields: opportunity notes, close date updates, stage suggestions, and follow-up tasks. All proposals are surfaced before writing.
- Follow-up task creation. The agent suggests task creation for next steps and assigns them to the right owner based on the meeting context.
How the agent works
The table below shows how meeting data turns into structured CRM updates and where approval sits in the loop.
| Input | What the agent extracts | Proposed output | Approval |
|---|---|---|---|
| Call transcript | Next steps, open questions, stakeholder changes, objections, timeline | Opportunity notes, close date update, task creation | Approval before write |
| Meeting notes | Decision blockers, stage readiness, buying intent | Stage change proposal, next task, follow-up email draft | Approval before write |
| Uploaded recording | Key moments, stakeholder sentiment, action items | Summary snippet, proposed task owner, CRM field updates | Approval before write |
How to set up this agent
Connect the meeting or call recording tool you currently use, such as Gong, Zoom, or Google Meet.
Specify which CRM fields the agent can propose updates for, including notes, dates, stages, and task fields.
Explain the summary structure expectation so the agent knows what to extract and how to present it.
Show the approval loop for proposed summaries and CRM writes so the buyer understands control remains with the rep or manager.
Permissions and approval checks
- Read access should include opportunity records, contact records, task history, and activity history.
- Write scope should be limited to approved fields like notes, dates, tasks, and stage suggestions.
- Connection to meeting tools should be surfaced clearly with the OAuth flow and scoped read-only access.
- Approval views should surface both the raw meeting context and the proposed CRM changes side by side.
Frequently asked questions
Does the agent write summaries directly into Salesforce?
No. By default, the agent generates the summary and proposes the field updates. You review both before approving the write to Salesforce.
Where does the agent get meeting context from?
The agent reads from meeting tools like Gong, Zoom, Google Meet, or uploaded notes. If you use a transcription service, the agent reads the transcript. If you paste notes manually, the agent reads the notes field.
What gets surfaced in the summary?
The agent extracts next steps, open questions, stakeholder changes, new objections, timeline updates, and decision blockers. It presents the summary in a structured format that maps cleanly to CRM fields.
Can the agent update the opportunity stage based on the meeting?
The agent can propose a stage change if the meeting content supports it, but stage updates always go through approval. You review the proposed change, see the reason, and decide whether to commit.