Sendoso + 6sense: AE and BDR MCP Playbook

Overview

Buyers ignore most of what lands in their inbox. Reply rates are flat, calls go to voicemail, and the same templated sequence arrives from every vendor. A real object at their door with their name on it and a note that proves someone paid attention still gets noticed. That is why 82% of revenue teams plan to maintain or increase their gifting budget, according to Sendoso's 2026 Digital Fatigue Report. Reps feel this first.

Marketing already runs account-based plays off 6sense. The gap sits between that work and the rep. A BDR sees a 6QA alert, then has to find the right contact, check whether marketing already sent something, pick a gift in a separate tool, and write the follow-up. An AE with a stalled deal goes through the same steps. An AI assistant can do the research and write the note, but it cannot put anything in a buyer's hands.

When Sendoso and 6sense are connected to the same assistant session, a rep can do all of it in one conversation. 6sense shows which accounts are active and who works there. Sendoso shows what has already been sent, finds a gift that fits the person, and sends only after the rep approves the preview. The same assistant drafts the follow-up email. The 6sense connection is read-only, and the team's send price limit is enforced on the Sendoso side. Each rep signs in individually, so each person only reaches what they are allowed to.

Why This Matters for AEs and BDRs

• Sales account and people insights (6sense) gives a rep an account summary, the people at the account, and recent company news in one ask. This gives time back. Research that took several tabs before the first touch happens in a single conversation.
• query_analytics_table (Sendoso) with 6QA trend analysis (6sense) shows what marketing already sent to an account before a rep reaches out. This closes the handoff gap. The rep avoids a repeat gift and can reference the one that already landed, which helps pipeline.
• call_transcripts with marketplace_product_search finds a personal detail from past Gong calls and matches a gift to it. A gift tied to the person, not the title, is what earns a reply.
• execute_send shows the exact price and gift in a preview before anything is sent, and the team's price limit applies automatically. This protects against the off-brand send or the overspend that reps and their managers worry about.
• Website activity (6sense) with salesforce_search_profile (Sendoso) shows when a quiet account becomes active again and what the last logged activity was. That is the moment to restart a ghosted deal, and the numbers can be proven afterward.

MCP Tools Reference

Sendoso MCP Tools

The Salesforce and Gong tools need those integrations connected. If they are not, they return a not-connected message, and enrich_profile and pdl_search_profile cover the recipient research.

6sense MCP Capabilities

6sense does not publish individual tool names. The assistant selects tools automatically, so these are listed as 6sense documents them.

6sense access follows each rep's license, role, and individual authorization. Reps without Sales Intelligence do not receive the sales-focused capabilities. All 6sense operations are read-only. Contact-level activity is limited to known CRM records. 6sense's own setup guide notes that access is governed by beta enrollment and organization settings, so confirm yours before you start.

Scenario 1: Check what marketing already sent, then make the first touch

Setup: A BDR gets a new 6QA account in their territory. Marketing may have already sent a gift or run a play there. The rep wants to open with something relevant and avoid repeating it.

How the MCP helps:

1. 6sense: returns an account summary, the key people, and recent company news for [ACCOUNT NAME].
2. Sendoso: runs query_analytics_table on recipient_company for [ACCOUNT NAME] over the last [NUMBER] days to show campaign, send status, and whether anyone engaged.
3. Sendoso: runs salesforce_search_profile on [CONTACT NAME] to check the last logged activity.
4. Sendoso: if marketing has not sent to this contact, runs marketplace_product_search under [BUDGET], then execute_send step 1 with an address confirmation email. You review the preview. Step 2 passes only the token and sends.
5. Assistant: drafts the follow-up email for your sequence, referencing the gift or the earlier send.

Example prompt:

Expected output:

Scenario 2: Multi-thread a Decision-stage deal before the next call

Setup: An AE has an open opportunity with one engaged champion. The account is in the Decision stage in 6sense, and the AE needs a second and third stakeholder to respond before the next call.

How the MCP helps:

1. 6sense: returns an account summary, people associated with the account beyond the current contacts, and recent engagement for known contacts.
2. Sendoso: runs salesforce_account_details for the open opportunity and contacts, and salesforce_notes for context from earlier conversations.
3. Sendoso: runs enrich_profile to confirm title and seniority for each new stakeholder, and call_transcripts for personal interests on anyone who has been on a call.
4. Sendoso: runs marketplace_product_search under [BUDGET] for each person, then get_product_details to confirm variants and ship-to country.
5. Sendoso: runs execute_send step 1 for each stakeholder with send_at set to arrive before [DATE]. You review each preview, then step 2 sends.

Example prompt:

Expected output:

Scenario 3: Restart a ghosted deal when the account becomes active again

Setup: A deal has gone quiet for weeks. 6sense shows the account visiting your site again. The AE wants a touch that gets a reply without asking for an address and reopening a cold thread.

How the MCP helps:

1. 6sense: shows website activity at [ACCOUNT NAME] over the last [NUMBER] days, the pages viewed, and engagement from known contacts.
2. Sendoso: runs salesforce_search_profile and salesforce_notes to show the last logged activity and what was discussed.
3. Sendoso: runs call_transcripts for a personal detail, then marketplace_product_search under [BUDGET].
4. Sendoso: runs execute_send step 1 with smart delivery enabled, so you do not need to ask for an address. You review the preview, then step 2 sends.
5. Sendoso: if the contact replies before the gift ships, cancel_send stops it and refunds the balance.

Example prompt:

Expected output:

Getting Started

1. Confirm access. Sendoso needs an eligible plan (Starter, Core, Advanced, or Enterprise), admin enablement, and each rep connecting their own Sendoso seat. 6sense needs Sales Intelligence access for the people and account capabilities, and each rep authorizes individually. Call transcripts need your Gong integration.
2. Connect Sendoso. Have your admin enable the connection, then connect Sendoso to your AI assistant through the secure sign-in. Sendoso setup details.
3. Connect 6sense. In Claude, go to Settings, then Connectors, then Browse, search for 6sense, select Connect, sign in, and select Allow access. 6sense setup guides.
4. Check both connections in one session. Ask: "Using 6sense, what is the current buying stage and top intent keywords for [ACCOUNT NAME]?" Then ask the assistant to use Sendoso to confirm which user and team you are signed in as.
5. Run Scenario 1 on one account. Ask the assistant to load the Sendoso sending workflow guide first, then paste the prompt. Review every proposed gift and message before you confirm.

Sendoso's MCP is generally available on eligible plans. Start with one account in your territory this week.