Best Practices Guide: AI Summaries

As an Admin, your job is to set teams up for success. When summaries are aligned with your team’s workflows and meeting types, you unlock visibility, improve team productivity, and reduce the burden of manual note-taking across Sales, CS, and Enablement.

What You’ll Do

• Create custom Summary Prompts based on meeting goals
• Configure Summary automations to trigger based on meeting template, title, or team
• Test and refine prompts using real meetings and feedback loops

Do It Today

• Meet with Sales, CS, and Enablement to define what a “good summary” looks like
• Build 2–3 prompt-based summary templates for core meeting types (e.g. Discovery, QBR, Onboarding)
• Configure automation rules and delivery destinations
• Test output using real meetings and refine based on feedback

What a Great Summary Prompt Looks Like

A strong summary starts with a well-structured prompt. Prompts guide the AI to focus on what really matters, whether that’s objections, action items, sentiment, or training follow-ups. Your prompt is the blueprint.

A Good Prompt Should...

• Be goal-oriented — e.g., “Create a training follow-up email”
• Be clear and directive — e.g., “List top 3 objections” or “Summarize in bullet points”
• Be structured — Break it into labeled sections (e.g., Greeting, Goals, Next Steps)
• Be tone-aware — “Professional and concise” or “Supportive and friendly”

Tips for Writing Your Own Prompt

• Start with: “What’s the outcome I want from this summary?”
• Break the output into sections or bullet points
• Include formatting instructions like “limit to 3 sentences”
• Clarify tone: “friendly,” “neutral,” “coaching tone,” etc.
• Test → Refine → Repeat

Including context from past meetings

By default, AI Summaries focus on the current meeting. If you want the summary to also reference relevant context from previous calls with the same customer, you need to explicitly request that in your summary prompt.

Example prompt additions

• “When summarizing, also consider relevant context from previous meetings with this customer.”
• “Include relevant decisions, open questions, and action items from past calls if they help explain the current discussion.”
• “If past meetings are not relevant, do not mention them.”

Ready to Use Scorecard Templates

Your job is to summarize a meeting transcript. Write at a Flesch reading score 80 or higher. Add timestamp ranges so I can find the related topics quickly.

General:Act as an information extraction tool for revenue teams. You are reviewing a transcript from a discovery meeting between an AE and prospect.

Your task: Extract the strategic information that supports qualification, messaging, and next steps.

Output Format:

Meeting Purpose: Clarify the goal of the call and why it was scheduled.

Key Takeaways: List core problems, use case fit, timeline, and stakeholders.

Meeting Summary: Recap the customer's pain points, desired outcomes, and how the product addresses them.

Product Feedback: If shared, summarize feature gaps or comparisons with competitors.

Follow-ups & Action Items: List each item, who owns it, and by when.

Suggested Next Steps by AI: Suggest 3 specific next actions and 1 strategic question to explore further.

Add timestamp ranges for each item (e.g., [07.222] - [13.488])

Your job is to summarize a meeting transcript. Write at a Flesch reading score 80 or higher. Add timestamp ranges so I can find the related topics quickly.

General:You act as a value realization analyst. You support Customer Success Managers in capturing strategic takeaways from QBR meetings with customers.

Your task: Extract key business outcomes, risks, and expansion potential.

Output Format:

Meeting Purpose: State the QBR objective or strategic checkpoint.

Key Takeaways: List value metrics, challenges, stakeholder alignment.

Meeting Summary: Describe the customer's sentiment, usage highlights, and relationship status.

Product Feedback: Note feature requests or concerns shared.

Follow-ups & Action Items: Identify who owns what and by when.

Suggested Next Steps by AI: Recommend 3 steps to increase value/retention, and 1 risk question to monitor.

Add timestamp ranges for each item.

Your job is to summarize a meeting transcript. Write at a Flesch reading score 80 or higher. Add timestamp ranges so I can find the related topics quickly.

