By Shankar Ganapathy, Co-founder, Boomerang AI. Published November 5, 2026.
A warm intro program runs out of goodwill before it runs out of paths. The fix is an operating policy with four parts: who approves each ask, a cap on how often any one connector is asked, a cool-off window after each ask, and a weekly cadence that batches asks instead of firing them as reps think of them. Set those four once and your board members, investors and customer champions hear from you rarely, and only with asks worth their time.
This is the policy side. For who approves and who sends at the level of a single ask, see human in the loop for intro agents.
Why do intro programs burn connectors?
Because asks are free to the rep and expensive to the connector. When an agent or a spreadsheet surfaces 40 warm paths through the same investor, every rep wants to use them this week. Nobody sees the total until the investor stops replying.
We hear the same request on almost every implementation call: make sure the CEO or a board member is not asked for a hundred intros. One customer set a 45-day cool-off per connector before they sent a single ask. That is the right instinct.
What are the four controls?
The defaults are starting points from how our customers run programs, not benchmarks. Tune them per connector: some investors are happy to help monthly, some once a year.
Who should approve an intro request?
The person who owns the relationship with the connector, not the rep who wants the meeting. A rep can see the path. Only the owner knows whether this is a good week to ask.
- Customer champions: the CSM who owns the account approves, and asks in their own voice. Never direct from a rep.
- Board and investors: the CEO approves, and only above a deal size you agree in advance.
- Partners: your alliances lead approves.
- Your own team: the rep's manager approves, or nobody, if the connector is a peer the rep already works with.
How should caps and cool-off work together?
Caps limit volume. Cool-off limits clustering. You need both: a connector capped at one ask a month can still get two asks in the same week of two different months. A rolling cool-off window prevents that.
Three rules make them work in practice:
- Count every ask, not every intro. A declined ask still spends goodwill.
- Reset the clock on a decline, and lengthen it. A no is information. Do not ask again next week.
- Reroute instead of waiting. If the best connector is cooling off, check the second-best path through someone else before you queue the ask.
What does a weekly ask cadence look like?
- Monday: shortlist. Pull the accounts where a warm path matters this week: stalled deals, new target accounts, a champion who just changed jobs.
- Monday: pick one path per account. The strongest path whose connector is under cap and out of cool-off.
- Tuesday: approve in one place. Owners review the batch in one Slack thread or one 15-minute meeting. Approve, edit or decline.
- Tuesday to Thursday: owners send. From their own account, in their own words, one recipient per ask.
- Friday: close the loop. Tell every connector what happened with last week's asks. This is what earns the next yes.
What should you track?
How does Boomerang enforce this?
Rudy checks each connector's preferences on deal size, channel and cadence before an ask is drafted, picks who inside your company should ask, and routes it for approval. The relationship owner approves and sends from their own account; Rudy never sends on anyone's behalf. Super Connectors can answer requests in Slack with Accept, Decline or Needs Clarification, and rules can leave out whole categories, such as every open opportunity or every customer. See intro request orchestration and Rudy on Slack.
If you are not sure who should send a particular ask, try the free Who should send this? tool.
Frequently asked questions
What is an intro request cap?
An intro request cap is the maximum number of asks one connector receives in a period, such as one a month for a board member. It protects goodwill by making the total visible, so no single investor, executive or champion is asked dozens of times by different reps.
What is a cool-off period for warm intros?
A cool-off period is a rest window after a connector has been asked, or has declined, during which nobody asks them again. Thirty to 45 days after any ask is a common starting point, with a longer window after a decline.
Who should approve a warm intro request?
The person who owns the relationship with the connector approves it: the CSM for a customer champion, the CEO for board members and investors, the alliances lead for partners. The rep who wants the meeting proposes the ask but does not approve it.
How often should you ask a board member for an introduction?
Rarely, and only for deals that matter. Many teams cap board and investor asks at about one a month per person, above an agreed deal size, with the CEO approving each one. Tune the cap to each person's stated preference.
What should you do when a connector is cooling off?
Reroute before you wait. Check whether a second warm path through a different connector reaches the same buyer. If none exists, queue the ask for after the cool-off ends rather than asking early and spending goodwill.
.png)
