Skip to main content
Call Summaries generate a structured post-call note after every call. Unlike signals, summaries are always-on — they run regardless of content. The power is in how you configure the sections.
Summaries: use the structured format. Plain natural language doesn’t work well for summaries. A summary prompt has multiple sections, per-section output rules, silence behavior, formatting requirements, and an example format — too many moving parts for a single unstructured instruction to handle reliably. The structured format earns its complexity here.

Summaries vs. Signals

The multi-lens framework: same call, different flavor

The same call can generate completely different summaries for different audiences — different sections, different emphasis, different delivery destinations. You don’t need to choose between a sales summary and a CS summary. You configure both.
The multi-lens concept. Configure one Summary for Sales and a separate one for CS. Both run on the same transcript. Both deliver to different channels. Each structured around what that audience needs to act on.

Sales lens vs. CS lens — section comparison

Configuring summary sections

Next steps prompts require attribution.Template: [Owner] — [Action] — [Timeline if stated]
  • Example: Rep — Send security documentation — by end of week
  • Example: Customer / Sarah (Procurement) — Confirm budget approval — before next call
If ownership is ambiguous, attribute to the person who spoke the commitment. If no next steps: output nothing.
There are two valid ways to configure a summary: per-section prompts (each section is its own extraction prompt configured individually in the UI) or a single comprehensive prompt that defines all sections and their output format in one go. The example below uses the single-prompt approach — useful when you want tight control over the full output structure and tone.

Full example: New Business call summary (active opportunities)

Full example: CS summary — customer call

Stage-based summary configuration

Call Summaries — QA checklist

  • Each section prompt has one clear extraction goal
  • Silence rule defined for every section
  • Next steps include attribution: owner + action + timeline
  • Sales lens and CS lens configured as separate summaries if both teams use Momentum
  • Stage-based sections configured if team has meaningful stage variation
  • Delivery destinations set correctly — right channel or DM for each lens
  • No section tries to do too much — split complex sections in two