Sendoso announced a request-based beta for its Model Context Protocol integration on June 24, 2026, allowing external AI agents to work with its gifting and direct-mail capabilities. The aim is to connect the information that prompts a send with the research, gift choice and follow-up around it. [S01]

A connection between revenue signals and physical sends

The launch named Demandbase, UserGems, Gong, Outreach, Clay and Warmly as founding integration partners. They contribute different parts of the workflow, from account intent and contact enrichment to conversation history and outreach coordination.

Scroll left or right to see all columns
A connection between revenue signals and physical sends

Stage

Intended function

Identify an opportunity

Use account, contact or engagement signals

Research and recommend

Combine available recipient context with gift options

Send

Execute a selected gift through Sendoso

Follow up

Connect delivery or redemption with the next sales action

For a revenue team, the attraction is continuity. A signal in one tool can inform a gift choice in another, and delivery can prompt a follow-up without the sender recreating the same context across multiple screens. That is a workflow proposition; the launch announcement does not establish a guaranteed improvement in conversion or sales. [S01]

A preview token is not the same as human approval

Later support documentation, updated August 19, describes a two-call sending process. A preview is generated first, followed by confirmation using a single-use token. The selected item, recipient and note are fixed at preview, and the service checks spending limits and available balance. [S02]

That documentation also identifies an important boundary: whether a person actually reviews the preview depends on the AI client's permission settings. The server can enforce the confirmation mechanism and spending controls, but those controls should not be described as proof that a human has read and approved every send.

For operators, this means reviewing both sides of the connection. Account limits govern what the service permits, while the agent client determines how execution is presented to a user. A team planning unattended campaigns needs to understand those settings before treating a successful tool call as an approved business action.

Access and rollout

The June launch offered access by request. Subsequent support material describes account enablement and eligibility for Core, Advanced and Enterprise plans. Because rollout labels in later release notes differ, the June beta date should not be read as a claim that every account received unrestricted access at launch. [S01] [S02] [S03]