summarize-conversation-transcript

name	summarize-conversation-transcript
description	Summarize a supplied transcript; never invent content.
metadata	{"short-description":"Turn transcripts into CRM-ready outcomes"}

Summarize Conversation Transcript

Outcome

A traceable conversation summary that preserves speaker intent and separates commitments from suggestions.

CRM-neutral operating contract

• Discover available CRM, communication, calendar, knowledge, and file capabilities before choosing a retrieval plan. If no live CRM is available, use user-supplied exports when that still satisfies the request; never imply a live write is possible.
• Map records by meaning, not vendor labels: organization, person, lead, opportunity, activity, product, service record, user or team, and knowledge item. Inspect schemas and custom fields, preserve native IDs, stages, currencies, timezones, and fiscal periods.
• Keep observed facts, derived conclusions, and missing information distinct. Anchor consequential claims to record IDs, fields, timestamps, or named sources, and state access or freshness limits.
• Start read-only. Before creating, updating, assigning, sending, or scheduling, show the exact proposed action and obtain confirmation unless the current request already authorized that exact mutation.
• Obey connected-system permissions, resolve ambiguous records or people instead of guessing, check for duplicates before creation, and report partial failures without repeated retries.

Workflow

1. Resolve the user, target records, requested scope, reporting window, timezone, and business objective. Ask only for missing details that materially change the result.
2. Retrieve the minimum authorized evidence needed from the following inputs: Transcript or detailed notes, participant identities when known, meeting purpose, related account and opportunity context, and current open commitments.
3. Normalize relevant entities and fields while retaining native record identifiers and source timestamps.
4. Apply the analysis rules below. When evidence conflicts, show the conflict rather than averaging it away.
5. Deliver the required output in a compact form suited to the scope. Put urgent or decision-relevant items first.

Analysis rules

1. Preserve speaker attribution and flag uncertain transcription, identity, dates, numbers, or decisions.
2. Extract customer goals, needs, evidence, objections, decisions, commitments, questions, risks, and next steps without adding facts.
3. Distinguish explicit agreement, tentative language, seller proposal, and unresolved issue.
4. Map only well-supported facts to candidate CRM fields and prevent duplicate activities or tasks.

Required output

• Conversation summary
• Customer needs and language
• Decisions and unresolved items
• Action items with owner and date
• Proposed CRM field diff
• Follow-up draft when requested

Actions and boundaries

Summarization is read-only. Confirm logging, field updates, task creation, or message sending separately.