To respond to an introduction email, thank the connector, acknowledge the other person and make the next step easy. A useful reply explains why the conversation is relevant without repeating your whole background.
If you requested the introduction, take responsibility for moving the conversation forward. If you are receiving the request, you can accept, suggest a narrower exchange or decline. An introduction is an invitation, not an obligation.
Who should reply first?
Choose the reply that fits your role
| Your role | What to do | What to avoid |
|---|---|---|
| You asked for the introduction | Thank both people and offer a specific next step | Waiting for the connector to schedule everything |
| You are the person being approached | Say whether the subject and timing work | Agreeing to a vague call out of politeness |
| The introduction is unexpected | Clarify the reason before sharing more information | Assuming consent or forwarding private details |
| The fit is wrong | Decline or redirect briefly | Inventing interest or a future commitment |
Fred Wilson’s double-opt-in approach is useful before an introduction is made. As the recipient, respect that same choice: check the actual ask instead of assuming that being copied means someone has agreed to help.
Example: you requested the introduction
Fictional example: a founder wants to learn about a buyer’s workflow. The founder is not asking for investment or pretending a research conversation is a product demo.
Thanks for connecting us, Ari.
Hi Noor, it’s good to meet you. Ari mentioned that you have experience coordinating multi-location operations. I’m researching how teams handle last-minute scheduling changes and would value your perspective.
Would a 20-minute conversation next week be useful? I can work around your availability. I’m also happy to send two questions by email if that is easier.
Thanks,
Sam
The message gives Noor a reason to respond and a lower-effort alternative. It does not ask Noor to inspect a deck, visit a website and propose times before understanding the purpose.
Example: you are accepting the conversation
Thanks, Ari, and nice to meet you, Sam.
The scheduling question is relevant to work I’ve done. I’m happy to compare notes for 20 minutes. Tuesday afternoon or Thursday morning would work for me. Could you send a short outline of the two questions you most want to discuss?
Best,
Noor
If the connector does not need to remain involved, say that you will coordinate directly. Move them out of the scheduling thread thoughtfully rather than continuing to copy them on every message.
Example: the introduction is not a fit
Thanks for the introduction. Sam, I’m not the right person for scheduling procurement, and I don’t want to send you in the wrong direction. I can’t recommend a current contact, but I hope you find someone closer to that work.
A concise no is more helpful than an enthusiastic reply that never produces a conversation. Do not volunteer another person’s contact details without considering their permission.
What should happen after the reply?
Prepare for the agreed conversation and record the actual next step. Yale’s networking guidance distinguishes learning conversations from job offers; the broader lesson also applies here. A conversation can be valuable without becoming a sale, referral or commitment.
Finta CRM can keep the relationship context and follow-up together. After a useful meeting, close the loop with the connector without sharing confidential details. For the earlier stages, read the Warm Introduction Playbook and how to introduce two people by email.
