Sales Leader MCP Playbook

Overview

Revenue teams using Gong have more context on their buyers than ever. The challenge this leads to is, actioning on the data in a way that cuts through. Even a well-researched, well-timed email gets lost in an inbox that looks like everyone else's. Buyers have learned to filter out digital outreach regardless of how relevant it is. A physical send, timed to the right moment and tied to something real from the relationship, still gets through when another email won't.

When the Gong MCP and the Sendoso MCP Server run in the same AI session (In Gong’s client or via an LLM like Claude), that reading happens in seconds. The agent pulls a synthesis of what Gong knows about a deal or account — blockers raised, stakeholder concerns, competitive mentions — and that context feeds directly into how Sendoso searches and executes a send. The gift gets chosen based on what is actually happening in the relationship. The note card references a real conversation. Neither platform alone closes that loop: Gong surfaces the signal; Sendoso acts on it.

The plays this combination enables are the ones that determine late-stage outcomes: re-engaging a deal that went dark, timing a send to arrive before a QBR, reaching the CFO who has been on two calls and never directly responded. Physical sends still break through when another email won't. 

Why This Matters for Sales Leaders

• Gong deal context + Sendoso send execution — The Gong agent reads the deal so the rep doesn't have to. Why a deal went dark, what a competitor said, what the champion raised on the last call — all visible in seconds, with a gift and note drafted from that context. The 30-45 minutes a rep loses reviewing call history before a re-engagement comes back as active selling time.

• Gong account briefs + Sendoso gift search — A structured brief maps every stakeholder and what they have raised. Sendoso searches for a gift per person with individual context. Multi-threading a buying committee without manually reading every stakeholder's call history first is only possible when both platforms are running together.

• Sendoso call transcripts + Gong deal context — Personal signals from rep-level calls meet deal-level synthesis. The gift fits the person, not the pipeline stage. The note card references something specific from a real conversation. That combination is what separates a send that gets a response from one that reads like a campaign.

• Sendoso send analytics — Pull send performance against pipeline stage to show which touches drove deal movement. The ROI conversation happens in the same session where the sending happened. Budget defense becomes data, not intuition.

MCP Tools Reference

Sendoso MCP Server Tools

‍

Gong MCP Tools

Gong's MCP exposes two connection types. The MCP server lets external AI clients — like Claude and ChatGPT — query Gong data via natural language: deal context, account intelligence, and admin-configured briefs. The MCP client lets Gong's own assistant call external MCP servers. These workflows run in your preferred LLM or directly within Gong's own client.

For full tool details, setup instructions, and credit consumption guidance, refer to Gong's official documentation:

• About Gong MCP
• About Gong MCP server
• Create an integration to connect to the MCP server

Scenario 1: Re-engaging a Deal That Went Dark

Setup: A late-stage deal has been silent for three weeks. The champion stopped responding. The rep's next email will either reopen the conversation or confirm it is over. Before it goes out, they need to know what happened.

How the MCP helps: The Gong MCP opens the loop. The agent queries Gong for deal intelligence, asking what objections or concerns were raised and whether any competitor was mentioned in the last 30 days. That synthesis tells the rep what was on the prospect's mind when they went quiet. 

Sendoso then pulls Gong call transcripts for the champion's email, surfacing personal interest signals from the rep's own recorded calls. These are real things that came up in conversation, not job title data. 

With both inputs in context, the agent searches the Sendoso marketplace for a gift that fits the person. It drafts a note using the deal context as the framing and the personal signal as the specific touch. 

Sendoso's send execution generates a full preview — product, price, note text, recipient, delivery method — and surfaces it for review. No confirmation token gets passed until the rep has approved every detail.

Example prompt:

Using Gong, pull the deal for [DEAL NAME or OPPORTUNITY ID]: what objections or concerns came up in the last [30] days, and did any competitor get mentioned?Then using Sendoso, pull personal signal excerpts from my Gong calls with [CHAMPION EMAIL].Based on both, find [1-2] gift options under $[BUDGET] with note card support.Draft a short note that references something real from the deal or the person — not the pipeline stage.Show me the full send preview for [CHAMPION FIRST NAME, LAST NAME] with smart delivery enabled before you execute anything.

Expected output: The agent returns a Gong deal synthesis (blockers noted, competitive mentions flagged), personal interest signals from the rep's calls with the champion, a product recommendation with price and draft note card, and a full send preview. The rep reviews everything. The send does not execute until the confirmation token is passed.

Scenario 2: Timed Send Before a Strategic Meeting

