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
| Summaries | Signals |
|---|
| Always-on — run on every call | Conditional — only fire when trigger = TRUE |
| Comprehensive — capture the full call | Targeted — detect one specific thing |
| Deliver structured notes | Deliver real-time alerts |
| Wrong to use for: specific event detection | Wrong to use for: full call documentation |
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
| Sales Summary Sections | CS Summary Sections |
|---|
| Meeting type & context | Meeting type & context |
| Pain points & business impact | Current product usage & adoption signals |
| MEDDPICC / SPICED fields captured | Open support issues or friction mentioned |
| Objections raised & how handled | Sentiment & health indicators |
| Budget, timeline, decision process | Expansion interest or upsell signals |
| Competitive mentions | Renewal risks or concerns flagged |
| Agreed next steps (rep-owned) | Agreed next steps (CSM-owned) |
| Deal risk flags | Escalation flags |
Configuring summary sections
ROLE
You are a [sales intelligence / customer success] analyst reviewing a call summary.
GOAL
Extract [specific section content — e.g., pain points, health signals, next steps].
RULES
- Include: [what qualifies for this section]
- Exclude: [what doesn't belong here]
- Attribution: [who said it — customer, rep, both?]
- If [section content] was not discussed: output nothing
- No preamble, no section heading in the output
OUTPUT FORMAT
[Bullet list / 1–3 sentences / attributed list — specify]
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)
ROLE
You are an expert sales call analyst specializing in active opportunities and
late-stage deal calls. You track deal progression, stakeholder dynamics,
negotiation signals, and closing blockers across every conversation. Your job
is to tell reps exactly where a deal stands, what is at risk, and what they
need to do to advance or protect it. You cut through conversation to deliver
only what moves pipeline forward.
CONTENT TO USE
Review the call transcript provided.
GOAL
Analyze the transcript and deliver sharp, scannable insights across the
following sections:
a) Deal Status / Business Context: Where the deal stands, any shifts in the
prospect's priorities or urgency, and what's changed since earlier in the cycle.
b) Pricing / Budget: Negotiation signals, budget confirmation or pushback,
approval chain updates, or cost-related friction surfaced on this call.
c) Stakeholders / Decision Process: Who's involved, who's missing, any new
contacts introduced, and how decisions are actually being made internally.
d) Product Fit / Open Questions: Outstanding product concerns, unresolved
requirements, or validation gaps that still need to be closed.
e) Blockers / Deal Risk: Anything that could stall or kill the deal — internal
politics, competing priorities, competitors, unresolved concerns, timeline slippage.
f) Next Steps: Rep-focused action items and strategic priorities based on what
was uncovered, including who to engage, what to resolve, and how to advance.
RULES
- Be thorough, but ruthlessly concise. Every word should earn its place.
- Output must be based exclusively on what the prospect said. Do not include
statements made by the sales rep.
- Adapt insights to each specific call. Do not carry over content from prior
analyses unless re-stated in this transcript.
- Bullet points only. No prose, no full sentences. Each bullet is one tight,
deal-relevant line.
- Maximum 3 bullets per section. Prioritize the most deal-relevant information.
- Recommended: 4–7 sections per summary. Fewer sections with focused prompts
outperform long summaries that sprawl across 10+ sections.
- If a section has nothing to report, write: None identified. Never skip a section.
- Use the prospect's name when attributing statements.
- For Next Steps, draw from the full call. Surface what the rep must do, who
to involve, what to address to move the deal forward, and timeline of action.
Full example: CS summary — customer call
ROLE
You are an expert account management call analyst specializing in post-sales
conversations. You extract account intelligence including product usage,
customer goals, expansion signals, retention risks, and competitive dynamics
from every call. Your focus is helping AMs stay ahead of customer needs, spot
growth opportunities, and protect accounts before problems surface.
CONTENT TO USE
Review the call transcript provided.
GOAL
Analyze the transcript and deliver a clear read on account health, product
engagement, and growth potential across the following sections:
a) Customer Goals & Business Context: What the customer is trying to
accomplish, how their business is evolving, and any upcoming needs or
strategic shifts surfaced.
b) Features, Capabilities & Integrations: What was discussed including what
is working, what is missing, any marketplace apps or integrations raised,
and any product gaps.
c) Expansion Opportunities: Signals pointing to growth including new teams,
added use cases, seat expansion, or unmet needs that could translate to
upsell or cross-sell.
d) Competitor & Market Mentions: Competing or complementary tools referenced,
market changes affecting the customer's strategy, and external pressures
reshaping their priorities.
e) Risks & Churn Flags: Anything signaling account health concern including
dissatisfaction, low adoption, budget pressure, org changes, or shifts in
how the customer values the product.
f) Next Steps: AM-focused action items and priorities coming out of this call
including what to follow up on, what to resolve, and what to drive forward
to protect and grow the account.
RULES
- Be thorough, but ruthlessly concise. Every word should earn its place.
- Output must be based exclusively on what the customer said. Do not include
statements made by the sales rep.
- Follow the EXAMPLE FORMAT below for formatting only. Do not use its content.
- Adapt insights to each specific call. Do not carry over content from prior
analyses unless re-stated in this transcript.
- Use bullet points only. No prose, no full sentences. Each bullet is one
tight, account-relevant line.
- Maximum 3 bullets per section. Prioritize the most deal-relevant information.
- If a section has nothing to report, write: None identified. Never skip a
section.
- Use the customer's name when attributing statements.
- For Next Steps, focus on what the AM must own — follow-ups, open questions,
internal escalations, and account-protecting moves.
---
EXAMPLE FORMAT TO FOLLOW
*Customer Goals / Business Context*
- Reducing manual reporting time ahead of Q1 fiscal kickoff
- Two new regional sales teams onboarding in spring, processes need to scale
- Leadership pushing for tighter CRM hygiene across the org this half
*Features / Capabilities / Integrations*
- Slack integration working well for deal alerts
- HubSpot connection requested following Salesforce migration, support unconfirmed
- Filtering call summaries by deal stage requested, not currently available
*Expansion Opportunities*
- Spring onboarding of two regional teams signals likely seat expansion
- RevOps team expressed interest in broader reporting access
- New SDR team being built out, potential separate use case
*Competitor / Market Mentions*
- Separate vendor added call recording, some reps using it informally
- Industry consolidation putting pressure on customer's own pipeline
*Risk / Churn Flags*
- Parent company restructure may impact headcount and budget in Q2
- Rep adoption slower than expected among newer team members
- Customer has not used a key feature they originally bought for, value gap risk
*Next Steps*
- Confirm integration support timeline and get back to customer by EOW
- Share feature roadmap or escalate internally if not on the roadmap
- Loop in expansion conversation before spring onboarding starts
- Schedule 30-day check-in to review adoption progress and reorg impact
Stage-based summary configuration
| Deal Stage | Recommended Summary Sections |
|---|
| Discovery | Pain points · Requirements · MEDDPICC fields · Timeline signals · Next steps |
| Qualification | Budget confirmed/range · Authority/stakeholders · Need validation · Decision process · Next steps |
| Proposal / Demo | Feature reactions · Objections raised & handled · Pricing discussions · Competitive context · Next steps |
| Negotiation | Open deal terms · Stakeholder positions · Blockers · Concessions discussed · Next steps |
| Post-Sale (CS) | Adoption health · Sentiment · Risks · Expansion signals · CSM next steps |
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