call-follow-up

name	call-follow-up
description	Prepare post-call follow-up; review before sends or writes.
metadata	{"short-description":"Turn completed calls into reviewed follow-up"}

Call Follow-up

Outcome

A coherent follow-up package that reflects what was actually discussed and closes open loops.

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 notes, participant identities, related CRM records, prior commitments, current fields, and user tone or channel preferences.
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. Extract decisions, commitments, questions, deliverables, owners, and dates with speaker evidence.
2. Separate customer commitments from seller commitments and proposed actions.
3. Draft the customer follow-up in plain language with accurate recap and next steps.
4. Create a field-level CRM update proposal and deduplicated task list; flag uncertain facts for review.

Required output

• Meeting outcome
• Customer follow-up draft
• Internal action list
• Proposed CRM diff
• Uncertainties requiring review

Actions and boundaries

Obtain separate confirmation for sending the message and for each batch of CRM or task changes.