Setup: A QBR is 48 hours away. The executive sponsor has been engaged but measured. The AE wants something to arrive the morning of, that signals they have been paying attention, not a gift that reads like a last-minute gesture.

Prerequisite: This scenario requires a pre-QBR brief type built in Gong by your admin before the workflow will run. The brief type defines what the agent surfaces — stakeholder context, open items, unresolved risks, etc. See How to create and manage brief types for setup guidance.

How the MCP helps: The Gong MCP starts with the pre-QBR brief your admin has configured. The agent generates that brief for the account, surfacing whatever your team defined as essential context such as open items, stakeholder roles, unresolved risks, agreed next steps. 

Sendoso then pulls Salesforce notes on the executive's record to surface CSM and AE observations, and pulls Gong call transcripts to find personal interest signals from recorded calls. 

With that full picture in context, the agent searches the Sendoso marketplace for an executive-appropriate gift and drafts a note that references something real from the relationship. Sendoso's send execution generates the preview with delivery scheduled for the morning before the QBR. The rep reviews the product, note text, and scheduled time before the send executes.

Example prompt:

Using Gong, generate a brief for [ACCOUNT NAME]: key themes, stakeholder dynamics,and agreed next steps.Then using Sendoso, pull Salesforce notes and Gong call signals for [EXECUTIVE EMAIL].Based on the brief context and personal signals, find [1] gift between $[MINIMUM] and $[MAXIMUM] appropriate for an executive-level send.Draft a short note that references something real from the relationship — not the deal stage, the person.Show me the full send preview with delivery scheduled for [DATE, TIME] before you execute anything.

Expected output: The agent returns the Gong account brief with stakeholder context, Salesforce and call-signal data for the executive, a product recommendation with note card draft, and a send preview with the scheduled delivery confirmed. The rep reviews before anything executes.

Scenario 3: Reaching the Full Buying Committee

Setup: A late-stage enterprise deal has five stakeholders. The champion is engaged. The CFO and IT lead have been on two calls but have not directly responded to any follow-up. The AE needs to reach all five without spending an afternoon reading through everyone's history.

How the MCP helps: The Gong MCP maps the committee. The agent generates a Gong brief on the account or deal, surfacing every named stakeholder, their stated concerns, and the themes that came up most across the engagement. That brief becomes the targeting input for Sendoso. 

For each stakeholder who was on a recorded call with the rep, Sendoso pulls Gong call transcripts to surface personal signals. For anyone not on a rep call, Sendoso enriches the profile by email to confirm role and seniority. 

The agent searches the marketplace for one gift per stakeholder, setting price ranges by level, and drafts an individual note for each person based on their specific context. 

Sendoso's send execution generates a separate preview per recipient. The rep reviews all previews together before passing any confirmation tokens. Nothing ships until every send has been individually approved.

Example prompt:

Using Gong, generate a brief for [ACCOUNT NAME or DEAL ID]: list every named stakeholder, what each one has raised or asked about, and the primary themes across calls.Then using Sendoso, pull personal signal excerpts for each of these emails: [EMAIL 1], [EMAIL 2], [EMAIL 3], [EMAIL 4], [EMAIL 5].For any stakeholder not on a recorded call, enrich the profile by email.Based on the stakeholder map and individual signals, find [1] gift per person under $[BUDGET PER PERSON], with a note draft for each that references something specific to them.Show me all send previews before you execute any of them.

Expected output: The agent returns the Gong stakeholder map with individual concerns noted, personal or enrichment data for each person, and a set of product recommendations with individual note card drafts. All previews surface for the rep's review before any confirmation token is passed.

Getting Started

1. Enable the Sendoso MCP. Your org admin enables the connection on a Core, Advanced or Enterprise Sendoso plan. Each rep connects their own seat through secure OAuth sign-in. Per-user authentication means everyone reaches only what their own permissions allow.

2. Enable the Gong MCP. A Gong admin generates a Client ID and Client Secret from the Gong Admin Center. Each rep authorizes with their own Gong login via OAuth 2.0. Server URL: https://mcp.gong.io/mcp. Gong MCP is rolling out in limited availability as of June 2026 — confirm access with your Gong admin before setup.

3. Add both servers to your AI client. In Claude or any compatible MCP client, connect both Sendoso and Gong as active MCP servers. Both need to be live in the same session for joint workflows to run.

4. Load the Sendoso workflow guide at the start of each session. Ask Sendoso to run get_workflow_guide for sending before the first multi-step workflow. It loads the correct step sequence from recipient research through send execution and stays in context for the session.