How to Decline an Introduction Request: 3 Texts
How to decline an introduction request without hurting the relationship: a decision table, three texts for the three real reasons, and what to offer instead.
By Brett Kaufman. 8 years using relationships to build sales pipelines, from political fundraising to a 7 figure business to running matchmaking for two communities. Over 1,000 introductions facilitated.
Here is how to decline an introduction request: answer within a day, give one true reason that protects the person they asked about, and offer one thing you can do instead. Almost every no falls into one of three cases: you do not know the target well enough, the target is overasked or protected, or the request is not ready.
Here is the scene. You get home from a mastermind dinner and there is a text from a searcher you sat next to. “Great meeting you. You mentioned you know the owner of that HVAC company in Tampa. Any chance you could connect us?” You do know him. He told you in confidence he might sell in two years. He also told you he gets three buyer calls a week and hates every one.
The easy answer is “sure, let me see.” That answer is the expensive one.
Why I say no more than people expect
I have facilitated over 1,000 introductions and I run matchmaking for two communities. The intros I regret are not the ones I declined. They are the yeses I should have turned down: the owner who took a call as a favor to me and never wanted it, the investor I asked one time too many.
Fred Wilson made the receiving side’s view plain in his post on the double opt in introduction. When someone wants an intro to him that he does not want, he writes: “I tell it like it is.” You owe the person asking the same honesty, and you owe it fast.
How to decline an introduction request in three parts
Every good no has the same three parts. It fits in one text.
- Speed. Answer within 24 hours. A slow maybe feels like a yes to the person waiting, and every day it sits, the no gets harder to send.
- One true reason that is about you. “I do not know him well enough to vouch for you” is about you. “He would never talk to someone like you” is about them. Only the first one is yours to say.
- One thing you can do instead. A better fit, a sharper ask, a later date. It turns the no into a next step and keeps the relationship moving.
Skip the apology paragraph. Forty words is plenty.
Should you say yes, redirect, or decline?
Use the ask itself to decide. Here is the table I would run every request through.
| What is true | Your move | What to offer |
|---|---|---|
| You know both sides and can write the why in one line | Say yes, then ask the target first | A double opt in intro |
| You met the target once and cannot vouch | Decline | Someone you do know who fits |
| The target has said yes to you a lot lately | Decline or delay | A date to ask again |
| The target is protected, such as an owner not on the market | Decline without naming why | A different route, or nothing |
| The ask is vague, no blurb, no clear reason | Not yet | A request for two lines on the deal |
| The asker ignored your last intros | Decline | Nothing, kindly |
If more than one row fits, the stricter one wins. More on screening at volume in how to make introductions at scale.
Text 1: when you do not know them well enough
This is the most common no and the easiest to send. It is true, it insults no one, and it points somewhere useful.
I only met Dana once, so I can’t put my name on it. Send me two lines on what you’re buying and I’ll think about who I know better who fits.
The second sentence matters. It tells the asker you are still on their side, and the two lines they send back show you whether a yes exists anywhere else in your phone.
Text 2: when the other side is overasked or protected
This is the owner in Tampa. You cannot say “he might sell in two years,” because that is his secret, not yours. You cannot say “he hates buyer calls,” because it makes him look bad. So you say less.
I’m going to hold off on that one. He’s asked me to keep new intros to a minimum for now. If that changes, you’ll be the first person I think of.
Everything in it is true. Nothing in it leaks. And “you’ll be the first person I think of” is a promise you can keep, as long as you write it down.
The same text works for a lender you asked twice this month or an investor who just closed a fund and is buried. Spread the asks. A yes person stays a yes person because you do not wear them out.
Text 3: when the request is not ready
Sometimes the fit might be real, but the ask is a single line with no context. You cannot forward “can you intro me to your banker friend?” to anyone.
Happy to think about it. Send me a short blurb I can forward as is: who you are, what you’re looking for, and why her. Then I’ll ask if she’s open.
This is a “not yet,” not a no. If they send a real blurb, you move to a double opt in. If they never send it, they answered for you. The warm introduction request template shows what a forwardable blurb looks like, and you can send them the link.
What should you never say when you decline?
- “Let me see what I can do,” when you already know the answer. It is a no with a six week delay.
- The target’s private situation. Not their sale plans, their fund timing, or their mood.
- “She’s not taking meetings with people like you.” Even if it is what she said.
- A yes you plan to quietly forget. That is how a connector ends up carrying intro debt, the promises that make you look like the person who does not deliver.
- A long apology. It makes the no sound bigger than it is.
What happens after you say no?
Log it. Who asked, for whom, the date, and which text you sent. Two things come out of that log.
First, you answer consistently. When the searcher asks again in March, you know what you said in October and whether anything changed. Second, you keep your “first person I think of” promises. The day the Tampa owner says he is ready to talk, you want that searcher’s name in front of you, not lost in a text thread from last fall.
This is one piece of the super connector’s operating system: capture, context, an intro ledger, and a daily list. The no is part of the ledger too.
Where declining breaks at volume
None of this is hard for one request. It is hard for the six you got after a single event, half of them by text at 11pm, two of them for the same lender. The ones you do not answer that night become slow maybes. The promises inside your noes, “you’ll be the first person I think of,” live nowhere.
The system that holds the yeses and the noes
That is part of why I built FRONT OF MIND. After the dinner, say a name and a sentence out loud, “searcher wants the Tampa HVAC owner, holding off, revisit if he is ready,” and it is filed under the event. When the reason changes, the person shows up in your 10 minutes for today with a one line reason why today and a drafted text, 40 words max. Nothing sends without your tap, and it learns from your edits.
When you need a better fit to offer instead, ask Liala “who do I know that is an SBA lender” and get the right people with why. Intros to make this week come with dated proof on both sides, so your yeses rest on something current.
It runs in your phone browser, and you can save it to your home screen. Your contacts are encrypted. No one on our team looks at them. Export and delete anytime.
Start free with your first 25 contacts and 1 intro, and see who comes up first.