Etiquette
How to Receive a Warm Introduction (and Preserve the Connector Relationship)
Most professional networking advice tells you how to ask for introductions. Almost none of it tells you how to receive them. The recipient’s behaviour (how quickly they respond, how they approach the first meeting, whether they close the loop) shapes the connector’s future routing in ways that compound over years.
The asymmetry most recipients miss
When someone introduces you to a professional contact, you are the beneficiary of their social capital, but you are also, in a practical sense, a test of their judgment. Connectors who make introductions are making a claim about the value of connecting two people. How you respond teaches them whether that claim was well-placed.
The feedback loop is slow and silent. No one calls out a recipient who responds poorly to an introduction. The consequence is subtler: the connector routes fewer introductions to them over time, without ever making a deliberate decision to do so. Understanding this asymmetry, that the recipient controls something that affects the connector’s future behaviour, is the starting point for receiving introductions well.
The connector’s reputation is on the line, not yours
When a connector introduces two people, they are making a claim: this person is worth your time. That claim travels with the introduction. If the recipient ignores the message, delays responding for a week, or treats the first meeting as an unsolicited pitch, the connector does not observe this neutrally. They file it. Most connectors do not call out recipients who handle introductions badly; they simply route fewer introductions to them in the future. The feedback is silent but cumulative. A recipient who responds slowly and never closes the loop gradually falls out of the circles where introductions circulate, not by any visible exclusion but because the people who could make those introductions have quietly learned that the routing does not land well.
Schmitt, Skiera and Van den Bulte’s research on referred customers found that the trust transfer mechanism central to warm introductions depends on the referring party’s confidence that the person they are introducing will reflect well on them. Connectors who lose that confidence in a recipient (through slow responses, poor meeting conduct, or the absence of any follow-up) become less likely to make introductions over time. The recipient who handles a single introduction badly is not making an isolated social error; they are adjusting the connector’s future behaviour.
Receiving well is a skill, and most professionals have never been taught it
Most professional networking advice is addressed to the person seeking introductions: how to ask, how to brief the connector, how to follow up. Almost nothing is addressed to the recipient. The assumption seems to be that receiving an introduction is passive: you respond or you do not, and little else is required. The assumption is wrong.
Handling an introduction well (responding promptly, acknowledging the connector correctly, approaching the first meeting with the right frame, and closing the loop afterward) is a practised skill that most professionals treat as an afterthought. The consequences of handling it badly are slow to appear and easy to misattribute. Receiving well is also, straightforwardly, in the recipient’s interest: the professionals who handle introductions well receive more of them, because the connectors in their network have learned that routing introductions to them is productive.
The 48-hour response window
Response time is the most visible signal a recipient sends. The 48-hour threshold is not arbitrary: it reflects the point at which a missing response begins to read as a signal rather than as inbox backlog.
1. Why 48 hours is the meaningful threshold
An introduction that arrives by email is, for most recipients, one message among dozens or hundreds. The connector who made the introduction knows this. What they are also watching, consciously or not, is whether you respond within a reasonable window. Forty-eight business hours is roughly the point at which a response that has not arrived begins to read as a signal rather than as inbox backlog. Before 48 hours, the connector can reasonably assume you are busy. After 48 hours, they begin to wonder whether the introduction landed, whether the recipient is interested, or whether their social capital was well spent.
The 48-hour threshold is not a rigid rule, and most professionals understand that some weeks are genuinely overwhelming. What matters is the pattern. A recipient who consistently responds within a day or two signals something different to connectors than one who consistently takes a week. The signal is about professional judgment and relationship investment, not about the specific introduction.
2. What a slow response actually communicates
The practical effect of a slow response is to place the connector in an uncomfortable position. They have made an introduction that apparently went nowhere. They do not know whether the recipient received the message, whether they are interested, or whether something went wrong. In many cases, the connector will never find out: the introduction simply disappears into silence. What they learn from this experience is that introductions to this recipient are uncertain. The next time they encounter someone relevant, the memory of the silent thread will register, even if it does not register consciously.
Research on professional responsiveness and credibility consistently finds that response time is used as a proxy for respect and engagement, not because a slow response is necessarily disrespectful but because it is visible in a way that other signals of engagement are not. A 2023 study of professional email behaviour found that initial response time was one of the strongest predictors of whether a relationship was subsequently viewed as active and reciprocal by the other party, independent of the quality of the message when it arrived. Responsiveness signals that you value the connection, and the connector who made it.
3. How to handle an introduction when timing is genuinely bad
Sometimes an introduction arrives during a period when a conversation is genuinely not possible: a product launch, a family emergency, a concentrated deadline. The right move is not to wait until the timing improves; it is to respond immediately and acknowledge the reality. A short note along the lines of "grateful for the introduction. I am in the middle of a concentrated period right now but would love to find a time in [two to three weeks]; I will be in touch then" does two things. It closes the connector out of the uncertain silence (they know the introduction landed). And it gives the recipient a self-imposed deadline that is far more likely to produce an actual follow-up than an intention formed in the middle of a busy week.
The note to the connector can be separate, or embedded in the same thread with the recipient on the thread. Either way, the connector should hear from you within 48 hours, even if the meeting itself is further out.
The BCC protocol from the recipient’s side
Most introductions arrive as three-party email threads. The recipient’s first reply has two audiences, two jobs, and a specific structure that most people improvise rather than design.
The structure of the first reply
A warm introduction typically arrives as a three-party thread: the connector, the person being introduced to you, and you. Your first reply has two audiences and requires two things. First, acknowledge the connector specifically, not with a generic "thanks for the intro" but with something that signals you understood what they did and why it was a considered act. "I know you’re careful about who you connect, so I appreciate you thinking this was the right fit" communicates differently from a generic courtesy. Second, address the other person directly and move the conversation into its next phase: propose a time, ask a specific question, or suggest a format for the conversation.
After this first reply, move the connector to BCC with a note explaining the move. "Moving you to BCC. Will report back" is enough. Some recipients copy this into the reply itself; others send a separate short message to the connector. Either approach works. What matters is that the connector does not spend the next two weeks watching an email thread they were never meant to be on.
The acknowledgment the connector actually needs
The acknowledgment that lands well is specific to what the connector did, not generic. "Thanks for thinking of me" is polite but lightweight. What the connector wants to know is that their judgment was sound: that the introduction was warranted, that the recipient treated it seriously, and that the connector’s reputation with the recipient was not spent on something that went nowhere.
A specific acknowledgment addresses this directly. It might reference the shared context ("I know you’ve worked with them for a long time, so I take this recommendation seriously") or the connector’s particular knowledge of the recipient’s situation. The goal is to signal that you understood this was a deliberate act, not a reflexive one, and that you are approaching it accordingly.
What not to put in the first reply
The first reply to a warm introduction is not the place for a detailed pitch, a CV, a product overview, or an extensive professional biography. Those things may be relevant, but they belong in the conversation, not in the opening message. A first reply that leads with a sales pitch or an extensive professional history immediately signals to both the connector and the recipient that you have misread the nature of the introduction. The introduction was a warm entry into a human conversation; a pitch in response to it retroactively makes the introduction feel like a sponsored referral to a sales process.
Keep the first reply short. Three or four sentences: acknowledge the connector, say something briefly personal or relevant about why the conversation is worth having, and propose a next step. The conversation itself can carry the professional substance.
Framing the first meeting
The first meeting after a warm introduction is where most recipients make their most consequential error. The frame they bring to the conversation is more important than the content of it.
Why the meeting frame matters more than the meeting content
The most common mistake recipients make in a post-introduction first meeting is entering it as a pitch. The connector introduced two people; the recipient treats the first meeting as an opportunity to explain their product, service, or value proposition at length. This is not simply ineffective. It actively degrades the connector’s trust in the recipient as a routing destination.
Connectors calibrate based on what they hear from the people they introduce. If the recipient’s company colleagues, customers, or mutual contacts observe that the recipient consistently converts warm introductions into sales presentations, the connector’s network learns this and adjusts accordingly. The professionals who receive the most introductions over time are the ones whose first meetings are consistently described as genuinely useful conversations, not because they suppressed their professional interests but because they approached the meeting as a two-way exchange rather than a captive audience.
What the first meeting should establish
A productive first meeting after a warm introduction establishes three things, in roughly this order. First, whether there is genuine common ground: shared professional context, a relevant problem, a mutual interest that makes future contact worthwhile. Second, what the other person is working on and where they are seeing friction or opportunity. Third, whether there is anything specific you can do for them, offer to them, or connect them with. Now, not in some vague future. The third element is the one most recipients skip, because they are focused on what they want from the meeting rather than what they can give.
Recipients who consistently close the first post-introduction meeting by offering something (an introduction of their own, a relevant article or resource, a connection to a third person who could be useful) are the ones who connectors describe as "good at being introduced to." The description is shorthand for something more specific: the meeting produced value for the other person, which reflects well on the connector who made it possible.
The follow-up that distinguishes recipients connectors route to again
After the first meeting, the recipient’s follow-up should do two things. A message to the person they met: a short note that references one specific point from the conversation and proposes whatever the next step is, or acknowledges that there is no immediate next step but leaves the door open clearly. And a message to the connector: a short update that tells them what happened. "We had a great call, and it looks like there might be something worth exploring" or "good conversation, probably not the right timing right now but I’m glad we spoke" both work fine. The content of the update matters less than the act of giving it.
Connectors who receive updates after they make introductions make more introductions to the people who give them. The mechanism is simple: the update confirms that the connector’s judgment was sound, that the introduction was taken seriously, and that the social capital they invested was respected. Connectors who never hear what happened from their recipients gradually make fewer proactive introductions, not as a deliberate decision but because the feedback loop that confirms the value of making introductions has been cut.
Deciding whether to accept
Accepting every introduction reflexively is not the right approach. Evaluating whether an introduction is worth accepting, and declining gracefully when it is not, is part of receiving well.
How to evaluate an introduction before accepting it
Not every introduction is worth accepting. A connector with poor judgment, a misaligned professional context, or an unclear rationale for the introduction is a real pattern, and accepting every introduction reflexively can produce meetings that cost time without producing anything. The evaluation should happen before the meeting, not after it.
The relevant questions are: Is the connector someone whose professional judgment you trust? Does the person being introduced have a genuine potential relevance to your current work or goals? Is the rationale for the introduction legible? Does the connector’s message make clear why they thought this connection was warranted? If all three answers are yes, accept. If one is unclear, you can often clarify with the connector before accepting. The evaluation is a matter of professional discretion, not gatekeeping. The goal is to ensure that the meetings you take are ones where you can contribute something, not only extract something.
When a proposed introduction is premature or misaligned
Some introductions arrive too early in a relationship to be useful. A connector who introduces you to a potential customer before you are ready to have a meaningful conversation, or to a potential partner before the context for a partnership exists, is well-intentioned but poorly timed. The right move is not to decline the introduction outright, but to ask the connector for a short delay and a specific reason: "I would love to meet them. Would it be worth waiting until [specific event] so I have something concrete to share?"
The reframing acknowledges the connector’s judgment while introducing a timing condition. It also signals that you are thinking about what a good meeting would require, which most connectors find more credible than either a flat acceptance or a vague delay.
Declining gracefully
A well-handled decline preserves the connector relationship and leaves the door open for a future introduction. A poorly handled one closes both.
How to decline without losing the relationship with the connector
Declining an introduction is uncomfortable because it appears to reject the connector’s judgment. Done badly, it does exactly that. Done well, it does something different: it signals that you take introductions seriously enough to decline the ones that are not the right fit, which is actually the behaviour connectors want in the recipients they introduce to.
The key is the reason you give and who you give it to. A direct "no, I don’t want to meet them" is almost never the right phrasing: it closes the connector’s options and makes the introduction feel like a social miscalculation. Better: "I appreciate you thinking of me. The timing is not quite right for me to take on [relevant context], but I’d love to reconnect with them in [specific future scenario]." This gives the connector a reason that is about circumstances rather than judgment, a path forward, and a signal that you are not dismissing their recommendation.
What to say to the person being introduced to you, if the connector has already made the introduction
If the connector has already made the introduction before you had a chance to decline, the situation is more delicate. The introduction has landed; the person on the other side now knows that a connection was made. Ghosting at this point damages both the connector’s reputation (their introduction was met with silence) and the recipient’s (their non-response is visible).
The right approach: reply to the thread, acknowledge the connection, and be honest that the timing is not right. "Thanks so much for connecting us. I’m in a concentrated period right now and can’t do justice to a proper conversation. I’ll keep [name] in mind as a contact for the future." This is not a commitment to a future meeting; it is an honest acknowledgment that closes the thread gracefully without leaving the connector holding a silent introduction.
Closing the loop with the connector
The loop-close is the most consistently neglected step in receiving a warm introduction, and the one with the most durable effect on the connector’s future routing.
What to tell the connector, and when
Most recipients never tell the connector what happened. The introduction was made; the meeting may or may not have occurred; the thread went quiet from the connector’s perspective. This silence is the most common failure in the recipient role, and it is also the easiest to fix. A single sentence, sent within a week of the meeting, is sufficient: "We had a good conversation. Looks like there might be something worth exploring" or "appreciated the intro, glad we had the call even if the timing wasn’t perfect." The update costs almost nothing and produces a meaningfully different outcome in the connector’s future willingness to route introductions.
Schmitt, Skiera and Van den Bulte’s research on the persistence of referred customer relationships found that the underlying mechanism is trust calibration: the referrer adjusts their future behaviour based on how well their referrals land. For connectors, the adjustment works the same way. Recipients who close the loop are not just being polite; they are giving the connector the feedback that makes them more likely to route future introductions.
When something significant happens: the second update
The first update after the meeting is a courtesy. If something significant develops from the introduction (a collaboration, a project, a hire, a deal, a long-term professional relationship), a second update months or years later is a categorically different kind of message. It confirms that the connector’s social capital was spent well; it closes a loop the connector may not even have been tracking consciously; and it tends to be received as one of the more pleasant surprises in a connector’s professional life. Most connectors who make introductions never hear whether anything came of them. The few who do hear, specifically and concretely, describe the experience as one of the more rewarding parts of having a useful professional network.
A short note, whenever the significant moment arrives: "I wanted to let you know that the intro you made to [person] a year ago led to [outcome]. I’m grateful." Nothing more is required.
Frequently asked questions
What if I genuinely do not have time to respond within 48 hours?
Send a brief note immediately, even one sentence, and set a specific follow-up date for yourself. "Grateful for the intro. I’m in a dense period this week; I’ll follow up properly on [day]." This closes the connector out of uncertainty (the introduction landed), gives the recipient a clear signal of your interest, and creates an external commitment that is far more likely to produce an actual follow-up than an intention formed in the middle of a busy week. The important thing is that the connector hears from you within 48 hours, even if the meeting itself is two or three weeks away.
Should I do research on the person being introduced to me before responding?
Yes, briefly. You do not need to spend an hour on this. A few minutes on their LinkedIn, their company website, or any recent public work they have done is usually sufficient. The reason is practical: a first reply that references something specific about the other person ("I noticed you’re working on [X] and I’d love to hear more about that") lands significantly differently from a generic acknowledgment. It signals that you treated the introduction as a deliberate act, not a routine calendar item. The research also helps you evaluate whether the introduction is genuinely relevant before you commit to a meeting.
How should I handle it if the first meeting goes poorly?
Tell the connector the truth, briefly. Not a detailed account of what went wrong, but an honest acknowledgment: "good to finally connect. Probably not the right fit right now, but glad we had the conversation." This is more useful to the connector than silence (they know the meeting happened and can calibrate their future routing) and more respectful than a false positive ("great meeting, lots of synergy"). Connectors who receive honest feedback, even mildly negative feedback, about their introductions adjust their routing more accurately than connectors who receive only silence or false enthusiasm.
Is there a way to decline an introduction that preserves the option to meet later?
Yes. Tie the decline to a specific future condition rather than a general unavailability. "I’d love to meet them. Can we time it for after [specific event or period] when I’ll have more to bring to the conversation?" This signals genuine interest, gives the connector a concrete path forward, and creates a natural follow-up point. The condition should be real, not vague: "sometime later this year" is not a condition that tends to produce a rescheduled introduction.
How does LetsBridge handle the recipient side of introductions?
On LetsBridge, both sides of an introduction consent before it is made: the person seeking the introduction, the connector, and the recipient are all involved in the process before any contact information is shared. This means recipients on LetsBridge are never surprised by an introduction they did not consent to, and can evaluate the relevance and timing of an introduction before committing to it. For connectors, the platform provides structure for managing introduction requests and tracking what comes of them, so the loop-close that most introductions never receive happens as part of the platform’s design rather than as an afterthought.