How to create and share actionable call snippets in Gong for team training

Ever sat through a two-hour sales call recording just to find one golden moment? Yeah, nobody has time for that. If you’re leading (or just trying to improve) a sales, CS, or support team, your people need fast, focused feedback—not another bloated Zoom link. This is where Gong’s call snippets come in. If you use Gong, you already know it’s great for recording and analyzing calls. But most folks miss out on the real time-saver: sharing short, actionable clips instead of full calls.

This guide is for anyone who wants to actually move the needle with team training, not just tick a box. I’ll show you how to create, organize, and share call snippets that your team will actually watch—and use. I’ll also point out where Gong shines and where it’s easy to waste time.


Why use call snippets instead of full call recordings?

Before we get into the weeds, let’s be honest: nobody is re-watching hour-long calls unless you force them, and even then, they’re probably multitasking. Snippets let you:

  • Highlight what matters: Show a killer objection handle, a fumbled pitch, or a perfect discovery question.
  • Save time: Cut to the chase—literally.
  • Make feedback digestible: Your team’s attention spans aren’t getting longer.
  • Encourage sharing and discussion: It’s way easier to react to a 2-minute clip than a 45-minute meeting.

Step 1: Identify moments worth sharing

Not every “snippet” is worth your team’s time. Here’s what to look for:

  • Strong openers or closes: Did someone nail (or botch) the first 60 seconds?
  • Objection handling: Real customer pushback, not just role-play.
  • Discovery questions: Moments where a rep uncovers needs or pain points.
  • Awkward silences or fumbles: We learn as much from misses as wins.
  • Unique value statements: When someone actually moves the deal forward.

Pro tip: Don’t get paralyzed by perfection. Even a rough snippet is better than another “let’s watch the whole call” calendar invite.

Step 2: Create a snippet in Gong

Here’s how you actually make a snippet. (Assuming you’ve got call recordings in Gong.)

  1. Open the call recording you want to mine for teaching moments.
  2. Find the right moment. Use the transcript search if you remember what was said. Don’t waste time scrubbing through audio if you can avoid it.
  3. Highlight the segment:
  4. Click and drag on the transcript to select the part you want.
  5. Or, if you’re old-school, use the start/stop timestamp method.
  6. Click “Create Snippet” (the scissors icon, usually). Name your snippet something specific—“Handling Pricing Objection, April 2024” beats “Good part.”
  7. Review and edit: Trim dead air, ums, or side chatter. Keep it tight—1 to 3 minutes max.

What not to do:
- Don’t make “highlight reels” just for the sake of it. If it’s not useful, skip it. - Don’t over-edit. You’re not making a Super Bowl ad.

Step 3: Add context and make it actionable

A snippet alone isn’t training. It’s just a clip. To make it actionable:

  • Add a note: “Notice how Sam reframes the objection instead of arguing.”
  • Ask a question: “How could this have been handled differently?”
  • Tie to a process: “This is our MEDDIC qualification in action.”

Gong lets you add comments or notes to snippets. Use them. If you can’t explain why you’re sharing a clip, don’t share it.

Pro tip: Don’t turn snippets into a “gotcha” moment or call out individuals in a way that embarrasses them. Focus on the behavior, not the person.

Step 4: Share snippets with your team

Here’s what’s actually effective:

  1. Send directly in Gong: Share the snippet link with teammates or channels. Gong lets you tag people, which is handy.
  2. Embed in Slack or email: Drop the snippet link with a quick note (“Worth 90 seconds. Notice the way pricing is handled.”)
  3. Add to a playlist: Group related snippets—like “Objection Handling Wins” or “Discovery Misses.” Gong’s playlist feature is underused and great for onboarding.
  4. Use in team meetings: Instead of another 60-minute call review, play snippets and discuss as a group. Way less painful.

What to avoid: - Dumping a dozen snippets at once. Nobody will watch them all. - Sharing without context. “Watch this” isn’t a strategy.

Step 5: Organize snippets so they’re actually used

Snippets are only useful if people can find them later.

  • Use clear naming conventions: “Product Demo – Handles Security Objection – May 2024” is better than “Clip 3.”
  • Build playlists for themes: Objections, demos, discovery, etc.
  • Keep it fresh: Prune old snippets so new hires aren’t watching outdated material.
  • Centralize resources: If your team uses a wiki, Notion, or Google Drive, drop key snippet links there.

Pro tip: Ask your team what snippets they want to see. Chances are, their requests are way more relevant than what you’d pick solo.

Step 6: Get feedback and iterate

Don’t assume what you share is hitting home.

  • Ask for reactions: “Was this snippet helpful? Would you handle it differently?”
  • Watch completion rates: If nobody’s watching, try shorter clips or different content.
  • Solicit suggestions: Encourage reps to create and share their own snippets. The best learning is peer-driven, not top-down.

What to ignore:
- Vanity metrics (like “views” alone). Engagement and discussion matter more than click counts.

What works, what doesn’t, and what to skip

What actually works:

  • Short, specific snippets (1–3 min).
  • Adding context or a learning question.
  • Organizing by theme, not just date or rep.
  • Sharing in the flow of work (Slack, email, team meetings).
  • Encouraging peer sharing and discussion.

What doesn’t:

  • Long or rambling clips. (Nobody has time.)
  • Snippets with no explanation.
  • Sharing too many at once.
  • Making it punitive (“Look how you messed up”).

What to ignore:

  • Snippets as “compliance” training. This is about actual learning, not box-ticking.
  • Over-produced highlight reels. Real, unpolished moments are more relatable.

Final thoughts: Keep it simple, keep it useful

Don’t overthink it. Gong call snippets are a tool, not a silver bullet. The trick is to use them to save time and surface real learning moments—not to create more noise. Start small, ask your team what’s working, and keep iterating. Most importantly, don’t let “perfect” get in the way of “actually helpful.” The best snippet is the one your team actually watches and talks about.

Now go make team training suck less.