The agent proposes. People approve. The person who owns the relationship sends. That is the whole design, and it is the difference between an agent for warm introductions and an AI SDR. A warm introduction is warm because a real person vouches for you. The moment software sends it for them, it is a cold email with a borrowed name on it.
Boomerang is the category example. Its agent, Rudy, reads the CRM, calendars, call recordings and Slack, spots when a deal needs a warm path, proposes who should ask whom, drafts the ask in the sender's voice, and tracks it to a booked meeting. Rudy never sends on anyone's behalf.
What is an AI agent for warm introductions?
It is the layer that sits between "we know someone at Acme" and a meeting on the calendar. Finding the buying committee is the easy part. The hard part is working out which of the hundreds of people across your executives, customer champions, investors, advisors and partners actually knows those buyers, which of them should make the ask, and when. Reps spend days on that in deal reviews, Slack threads and texts, and still miss most of the paths.
An agent does that work continuously and brings the answer to the rep. What it does not do is decide on anyone's behalf that a relationship should be spent. That decision stays with people, at three points.
Why a warm intro agent should never send
The warmth is the endorsement. A target opens an introduction because a person they know chose to make it. If the agent sends, nobody chose. The target can usually tell, and the connector's reputation takes the hit for an ask they never saw.
Relationships are spent, not used. A handful of well-placed introductions a quarter does more for a connector, and for your program, than a stream of reluctant ones. Only the connector knows whether this one is worth it: whether they know the target well enough to vouch, whether the timing is right, whether there is a conflict. Boomerang's own guidance to connectors is a single test: would the prospect be glad about this introduction tomorrow morning?
Declines are information. "I don't know them well enough" is the most common reason a connector says no, and it is exactly the signal the agent needs to route the next ask better. An agent that sends without asking never hears it.
For the mechanics of the email itself, see should the connector send the first email.
Should the connector send the first email, or me?
The connector. Their name in the From line is the credibility signal. Your name in the From line is one more stranger in the inbox, however good the copy.
The flow that works
- You draft a forwardable note and send it to the connector. In Boomerang, Rudy writes this draft in the connector's voice once they accept the request.
- The connector reviews it, adds a one-line personal note at the top ("Sarah, meet Alex"), and sends it to the target from their own account. Rudy never sends it for them.
- The target replies on the connector's thread, so all three of you are on the same email.
- The connector steps out with a short line ("I'll let you two take it from here") and you carry on directly.
Two mistakes to avoid
- Sending it yourself with the connector copied in. To the target this looks like a cold email with a name-drop. The connector has not vouched; they have only been copied.
- The connector rewriting it into a pitch. Extra commentary dilutes the ask. The connector's job is to vouch and forward. The substance is already in the note.
When to use double opt-in. Some connectors prefer to email the target first ("Open to an intro to Alex?") and forward only after a yes. It adds a step but protects the connector's relationship, so it is the better choice for very senior targets or relationships the connector is careful with. For peers and strong relationships, a direct forwarded intro is usually fine.
Whichever route, the decision and the send stay with the person who owns the relationship.
How it works, step by step
- Maps the ecosystem. Every Super Connector across four types: executives and employees, investors and advisors and board members, customer champions, and partners. None of them has to upload, install or agree to anything for the map to exist.
- Maps who each of them knows. More than 80 relationship signals, monitored continuously. See relationship signals for the families and how each path is graded.
- Watches the deals. CRM, calendars, call recordings and Slack, so it knows when a deal moves, goes single-threaded, or a champion changes jobs.
- Proposes, then waits. It flags the risk, lists the warm paths with the evidence behind each, and proposes who should ask whom. Nothing moves until the rep approves the plan.
- Routes to whoever owns the relationship. Board and investor asks go through the CEO or chief of staff. Customer asks go through the CSM or the executive with the most meetings on that account. Internal executives are asked directly.
- The connector decides. They see the target, the rep's reason, what the rep wants to discuss and the relationship context behind the path. They accept or decline, with a reason the rep can read.
- The connector sends. Accepting generates a draft in their voice. They edit it, copy it, and send it from their own inbox. The agent does not send the introduction to the prospect.
- It tracks it to the meeting. The request moves from Pending to Approved to Intro Sent to Completed, the agent nudges when it goes quiet, and reports the outcome back.
Who decides what
| Moment | What the agent does | Who decides |
|---|---|---|
| A deal needs a warm path | Flags it and lists the paths, with the evidence for each | The rep: act on it or not |
| Choosing the route | Proposes who should ask whom, and through which internal owner | The rep approves the plan, or picks a different path |
| Making the ask | Delivers the request, with the context behind the path | The connector accepts or declines |
| Sending the introduction | Generates a draft once the connector accepts. Sends nothing | The connector edits it and sends it, from their own account |
| After it lands | Tracks the reply, nudges, reports the outcome | The rep takes the meeting |
Respond or notice: what the agent starts on its own
There are two modes, and the difference is who starts the conversation, not who sends.
Respond. Something starts it. A rep asks in Slack which open deals have a warm path to the economic buyer, or a standing rule fires because a champion moved, a deal stalled above a threshold, or an account went single-threaded. The agent answers.
Sentient. Nothing starts it. The agent reads the deals, sees a champion go quiet or an account lose its only thread, and brings the path to a rep who did not know to ask.
In both modes the approvals above are identical. Noticing on its own is not sending on its own. On Boomerang, Respond is on the Team plan and Sentient is on Company; see pricing.
The rules it enforces
Each connector sets their own engagement preferences: minimum deal value, opportunity stage, contact seniority, channel and cadence, plus any exceptions. The agent filters every request against them before the connector sees it, so off-fit asks never arrive. A connector who needs a longer break can step back without their data being removed.
Two more rules protect the network. A contact cannot be requested twice while a request is in flight, so nobody is pinged twice about the same person and no target receives duplicate introductions. And the agent never turns a connector's network into a directory: it surfaces paths tied to an active request, not a list of everyone they know.
How it differs from tools that look similar
| Tool type | What it does | Who sends | Warm or cold |
|---|---|---|---|
| AI agent for warm intros | Finds the path, proposes the ask, drafts it, routes it, tracks it | The connector | Warm |
| AI SDR | Writes and sends outbound sequences at volume | The software | Cold |
| Sales engagement | Runs sequences a rep has written | The rep | Cold, sometimes name-dropped |
| Relationship intelligence dashboard | Shows who knows whom when someone searches | Whoever acts on it | Depends on the human |
| Warm intro drafting assistant | Ranks paths and writes a message when asked | The user | Warm, but not routed to the connector |
The last row matters because the gap is narrow. Several relationship tools now draft the message, and some add approval steps. What makes something an agent for warm introductions is doing all of it together: routing the ask to the person who owns the relationship, enforcing that person's preferences, holding a trackable request, and watching the deals in the background. For the wider field, see best warm introduction software.
Where the agent works
- Slack. In deal channels, answering in the thread you asked in, with links back to the record behind every answer. When a question is ambiguous it asks before it answers. Rudy for Slack.
- Any AI assistant, through MCP. Ask for a warm path from inside Claude or any client that supports a remote MCP server. Boomerang MCP server.
- The CRM. Warm paths on Salesforce and HubSpot account records, and relationship signal as fields in Salesforce, HubSpot and Attio.
When it is worth adopting
It depends on the network you already have, not your funding stage or headcount. A twelve-person company with a well-connected board has more to activate than a hundred-person company that has never asked a customer for an introduction. The practical threshold is enough connectors across enough of your target accounts that the paths stop being occasional and start being a channel. Starting with three to five engaged connectors beats a long list of people who never log in.
Admin setup takes about 30 minutes. You see warm paths the same day, and you can go live right after.
Bottom line
Judge an AI agent for warm introductions on two things: how much of your network it can see, and what it refuses to do. The first decides how many doors it finds. The second decides whether your board, customers and investors still want to open them next quarter.
Frequently asked questions
Does an AI agent for warm introductions send emails on my behalf?
A well-built one does not. On Boomerang, Rudy drafts the introduction, but the person who owns the relationship sends it from their own inbox, in their own voice. Accepting a request generates a draft; it does not send anything to the prospect.
Who approves a warm introduction before it goes out?
The rep approves the plan the agent proposes: which buyer, which path, which internal owner. When the ask goes through an internal owner, such as the CEO for a board member or the CSM for a customer, they approve it too. Then the connector who knows the buyer accepts or declines. Only then does the connector send the introduction.
Is an AI agent for warm introductions autonomous?
It works continuously in the background: it watches deals, maps relationships and can raise a path nobody asked about. It does not act autonomously on the relationship. Spending a connector's goodwill is always a human decision.
What is the difference between an AI agent for warm intros and an AI SDR?
An AI SDR writes and sends outbound email itself, which makes it cold by definition. An agent for warm introductions routes the ask through someone who actually knows the buyer, and that person sends it. One replaces the sender; the other finds the right one.
Can a connector say no?
Yes, and it is expected. There is no penalty for declining and no target acceptance rate. The connector gives a short reason, usually relationship strength, fit or timing, and the rep can try another path to the same person.
What does Sentient mode mean?
On Boomerang's Company plan, Rudy raises warm paths nobody asked about: a champion going quiet, an account losing its only thread. It changes who starts the conversation. It does not change who approves or who sends.
Can I use the agent inside Slack or Claude?
Yes. Rudy works in Slack deal channels and through Boomerang's MCP server in Claude or any client that supports remote MCP servers. MCP and API access are included on every plan.
Should the connector send the first email, or me?
The connector. Their name in the From line is what makes the introduction warm. You, or Rudy, draft a forwardable note; the connector reviews it, adds a line of their own and sends it from their own account. Rudy drafts, but never sends. Sending it yourself with the connector copied in reads as a cold email with a name-drop.
