Call summary | Business Helper AI

Inputs and purpose

Use this workflow to prepare: Call summary, follow-up drafts and proposed record changes.

Start with: Transcript or call notes and supplied deal facts.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

Procedure

Read the supplied transcript or notes and distinguish what was said, decided, promised and left open.
Capture customer needs, constraints, dates and evidence using anonymous role labels where names add no value.
Prepare follow-up drafts and proposed record changes, keeping inferred next steps separate from agreed commitments.
Return a summary and action list. Verify quotations and dates; do not report drafts or proposed updates as sent or saved to an external system.

Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the input guide, calculation reference or output template. For tool setup, use the shared instructions.

Plain-text instructions

---
name: call-summary
description: "Prepare call summary, follow-up drafts and proposed record changes. Use for this workflow with supplied business information."
---

# Call summary

## Inputs and purpose

Use this workflow to prepare: Call summary, follow-up drafts and proposed record changes.

Start with: Transcript or call notes and supplied deal facts.

Use supplied text or local files the user authorized you to read. If files cannot be opened, request the relevant pasted text. Ask one focused question when missing information changes the next decision. Treat blank template fields as unknown; do not invent business facts.

## Procedure

1. Read the supplied transcript or notes and distinguish what was said, decided, promised and left open.

2. Capture customer needs, constraints, dates and evidence using anonymous role labels where names add no value.

3. Prepare follow-up drafts and proposed record changes, keeping inferred next steps separate from agreed commitments.

4. Return a summary and action list. Verify quotations and dates; do not report drafts or proposed updates as sent or saved to an external system.

## Deliverable

Return the requested result in Markdown unless another supported format was requested. Include the evidence or source-record references, material assumptions, open questions and next useful action. Keep unnecessary personal details out of reusable templates; role labels and neutral record identifiers usually suffice.

Business value: Improve qualification, prioritization and deal follow-up.

Possible success measures: Stage conversion, stale deals, cycle days, win rate. Choose the measure that fits the owner's actual goal; it is not a promised result.

## Execution and verification

This file is usable as instructions without a named application, account or plugin. Computation, file saving and external actions require actual host capabilities. Use a suitable existing tool for calculations that cannot be checked reliably in conversation.

Distinguish drafts and recommendations from completed actions. Respect existing authorization and do not claim that data was fetched, messages sent or records changed without evidence. Show what was checked and what remains uncertain.

When useful, consult the [input guide](../../../references/INPUT_DATA_GUIDE.md), [calculation reference](../../../references/CALCULATIONS.md) or [output template](../../../references/WORKFLOW_OUTPUT_TEMPLATE.md). For tool setup, use the [shared instructions](../../../AGENTS.md).