ABM Marketer: Sendoso MCP Playbook
Overview
Everyone on your Tier 1 list is getting the same seven-touch cold sequences, the same retargeting impressions, the same “personalized” messages. And while there are advancements in the quality of personalized outreach, you’re still stuck combatting the attention recession. In a world of digital fatigue, a well-timed physical send or eGift still breaks through, but only when it lands at the right moment with a message that fits the context. With the MCP you can act on intent signals the moment they surface, without spending time building lists or connecting tools.
The Sendoso MCP turns your AI assistant into a direct execution layer for ABM gifting. Whether it’s setting up signal based automations or following up after an important meeting, Sendoso’s MCP gives you the ability to act on those signals and activities instantly. No more waiting for ops to build a new integration, start a campaign creation flow, relying on someone else to remember to execute the send, and no more switching between tools.
Prompt your AI assistant once then let it handle research, product selection, note generation, and send execution through Sendoso’s MCP.
Why This Matters for ABM Marketers
- Recipient Intelligence → Pull Salesforce or CRM context and Gong call history on any contact before picking a gift. The AI surfaces what the person cares about so the note reads as informed, not generic. No manual CRM digging before every play fires.
- Marketplace Product Search → Find the right gift for any play in seconds. Search by intent theme, product type, or price range and get back curated results your budget already supports. No more "what do we send?" conversations before every play fires.
- Execute Send → Act on a buying committee signal in the same workflow session. The AI surfaces a send preview for your review before anything moves. Once you confirm, sends execute. No Sendoso login, no campaign creation flow.
- Get Recipient Link → Generate shareable gift links your reps can deploy at exactly the right moment. Stage the gift from your end, hand the link to the rep, and let them control the timing.
- Cancel Send → Stop a send before it ships when an account disqualifies, a contact is entered incorrectly, or a deal shifts. Pre-ship only. Balance is refunded automatically.
- Query Analytics → Pull send volume, delivery status, and engagement rates across your ABM program without opening another tab or building a report on the day of the QBR.
MCP Tools Reference
Recipient Intelligence
Gift Discovery
Gift Execution
Program Analytics
Scenario 1: The Intent Surge Play
Setup: Your intent data has flagged a batch of Tier 1 accounts entering active research stage this week. Multiple contacts across those accounts have been engaging with competitor content for two weeks. Your reps have been reaching out with no response.
How the MCP helps: You export the qualifying contacts from your intent platform and paste the list into your AI assistant. The assistant can enrich each contact to confirm title and seniority, then searches for one product that fits the intent play theme and price range. It prepares a batch send across all contacts with a single note template tied to the signal. You review the product and note before anything executes. Once you confirm, all sends fire in one session and you receive a send ID for each contact.
Example prompt:
My intent data flagged [X] Tier 1 accounts as entering active research this week.
Intent signal: [DESCRIBE: contacts researching what topic or category, for how long]
Find a [SEND TYPE: physical gift or eGift] between $[MIN] and $[MAX]
that fits a [THEME: productivity, professional development, etc.] play.
Contacts across all qualifying accounts:
- [FIRST NAME] [LAST NAME] | [COMPANY] | [TITLE] | [EMAIL]
- [FIRST NAME] [LAST NAME] | [COMPANY] | [TITLE] | [EMAIL]
- [FIRST NAME] [LAST NAME] | [COMPANY] | [TITLE] | [EMAIL]
Draft a note template for this segment that references [SPECIFIC CONTEXT: their
active evaluation timeline, research behavior, etc.] without naming specific
companies or competitors.
Before sending, show me the product, price, and note template. Once I confirm,
execute all sends and return a send ID for each contact.
Expected output: The AI surfaces one product with price, shows the note template for review, then generates individual send previews with confirmation tokens. After you confirm, sends execute across the full list and send IDs are returned.
Scenario 2: Post-Event Account Acceleration
Setup: You just ran a hosted executive roundtable that 11 of your top 30 target accounts attended. Nineteen registered accounts did not show. Your window to use event name recognition before it goes cold is 72 hours.
How the MCP helps: You paste your attendee and no-show lists into your AI assistant. The assistant prepares two send flows: a "thanks for joining" send for attendees with a meeting-focused note, and a "we missed you" send for no-shows with a content offer as the hook. You review and approve both groups before anything executes. Both batches fire in one session. You then use Query Analytics to check delivery status before reps begin follow-up calls, so they are reaching out when the package is in hand.
Example prompt:
I have two groups from [EVENT NAME] on [DATE].
Attendees: send a [SEND TYPE] between $[MIN] and $[MAX]
[PASTE LIST: First Name | Last Name | Email]
No-shows: send a [SEND TYPE] between $[MIN] and $[MAX]
[PASTE LIST: First Name | Last Name | Email]
Draft a note for each group:
- Attendees: reference [SPECIFIC TOPIC OR MOMENT FROM THE EVENT]
- No-shows: reference [CONTENT OFFER OR FOLLOW-UP HOOK]
Before executing, show me the product and a sample note for each group. Once I
confirm, run both batches and return all send IDs grouped by segment. Flag any failed sends.
Expected output: The AI surfaces the selected product and a draft note for each segment. After confirmation, both batches execute and send IDs are returned grouped by attendee and no-show. Failed sends are flagged with reason codes.
Scenario 3: Dark Account Re-Engagement — Rep Enablement
Setup: You have a list of strategic accounts that went dark in the last 30 days, all with open opportunities and significant pipeline. Reps have been following up with no response.
How the MCP helps: Rather than adding more emails to sequences that are not working, you stage a physical gift for each account and generate shareable links your reps can deploy at the right moment. Before searching for a product, the AI pulls Gong call history and Salesforce notes on each contact, surfacing personal signals your team already captured. It uses that context to write a personalized note for each send rather than a generic template. After you confirm the product and notes, sends execute and recipient links are returned grouped by account. Each rep gets the link for their account and context on when to use it.
Example prompt:
I have a list of [X] accounts that went dark in the last [X] days.
All have open opportunities in [DEAL STAGE] with [PIPELINE RANGE].
For each contact below, check Salesforce notes and Gong call history for any
personal signals I can use in the note card: interests, preferences, or recent
conversation context.
Contacts:
- [FIRST NAME] [LAST NAME] | [COMPANY] | [TITLE] | [EMAIL]
- [FIRST NAME] [LAST NAME] | [COMPANY] | [TITLE] | [EMAIL]
- [FIRST NAME] [LAST NAME] | [COMPANY] | [TITLE] | [EMAIL]
Find a physical gift between $[MIN] and $[MAX] appropriate for
[SENIORITY LEVEL: VP, Director, C-suite] contacts.
Use link delivery so each rep can share at the right moment.
Before sending, show me the product and a personalized note draft for each
contact based on what you found. Once I confirm, execute all sends and return
recipient links grouped by account so I can route each to the right rep.
Expected output: The AI surfaces available Gong and Salesforce context for each contact, then selects a product and drafts a personalized note for each. After confirmation, sends execute and recipient links are returned grouped by account. Each rep receives the link for their account with guidance on when to deploy it.
Getting Started
- Confirm your Sendoso plan. The Sendoso MCP is available on Core, Advanced, and Enterprise plans. On legacy plans, it is available on Plus, Pro, and Enterprise. Have your org admin enable MCP access in Sendoso account settings.
- Add Sendoso as a custom connector. In Claude Desktop, Claude Code, or any MCP-compliant client, add Sendoso as a custom connector. Authentication runs through OAuth 2.1 + PKCE via Auth0. Your token is scoped to MCP tool actions only and does not expose broader account permissions.
- Confirm your product catalog is funded. The MCP searches your org's marketplace catalog. Gift inventory and budgets still live in Sendoso. Before running a play, confirm your team balance is funded and price limits are set in account settings.
- Request beta access before testing. The Sendoso MCP is in request-based beta targeting a June 24 launch. There is no sandbox or demo environment available yet. Contact your Sendoso account team for beta access.
- Establish your rep handoff signal. The MCP returns send IDs and recipient links. Before scaling, agree with your rep team on how that signal gets to them: a message drafted by the AI, a task note, or a direct copy-paste from your prompt session. The follow-up call timing is the variable that determines whether the send converts to a meeting booked.
Supported at launch: Claude Desktop, Claude Code, and other MCP-compliant clients. Additional AI clients are being added. Contact your Sendoso account team for the current compatibility list.
Tool availability: Recipient Intelligence (enrich_profile, salesforce_search_profile, salesforce_account_details, gong_call_transcripts), Marketplace Product Search, Execute Send, Cancel Send, Get Recipient Link, and Query Analytics are all confirmed production tools available at launch.
See how leading B2B companies use Sendoso to fuel revenue
