Published October 2, 2026
Professional introduction coordination
A founder promises to introduce two people after a useful conversation. The promise is easy to make and easy to lose among other work. An assistant can turn it into a completed introduction, but only if the handoff preserves why the connection was proposed and whether both people want it.
The administrative task is more than putting two email addresses together. A good introduction respects the context of each relationship and gives the recipients a reason to continue. It also avoids implying that the founder endorses a person, service, or opportunity more strongly than intended.
Capture the purpose while it is still clear
Record who should meet, what they might usefully discuss, and what the founder actually promised. “Introduce them about the workshop project” is more informative than “connect these contacts.” Include any timing constraint or sensitivity the assistant needs to understand before drafting a message.
Distinguish a firm promise from a possible idea. A founder may say, “I might know someone who could help,” without having decided that an introduction is appropriate. The assistant should preserve that uncertainty and ask for a decision rather than turning the suggestion into an obligation.
Do not require a long relationship history. The assistant needs enough context to prepare the coordination, not a complete account of every previous interaction. Keep personal information out of the record unless it is necessary for the task and appropriate to retain.
Confirm that the connection is welcome
Agree on who will ask permission and what the request should say. The founder may prefer to approach a close contact personally while the assistant handles practical follow-up. In other cases, the assistant may have explicit authority to send a short permission request on the founder's behalf.
Explain the proposed subject and the expected next step. Someone may welcome an exchange of emails but have no capacity for a meeting. Permission should fit the actual request rather than being treated as a general willingness to provide unlimited help.
| Stage | Assistant can prepare | Decision that stays explicit |
|---|---|---|
| Initial idea | Names and proposed purpose | Whether to pursue the connection |
| Permission | Bounded invitation | Whether each person agrees |
| Introduction | Context and next step | Any endorsement attributed to founder |
| Follow-up | Status reminder | Whether further involvement is wanted |
If either person declines, close the task courteously. Do not ask for an explanation unless it is needed and welcome. A declined introduction can still represent a well-run process because it protected the recipients from an unwanted commitment.
Draft an introduction that does useful work
The message should identify each person, explain the relevant connection, and state the agreed purpose. Use the descriptions they have approved or that the founder knows to be accurate. Avoid inventing credentials or adding promotional adjectives to make the introduction sound more impressive.
Be careful with endorsement language. “I thought you might find it useful to compare notes” conveys a different relationship from “I strongly recommend hiring this person.” The assistant should use the founder's intended level of support rather than filling the gap with enthusiastic boilerplate.
Keep the next step modest. If both people agreed to exchange information, do not announce that they will schedule a long meeting. The introduction should transfer the conversation to them without dictating a commitment they have not accepted.
Use a visible but lightweight queue
Track introductions as awaiting founder decision, awaiting permission, ready to send, sent, or closed. These labels make the next action clear without requiring a complex relationship management system. Record the current owner so a task does not remain indefinitely in an ambiguous waiting state.
Set a reminder based on the context of the promise. A time-sensitive project may warrant an earlier follow-up than a general professional connection. Avoid treating silence as consent or repeatedly reminding someone who has not agreed to participate.
If the founder has promised several introductions, review them together. The assistant can show which are missing context and which are ready. That lets the founder supply the necessary decisions in a focused session rather than receiving a stream of unrelated interruptions.
Handle changing circumstances
An introduction can become less appropriate while permission is pending. A project may close, a person may change roles, or the original question may be answered another way. The assistant should check whether the purpose still exists before sending a delayed message.
When the scope changes, update the permission request. A conversation about general industry experience is not the same as a request to evaluate a commercial proposal. The recipients should know what they are being invited into at the point they agree.
For writing reference, see the plain language guide. In your own messages, specificity matters more than ceremony. A short explanation of relevance is usually more helpful than a long paragraph praising both people.
Close the loop without supervising the relationship
Once the introduction is sent, the assistant can record completion and any follow-up the founder explicitly promised. The recipients generally own the conversation from that point. Do not routinely ask them to report what they discussed or whether they found each other useful.
If the founder needs to know whether a time-sensitive connection occurred, agree on a proportionate check. A simple inquiry may be enough. Avoid turning a friendly introduction into a monitored project unless everyone understands that it serves an actual business workflow.
Review missed promises periodically. If introductions repeatedly stall because the founder forwards names without context, improve the original capture habit. The assistant should not have to guess the purpose from a calendar entry or reconstruct it from unrelated correspondence.
Executive support can include maintaining this queue alongside other open commitments. Bring examples of introductions that tend to stall to a free consultation so the administrative scope can be defined around your real needs.
Frequently asked questions
Can my assistant send introductions from my inbox?
Only under the access and communication authority you have explicitly granted. Agree on whether messages are drafted for review or sent under a defined rule. The recipient should not be misled about who prepared or coordinated the exchange.
What if I already promised the introduction verbally?
The promise still needs enough context and appropriate permission to be fulfilled well. Ask the assistant to capture the intended purpose and identify anything missing. A verbal promise should not force either recipient into an unwanted conversation.
Should every introduction use a standard template?
A reusable structure can prevent omissions, but the relevance should be specific. If the same description fits every pair of people, it probably does not explain why these two should connect. Keep the framework short and personalize the substance.