General:Act as a coaching support tool. You help Enablement and Managers review recorded sales calls to identify coachable moments.

Your task: Extract key behaviors and missed opportunities for rep coaching.

Output Format:

Meeting Purpose: What was the intended outcome of the rep’s call?

Key Takeaways: List observed strengths, gaps, and sales techniques used.

Meeting Summary: Evaluate how well the rep identified need, communicated value, and handled objections.

Product Feedback: Capture anything the customer said about product capabilities or confusion.

Follow-ups & Action Items: List internal training needs or external next steps.

Suggested Next Steps by AI: Offer 3 coaching recommendations and 1 question to ask in a 1:1.

Add timestamp ranges for each item.

Your job is to summarize a meeting transcript. Write at a Flesch reading score 80 or higher. Add timestamp ranges so I can find the related topics quickly.

General:Act as a product researcher. You assist Product Managers in extracting actionable insights from early user feedback calls.

Your task: Highlight problems, reactions, and adoption blockers.

Output Format:

Meeting Purpose: What feature or prototype was being tested?

Key Takeaways: Summarize the user’s goals, reactions, and challenges.

Meeting Summary: Explain which UX moments worked or failed and why.

Product Feedback: Capture bugs, usability issues, and feature gaps.

Follow-ups & Action Items: List dev-facing and customer-facing to-dos.

Suggested Next Steps by AI: Recommend next interview questions and one design iteration.

Add timestamp ranges for each item.

Your job is to summarize a meeting transcript. Write at a Flesch reading score 80 or higher. Add timestamp ranges so I can find the related topics quickly.

General:Act as a strategic copy researcher. You’re analyzing a VoC interview transcript for messaging, content inspiration, and market signals.

Your task: Extract rich insights and customer language.

Output Format:

Meeting Purpose: What topic or product was the interview focused on?

Key Takeaways: Pull out pain points, emotional triggers, and success stories.

Meeting Summary: Highlight how the customer describes the product and value.

Product Feedback: Any suggested features or competitive mentions.

Follow-ups & Action Items: Identify if this is usable for content, case study, or further interviews.

Suggested Next Steps by AI: Suggest messaging improvements or content formats.

Add timestamp ranges for each item.

Your job is to summarize a meeting transcript. Write at a Flesch reading score 80 or higher. Add timestamp ranges so I can find the related topics quickly.

General:Act as a team assistant. You’re extracting updates and decisions from an internal project or leadership sync.

Your task: Capture progress, blockers, and upcoming priorities.

Output Format:

Meeting Purpose: What was the goal of this sync?

Key Takeaways: Summarize major updates per team or function.

Meeting Summary: Recap team alignment, challenges, and decisions made.

Product Feedback: Skip if not applicable, otherwise summarize internal blockers.

Follow-ups & Action Items: List project tasks and deadlines with owners.

Suggested Next Steps by AI: Propose next steps or questions for next sync.

Add timestamp ranges for each item.

Common Use Cases for Summaries

1. Sales Teams

Use Case: Discovery Calls (SPICED / MEDDIC)

✅ Best practice: Use a custom summary prompt to capture strategic buyer insights like pain, urgency, goals, and the decision-making process.

❌ Pitfall: Flat summaries that miss key signals, like buying intent or decision dynamics.

Custom Prompt Tip:

Use structured sections like:

• Meeting Purpose
• Key Takeaways
• Follow-ups & Action Items
• Suggested Next Steps

📝 Example prompt line:

Extract SPICED/MEDDIC insights like pain points, urgency, and decision criteria. Add timestamp ranges for each.

Use Case: Demo Reviews

✅ Best practice: Automatically summarize if the demo addressed real customer needs and objections.

❌ Pitfall: Generic play-by-play recaps with no strategic context.

Custom Prompt Tip:

Include fields like:

• Use Case Fit
• Objection Handling
• Product Interest Level

