GongTable

Find customer proof opportunities in Gong calls

Find call-backed customer proof opportunities in Gong conversations, including quotes, outcomes, story angles, and approval-ready follow-up asks.

Run playbook

Overview

This playbook finds customer proof opportunities in Gong calls and turns them into a prioritized backlog of testimonials, case study angles, sales proof points, and follow-up asks. It is built for teams that know customers say useful things on calls, then watch those moments disappear into recordings.

Juno reviews recent conversations for direct customer language, outcomes, story arcs, and approval-sensitive signals. The output is a table plus a short brief that helps marketing and sales decide what proof to pursue next.

Why you should build proof from real customer conversations

Strong proof usually starts before anyone asks for a testimonial. It shows up when a customer explains why they switched, what changed after implementation, which stakeholder was convinced, or what anxiety disappeared.

Gong transcripts make those moments easier to revisit, and the FTC's endorsement guidance is a useful reminder that customer proof should be honest, not misleading, and connected to real experience. This playbook keeps both ideas in view: find the strongest raw proof, then route it through the right approval path before it becomes public copy.

That makes the backlog more useful than a grab bag of nice quotes. Each opportunity is scored for specificity, relevance, approval likelihood, sensitivity, and where it could improve conversion, from landing pages to sales decks to nurture emails.

Step-by-step

  1. 1
    Confirm the call window, target segment, product line, proof need, existing assets, and any approval or customer-sensitivity rules Juno should respect.
  2. 2
    Review Gong conversations for customers describing outcomes, selection reasons, implementation wins, before-and-after moments, competitive switches, or concerns that were resolved.
  3. 3
    Capture the strongest proof signals with account context, buyer role, quote or paraphrase, story angle, recommended format, and where the proof could be used.
  4. 4
    Score each opportunity for evidence strength, freshness, audience fit, approval likelihood, risk, and likely marketing value.
  5. 5
    Create a prioritized proof backlog and draft follow-up asks that account owners or marketers can personalize before requesting approval.

Frequently asked questions

Can Juno turn call quotes directly into testimonials?

Not by default. The playbook identifies promising proof and drafts follow-up asks, but customer permission and review should happen before any quote is published.

What kinds of calls are best for this?

Customer success, renewal, expansion, implementation, and late-stage sales calls are often strongest because they include context, outcomes, and buyer language. Prospect calls can also surface useful proof needs.

How often should we run it?

Monthly is a good default for active teams. Run it sooner before a case study campaign, landing page refresh, sales deck update, or customer marketing push.