An Introduction Should Not Spend Another Person’s Availability
Connecting two people is generous only within the offer each person has actually made. A useful introduction distinguishes contact, a conversation and an obligation.

Inside this article
01The connector should not make the appointment on someone else’s behalf ↓02Ask a question that can receive a private refusal ↓03A short conversation is not an open-ended advisory role ↓The connector should not make the appointment on someone else’s behalf
Consider a hypothetical introduction between a friend seeking advice and an acquaintance with relevant experience. The connector writes that the acquaintance will be delighted to help, copies both people and suggests they arrange an hour together. The introduction has already made several promises: interest, willingness and time. Only one of the people described has actually been asked.
This essay proposes a standard for personal introductions, rather than reporting research about networking behaviour. A connector should be careful about the difference between opening a possible conversation and assigning someone a contribution. The value of knowing two people does not include the authority to decide what either owes the other.
Ask a question that can receive a private refusal
Before connecting the two, the introducer could send a short account of the request: who is asking, why the connection might be relevant and what kind of conversation is being proposed. The acquaintance can then decide without having to decline in front of the person seeking help. That private answer should remain a real answer.
If they decline, the connector need not relay the reason or invite the requester to negotiate around it. A simple account that the introduction is not available can preserve both dignity and privacy. The connector should also avoid promising the requester a future opportunity that nobody offered. A courteous refusal does not need to be turned into an indefinitely postponed acceptance to make the exchange feel generous.
A short conversation is not an open-ended advisory role
Suppose the acquaintance agrees to a brief introductory call. The introduction should communicate that scope accurately. It should not describe a mentor, adviser, collaborator or advocate unless that role has been accepted. Those terms can imply a continuing relationship where the person intended only one conversation.
The requester should be able to prepare within the actual offer. A clear description lets them choose the question that matters most and understand what remains outside the arrangement. It also gives the acquaintance a natural ending. The call can conclude without either person having to invent a new obligation merely because the connector used expansive language. A modest offer stated truthfully is more useful than a grand promise that someone else must later reduce.
Do not use praise as an invoice for future help
An introducer may want both parties to feel valued. Describing someone’s relevant work can explain why the connection makes sense. Declaring that they always help everyone, never say no or can solve any problem can quietly make refusal seem inconsistent with the identity just presented.
The introduction should identify relevance without prescribing generosity. In the fictional case, it could say that the acquaintance has experience with a particular kind of project and has agreed to discuss one initial question. That is sufficient. The connector does not need to sell their willingness by assigning a personality they must now maintain. Specificity also protects the requester from expecting expertise or access that the person never claimed to provide.
Contact details should follow the permission actually given
The connector should establish how the people want to be connected. Permission for an email introduction should not automatically become permission to distribute a private number, add someone to a large group or introduce several other people. Each changes the audience or the form of access.
A useful practical arrangement lets the person select the channel and the amount of context shared. If an explanation contains personal information, the introducer should ask whether it belongs in the message. The goal is an appropriate introduction, not the most complete possible account of either person’s circumstances. Relevance should guide the detail. Knowing something privately is different from being authorised to use it as persuasive background in another person’s request.
An introduction is not an endorsement of every future proposal
Two people may go on to discuss a project, a purchase or a collaboration. The original connector should not let the introduction imply that they have evaluated those later terms. Equally, the requester should not borrow the connector’s reputation to suggest a guarantee that was never given.
Where the possibility of confusion is material, the introduction can state its limited purpose in ordinary language: I thought a conversation might be useful; you should each decide whether the fit is right. This does not require making the message suspicious or defensive. It simply keeps the relationship between the parties theirs to form. The connector has supplied a route to meet, rather than certified the outcome of a conversation that has not yet occurred.
Leave the bridge without managing every crossing
After making the introduction, the connector can let the two people decide how to proceed. They need not demand updates, press the acquaintance for an answer or ask the requester to report whether sufficient help was provided. Those actions could extend an already completed introduction into informal supervision of someone else’s generosity.
CYPAPER’s essay on praise and assumed roles examines a related pressure from the recipient’s position. The connector has a distinct responsibility: describe the permission accurately before the pressure appears. A well-made introduction offers a possibility and preserves the freedom of both people to decide what comes next. Its success lies in the honesty of the opening, not in extracting the largest possible contribution from the person whose name made it attractive.
Gabriel Nicolaev — CyGuru
Overhead view of two people seated across a small cafe table beside a patterned tile wall; illustrative photograph.
Another angle on this subject
Continue through related ideas, decisions and consequences.
Human BehaviourListening Should Not Turn Another Person’s Story Into Your Own
A conversational opinion on sharing a relevant experience without taking over the encounter in which someone else came to be heard.
Technology & AIAn AI Agent Should Not Inherit Every Permission Its User Holds
The next operating question for AI agents is how much authority each task actually requires, and how a mistaken action can be contained.
Human BehaviourBeing the Host Does Not Make You Responsible for Every Friendship
Hospitality can create the conditions for a good gathering without controlling every conversation. A host should distinguish practical care from a demand that everyone connect.