📝 Example prompt line: Summarize how well the demo addressed the customer's goals and objections. Add timestamps for each section.

Use Case: Closing Call Audits

✅ Best practice: Use summary prompts to extract deal-critical data like stakeholder confirmation, pricing discussions, and next steps.

❌ Pitfall: Missing key deal information like timeline, blockers, or sign-off authority.

Custom Prompt Tip:

Include:

• Decision-maker Signals
• Contract Details
• Final Questions & Objections

📝 Example prompt line: Highlight signals of deal readiness including stakeholders, pricing, and urgency. Add suggested next steps.

2. Customer Success Teams

Use Case: Onboarding Consistency

✅ Best practice: Create onboarding summary prompts to track if key goals and success metrics were captured.

❌ Pitfall: Technical onboarding summaries with no business context.

Custom Prompt Tip:

Include:

• Success Metrics
• Milestones Discussed
• Onboarding Risks

📝 Example prompt line: Summarize onboarding goals, success metrics, and initial blockers. Add timestamps for key topics.

Use Case: QBR Effectiveness

✅ Best practice: Use summary prompts to highlight product impact and create a customer-facing recap.

❌ Pitfall: Over-reliance on usage stats instead of business results.

Custom Prompt Tip:

Use:

• ROI / Value Delivered
• Strategic Initiatives
• Product Gaps or Risk Flags

📝 Example prompt line: Generate a QBR recap that connects product usage to business value and future goals.

Use Case: Churn Risk Detection

✅ Best practice: Use summary content to track tone shifts, frustrations, or missed value moments.

❌ Pitfall: Only reacting after usage drops.

Custom Prompt Tip:

Add:

• Tone Sentiment
• Product Concerns
• Renewal Readiness

📝 Example prompt line: Extract signs of dissatisfaction or renewal hesitation from the transcript.

3. Product & Marketing Teams

Use Case: Feature Rollout Monitoring

✅ Best practice: Create summaries that flag feedback from sales calls on new features.

❌ Pitfall: Reps forget to mention the feature or capture the customer’s reaction.

Custom Prompt Tip:

Include:

• Feature Mentioned
• Initial Reaction
• Follow-Up Questions

📝 Example prompt line: Highlight any feedback or interest in new features mentioned during the call.

Use Case: Voice-of-Customer Collection

✅ Best practice: Use summary templates to extract qualitative feedback and use quotes in marketing.

❌ Pitfall: Relying on vague CRM notes instead of full customer voice.

Custom Prompt Tip:

Add:

• Exact Quotes
• Feature Requests
• Customer Phrasing

📝 Example prompt line: Capture product requests, user feedback, or pain points in the customer’s own words.

4. Enablement & RevOps

Use Case: Sales Methodology Compliance

✅ Best practice: Check if summaries reflect methodology structure (SPICED, MEDDIC, BANT).

❌ Pitfall: Teams trained but don’t use the framework in live calls.

Custom Prompt Tip:

Include:

• Business Pain
• Decision Criteria
• Timeline Signals

📝 Example prompt line: Check if the rep applied MEDDIC during the call. List qualifying elements discussed.

Use Case: Training Effectiveness

✅ Best practice: Use summaries from shadowing sessions or onboarding calls to gauge effectiveness.

❌ Pitfall: No post-training evaluation.

Custom Prompt Tip:

Include:

• Rep Strengths
• Missed Opportunities
• Timestamped Coaching Moments

📝 Example prompt line: Summarize rep performance, highlight coaching moments, and flag areas needing improvement.

Automations

Once your summary templates are set up, the next step for any admin is to define automations that ensure the right summary is applied to the right meeting, without manual work.

We recommend using a combination of filters like meeting title, team group, and audience type to make sure each meeting is evaluated with the most relevant summary

A well-structured automation setup might look like this:

AI Meeting Context for Automations: The AI now uses the full meeting context, including the transcript and available CRM data, to understand what the conversation is about. This lets you create automations based on meaning rather than only rigid filters. For example, you can trigger different summary templates when it is a first meeting, a qualification call, or an intro conversation.

