A first email has to do a little more work than a message to someone who already knows you. The reader needs to identify you, understand why you chose them, and see what—if anything—you want them to do next. That does not require a long biography or a detailed account of how you found their address. A few specific, relevant details can make your purpose clear while respecting their time. Use the steps below to build a message that gives an unfamiliar contact enough context to decide how to respond.
The useful bits
- Identify yourself and your relevant connection in a sentence or two.
- Explain why you are contacting this person, not just what you want.
- Make one clear request and say what a useful reply would look like.
Start with a subject that previews the reason
A subject line should help the recipient understand the topic before opening the message. Keep it specific enough to distinguish your email from a general introduction, but do not try to fit the whole story into it. A project, shared context, or clear request can provide useful orientation.
For example, “Question about the [project name] workshop” tells the reader more than “Hello” or “Quick question.” If you have a genuine connection to mention, such as a mutual contact who suggested you write, include it only if it is accurate and appropriate to share. Do not imply an introduction or endorsement that did not happen.
Introduce yourself in terms that matter here
Give your name and a compact description of your role or relevant background. The recipient usually does not need your full career history. Choose the detail that helps them place you in relation to the reason for writing: perhaps the team you work with, a relevant project, or the kind of work you do.
Avoid making the recipient infer your connection from an email address or signature. If your role is broad or unfamiliar, explain it in everyday language. A useful test is whether the person can answer, “Who is writing, and why might this be relevant to me?” after reading the opening lines.
Subject: Question about the [project name] workshop Hello [Name], I’m [Your name], a [role] at [organization]. I work on [brief, relevant area].
Explain why you chose this person
State the reason for contacting this particular recipient. You might be asking because their role connects to your question, because they shared information relevant to your work, or because a mutual contact suggested you reach out. Be direct and factual; a short explanation is more useful than vague praise.
If your reason depends on something you read or heard, name it clearly enough for the recipient to recognize. Do not assume they know which article, event, or conversation you mean. If there is no particular connection beyond their role, say so plainly and keep the message considerate.
Give just enough background to make the request make sense
Add the minimum context the recipient needs to understand your question. Include the situation, the relevant constraint, and what you have already considered if that changes the answer. Leave out details that do not affect the request; a first email is an opening, not a complete project history.
Be careful with unexplained acronyms, internal labels, and assumed knowledge. If a short phrase can clarify a term, include it. If the background takes several paragraphs, consider whether the request can be narrowed or whether a brief conversation would be more appropriate.
Make one next step easy to recognize
Put the main request in a direct sentence. Ask for one action where possible, such as a recommendation, a short answer, or a conversation. If you suggest a meeting, give a reasonable duration and a flexible way to arrange it; do not presume the person is available at a time you chose.
Explain what kind of response would help and, when relevant, provide a practical deadline with a reason. Avoid stacking several unrelated requests in the same message. If the person is not the right contact, you can make redirection an easy alternative rather than asking them to solve the whole problem.
I’m trying to understand how [specific process] works for [brief situation]. Would you be willing to point me to the right resource, or suggest who might be best to ask? A short reply is plenty.
Review the message from the recipient’s point of view
Before sending, check that the subject, introduction, reason, and request agree with one another. Make sure names and organization details are correct, any mutual contact is described accurately, and the requested next step is visible without searching through the message. Use a professional sign-off with your name and a way to identify your organization or role when that information is relevant.
Then confirm that the message is addressed to the intended person and that any promised attachment is actually included. You can check whether the draft worked by asking someone unfamiliar with the situation to read it—or by pausing and answering three questions yourself: Who am I? Why this recipient? What reply am I asking for? If any answer is unclear, revise that part rather than adding a long explanation.
- Can the recipient identify you from the opening?
- Is the reason for contacting them specific and truthful?
- Is there one clear, manageable next step?
- Can they understand the request without knowing your background?
About this guide
Prepared with AI assistance for the BITTU Mail editorial library. Check important details against your original messages and current account settings. Product access depends on your role, plan and provisioning state. Provider interfaces and requirements can change.
View current plans · Security information · Suggest a correction