
Introducing yourself by email is common when starting a job, contacting a professional in your field or following up on a referral. The recipient cannot rely on the context of an in-person conversation, so your message must establish relevance quickly and make the next step easy.
A strong introduction email is concise without sounding abrupt. It gives the recipient enough information to understand the relationship, avoids an oversized request and uses a specific subject line.
You might introduce yourself by email when:
Joining a new team or company
Contacting a colleague in another department
Reaching out to a potential mentor
Requesting an informational conversation
Following a mutual contact's referral
Beginning work with a client or vendor
Connecting after an event
Introducing two people, with permission
The content should match the relationship. A note to new teammates can be warm and collaborative. A message to a stranger should show why you selected that person and keep the request limited.
The subject should help the recipient recognize the purpose without opening the message.
Examples include:
Introduction: Maya Chen, new product analyst
Referred by Luis Romero: brief research question
Following up from the Denver sustainability forum
New project contact for the Atlas rollout
Avoid vague subjects such as “Hello,” “Important” or “Quick question.” Do not use false urgency or imply a referral that did not occur.
Use the name and level of formality that fit the context. “Hello Dr. Ahmed” is suitable when a title matters; “Hi Priya” may fit a workplace with informal norms. Verify spelling and pronouns rather than guessing.
When you do not know a person's name, research the appropriate contact. “Hello hiring team” is preferable to “To whom it may concern” for many modern professional messages.
State your name, role and relevant context in the first sentence. The recipient should not need to search your signature to understand who wrote.
My name is Elena Park, and I joined Northstar's operations team this week as a project coordinator.
Describe why you are writing to this person. If someone referred you, say so only with that person's permission. Mentioning a specific article, talk or project can establish genuine relevance.
Ask for one realistic next step. A 15-minute conversation, the correct resource or confirmation of a meeting owner is easier to evaluate than “Can I pick your brain?”
Make it possible to decline. A stranger does not owe you time, an introduction or career advice.
Give the details needed to answer, but avoid pasting your full biography. If a portfolio or document is relevant, link to an established page or mention that you can send it upon request. Unexpected attachments and unfamiliar links can create security concerns.
Thank the recipient and use a closing that fits the tone, such as “Best,” “Regards” or “Thank you.” Include your full name, role and relevant contact information.
Check the recipient, name, company, dates, links and request. Pay special attention when adapting a template; sending the wrong company name is memorable for the wrong reason.
The following fictional examples can be adapted to your situation.
Subject: Introduction: Daniel Ruiz, new customer operations manager
Hello team,
My name is Daniel Ruiz, and I am joining Cedarline today as the customer operations manager. I will be working with support, success and product operations to improve our service processes and reporting.
For the past five years, I have managed customer operations for subscription software teams, with a focus on onboarding, capacity planning and cross-functional problem-solving. During my first few weeks, I plan to learn how the current workflows operate and understand what is already working well before proposing changes.
I will be reaching out to schedule brief introductions, but please feel free to say hello on Slack or email me. I am looking forward to working with you.
Best,
Daniel Ruiz
Customer Operations Manager
Why it works: The message identifies Daniel's role, gives relevant background and explains how he intends to begin. It does not overstate authority or promise immediate transformation.
Subject: Question about your transition into healthcare analytics
Hello Ms. Patel,
My name is Simone Brooks, and I am a reporting analyst in higher education exploring a transition into healthcare analytics. I read your recent association interview about moving from public-sector reporting into hospital operations, and your comments about data governance were especially useful.
If you are open to it, could I ask you three questions in a 15-minute phone conversation during the next two weeks? I am particularly interested in which skills transferred directly and which areas required additional training. I am happy to work around your availability, and I understand if your schedule does not allow it.
Thank you for considering my request.
Best,
Simone Brooks
Reporting Analyst
linkedin.com/in/simonebrooks
Why it works: Simone explains why she contacted this individual, asks for a limited amount of time and gives the recipient a comfortable way to decline.
Subject: Referred by Marcus Lee: community research collaboration
Hello Dr. Okafor,
My name is Leah Nguyen, and I lead community research at Harbor Transit Alliance. Marcus Lee suggested I contact you and confirmed that I could mention his name. He thought our upcoming accessibility study might connect with your work on inclusive public-space design.
We are developing the research plan for interviews with riders who have mobility disabilities. I would value your perspective on two questions about recruitment and accessible participation. Would you be available for a 20-minute call next week? Tuesday afternoon and Thursday morning are open for me, but I can adjust if another time is easier.
I have included a link to our public project page below for context. I can send a one-page research outline if that would be useful.
Thank you,
Leah Nguyen
Community Research Lead, Harbor Transit Alliance
harbortransit.example/accessibility-study
Why it works: Leah names the mutual connection with permission, explains the relevance and asks for a specific conversation. She links to a public source rather than attaching an unexpected file.
Subject: [Clear purpose or shared connection]
Hello [Name],
My name is [full name], and I am [role or relevant context]. I am contacting you because [specific reason, shared connection or relevant work].
[One or two sentences of useful background.] Would you be open to [one clear, proportionate request]? [Optional timing or easy way to decline.]
Thank you for [considering the request/time].
[Closing],
[Full name]
[Role and organization]
[Relevant contact or professional link]
Introduction: [Name], new [role]
[Mutual contact] suggested I reach out
Following up after [event]
New [project] contact at [company]
Question about your work on [specific topic]
Introduction before our [date] meeting
Keep the subject truthful. Adding “Re:” to a new email to make it look like a reply, or claiming urgency that does not exist, damages trust.
Many professional introductions fit in roughly 100 to 200 words. Internal team introductions can be slightly longer when colleagues need background. Cold networking messages should usually be brief because the relationship is new.
Length depends on complexity, but every paragraph should help the recipient identify you, understand the reason or respond. Move detailed proposals into an approved document after the recipient expresses interest.
Mention the specific work, event or connection that prompted the email. Generic praise such as “I have followed your amazing career” can sound automated.
Do not request a job, referral or extensive review from a stranger in the first line. Ask for information or a small next step and accept that the person may not respond.
Ask the mutual contact before using their name. A referral should mean that the person genuinely suggested or approved the contact.
Send from an appropriate address and include a clear signature. Avoid unnecessary personal data such as a home address or identification number.
Use one relevant professional or official link. A recipient may reasonably avoid unfamiliar shortened URLs and attachments. The Federal Trade Commission advises caution with unexpected links and attachments because phishing messages may install malware or steal information.
If the message is time-sensitive, a short follow-up after several business days may be appropriate. Add value or restate the request briefly. Repeated daily messages create pressure and rarely improve the response.
Using a vague or misleading subject line
Misspelling the recipient's name
Writing a long autobiography before stating the purpose
Sending the same generic praise to many people
Asking for several large favors
Attaching files without context or permission
Claiming a mutual connection without approval
Using a casual tone in a formal setting
Hiding the requested action
Forgetting contact information
Following up too frequently
If someone introduces themselves, acknowledge the message and answer the request directly. If you cannot help, a brief decline is sufficient. Do not forward their personal details or request to others without permission.
When an intermediary introduces two people, reply all initially so the introducer knows the connection was received, then move them to BCC or a separate thread when appropriate. Thank the introducer and state the next step.
AI can help shorten a draft, adjust tone or generate subject options. Provide only the context needed and remove confidential or sensitive information. Review the output for invented relationships, inaccurate compliments and language that does not sound like you.
Mass-personalized introductions can damage reputation when the details are wrong. A smaller number of thoughtful messages is usually more effective than automated outreach without relevance or consent.
If an introduction leads to a meeting where you need to present a proposal, portfolio or project overview, Dokie can help organize approved information into a clear deck. You can structure it around the context, audience need, your relevant experience, proposed approach, supporting evidence and next step.
Review every Dokie-generated slide before sharing it. Verify names, facts and links, remove confidential correspondence and obtain permission before including another person's information or work. Dokie can support presentation structure, but professional trust depends on your accuracy, judgment and respect for privacy.
State your name and role early, explain the relevant connection or reason, make one clear request and close with professional contact information.
Use a specific, truthful subject such as “Introduction: Maya Chen, new product analyst” or “Referred by Luis Romero: research question.”
Only when the context calls for it or the recipient requested it. For cold outreach, a professional profile link or an offer to send the resume may feel safer than an unexpected attachment.
Get the contact's permission, mention the person accurately, explain why they suggested the connection and make a proportionate request.
Several business days is a common guideline, adjusted for the stated timeline and urgency. One concise follow-up is often enough unless the recipient invites further contact.
AI can support drafting and editing, but you should verify every detail, protect private information and revise the message into your own voice. Never allow it to invent a referral or relationship.