To use it, add Meeting Context as a condition in your automation settings and describe in natural language when the rule should apply.

When is this especially useful? Here are some situations where Meeting Context solves problems that standard filters can't:

• Unreliable meeting names: If your team uses a tool like Outreach or Salesloft that writes the meeting type into the calendar invite description, you can use that instead of the title — for example: "If the calendar description contains 'Discovery', apply the Discovery template."
• Structured CRM workflows: If your CRM auto-creates events with a Type field (e.g. a Salesforce-based onboarding flow with stages like Kickoff, Handover 1, Handover 2), the AI can read that field to trigger the right template — no naming convention required.
• Deal stage: Trigger a lightweight template for early-stage calls and a more detailed one for late-stage or negotiation conversations, based on the opportunity stage in your CRM.
• Customer segment: Route SMB and Enterprise accounts to different templates automatically, based on account data already in your CRM.

Summaries aren’t just for documentation. They’re how managers turn AI into an extra set of ears. Used consistently, they surface what’s happening in the field, how messaging lands, and which reps need a hand.

What You’re Aiming For

As a manager, your job isn’t just to read summaries, it’s to coach with them.

Summaries help you:

• Catch misaligned messaging or risky phrasing early
• Compare how top reps position your product
• Track product feedback across markets or industries
• See if objection-handling or next steps are clear
• Guide new hires on real examples of what “good” looks like

Best Practice: Weekly Summary Scan

Set aside time each week to scan AI-generated summaries across your team:

1. Skim summaries for red flags
   Focus on deals without clear next steps or with repeated objections.
2. Add contextual manager comments
   Highlight strong discovery moments or suggest rephrasing:
   "Nice job connecting value to ROI, consider confirming decision timeline earlier."
3. Tag & share coaching-worthy summaries
   Use Slack or your LMS to highlight standout summaries as teachable moments.
4. Spot patterns with filters
   Look at summaries across meeting types, topics, or teams to detect trends in product messaging, deal risk, or rep development.

Use Summaries to Answer Strategic Questions:

✅ Manager Actions (At a Glance)

• ✅ Read summaries for red flags before pipeline reviews
• ✅ Comment on summaries to coach in-context
• ✅ Use summaries to spot trends in positioning and objections
• ✅ Turn high-quality summaries into training examples
• ✅ Pair summaries with recordings for faster QA
• ✅ Filter summaries by team, topic, or meeting type

Summaries aren’t just a paper trail. They’re your fast track to working smarter. Use them to cut down post-call admin, reflect on your performance, and follow up with confidence.

What to use them for

1. Get a clear recap of what happened in your calls
2. Save time with pre-drafted follow-up summaries
3. Catch anything you may have missed live
4. Reflect on your talk time, delivery, and pacing

Best Practice: Build a Personal Summary Habit

Use summaries to create a consistent post-meeting routine that works for you, not just the CRM.

After Every Key Meeting:

• Read your AI summary
• Use the auto-generated follow-up email as a draft — review, tweak, and send
• Check for gaps in your delivery (Did you ask next steps? Confirm urgency?)

“I noticed I talked a lot about features but missed clarifying success metrics. I’ll add that to my next call.”

Once a Week:

• Reflect on what’s changing in your calls over time
• Bookmark one or two strong summaries to reuse as templates

💡 Pro Tip: Save Time with the Follow-Up Email

Demodesk automatically generates a follow-up summary email for external meetings. You’ll see it in your recording view after the call — review it, make quick edits if you want, and send. What used to take 15 minutes now takes 2.

Use the AI’s structure as your template and save your mental energy for the actual deal.

✅ User Actions (At a Glance)

• ✅ Read 1 AI summary per week to reflect and improve
• ✅ Edit and send the follow-up email directly from your account
• ✅ Save standout summaries for future reference