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.Sales lens vs. CS lens — section comparison
Configuring summary sections
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

