---
name: discovery-call-debrief
description: Converts a discovery call transcript or notes into a structured summary, qualification evidence, CRM field proposals, risks, and dated next steps. Use after sales calls for call debriefs, discovery summaries, CRM update suggestions, follow-up preparation, or opportunity qualification.
license: Apache-2.0
metadata:
  adlass.categories: "sales-crm/meeting-prep-debrief, sales-crm/pipeline"
  adlass.industries: ""
  adlass.tags: "discovery-call, call-summary, crm-update, qualification, next-steps, sales"
  adlass.adaptation: "mapping"
  adlass.source: "n8n:2336, n8n:2547, n8n:4641"
  adlass.version: "1"
---

# Discovery call debrief

## Purpose

Turn conversation evidence into a reliable sales record. Capture the customer's situation, impact, desired outcome, stakeholders, timing, objections, commitments, and proposed CRM updates without inventing facts.

## Scope

One call transcript or note set, prior opportunity context, qualification framework, CRM field schema, and follow-up actions stated in the conversation.

**Excluded:** sending the follow-up, changing CRM data, assigning work to people who were not named, and legal or technical commitments not made in the call.

## Data basis

- Call transcript or notes supplied as a document input.
- Prior opportunity notes and CRM schema in scope.
- Qualification framework in scope.

## Result

A cited call summary, CRM update proposal, and action register with owners and dates.

## Quality criteria

- Every material fact cites speaker and timestamp or note location.
- Facts, interpretations, and open questions are separated.
- No next step lacks an owner or due date unless explicitly unknown.
- CRM proposals use the target field vocabulary.
- Contradictions are surfaced.

## Instructions

Prefer direct statements over paraphrased assumptions. Quote objections when wording matters. Preserve uncertainty around budget, authority, timing, and competition. Use prior notes only to identify changes, not to fill missing call content. Keep the summary concise enough for CRM use.

## Adapt before use
Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

- Map the CRM fields and qualification framework.
- Define timestamp and citation format.
- Define required action fields and date convention.