Gong helps revenue marketers decide what prospects and customers are saying in sales conversations before shaping campaigns, handoffs, or enablement. With the connector authorized, Juno can review call details and transcripts, inspect scorecards, track team activity, and bring conversation evidence into campaign briefs or follow-up plans. It keeps call context, coaching signals, and revenue activity close to the marketing work that depends on them.
What Juno does with Gong
Gong gives Juno a practical Gong MCP connector for marketers who need the voice of the customer before they shape campaigns, handoffs, or enablement. Once authorized, Juno can read call transcripts, explore call details, review scorecard reports, and track team activity so revenue conversations show up where marketing decisions are being made.
The useful part is not another tab for skimming recordings with a cold coffee. Juno can turn call context into campaign briefs, follow-up plans, messaging notes, and handoff trackers that explain what buyers asked, where reps needed support, and which accounts deserve attention.
Gong's own guide to viewing call transcripts shows why transcripts matter: they let teams revisit what was said, search conversation moments, and share snippets. Its documentation on scorecards also explains how structured call feedback helps teams spot coaching patterns, which is useful context when marketing is tuning talk tracks or enablement.
Where it fits in your workflow
Connect Gong when the next marketing task depends on recent sales reality. That might be a campaign brief for a segment with fresh objections, a product launch handoff, a customer story shortlist, or an enablement pack built around what reps are actually hearing.
In practice, Juno can start with a question like "what did enterprise prospects push back on this month?" and shape the answer into a concise roadmap, brief, tracker, or draft pack. It can pull together relevant call details, transcript evidence, scorecard themes, and team activity so the next decision is grounded in conversation evidence instead of the loudest anecdote.
It also helps after campaigns are live. If a new offer is landing awkwardly, a handoff is getting muddy, or a talk track is picking up steam, Juno can use Gong context to show what changed and what marketing should adjust next.
What you get
- Gong conversation briefs that combine call transcripts, call details, scorecard context, and team activity around a specific marketing question
- Transcript readouts that surface customer language, objections, buying signals, and follow-up moments worth bringing into a campaign
- Scorecard report summaries that help marketing understand where reps need clearer positioning, sharper proof, or cleaner enablement
- Team activity snapshots that show which conversations, accounts, and handoffs deserve review before the next send or planning meeting
- Follow-up plans that turn revenue conversation evidence into messaging notes, draft packs, enablement angles, or account handoff trackers
Frequently asked questions
Does Juno replace Gong?
No. Gong remains the system for revenue conversations, call recordings, transcripts, scorecards, and sales intelligence. Juno brings that context into the marketing work surface where briefs, trackers, and follow-up plans get made.
What should I connect Gong for first?
Start with a focused workflow: review sales objections before a campaign, prepare an enablement brief, summarize call themes for a segment, or build a follow-up tracker for accounts that need marketing support.
Can Juno analyze scorecards and team activity?
Yes. Juno can review scorecard reports and team activity available through the connector, then summarize the patterns that matter for messaging, enablement, handoffs, and campaign timing.
What inputs make the connector most useful?
Bring the campaign goal, segment or account set, timeframe, and the output you want. Juno works best when it knows whether you need a brief, roadmap, tracker, or draft pack.