A three-line approach to short, considerate introductions people answer

Intro Emails That Respect the recipient's inbox start from a rule that is simple to state and hard to keep: every sentence must earn the next minute of attention. An introduction arrives as an uninvited task, often between a deadline and a meeting. The reader decides in seconds whether to reply now, later, or never. Respect means supplying the context, the reason, and the next step without making anyone open a second document or search a name. It also means writing for the busiest person on the thread, not the most patient one. A short, specific note is not a matter of style; it is the difference between an introduction that starts a conversation and one that quietly expires.
A vague introduction shifts work onto the reader. If the note says only 'you two should meet', the recipient must work out who the other person is, why the connection matters, and what response is expected. Most people do not do that work; they archive the message and move on. The cost is invisible to the sender and expensive for the relationship. A better note answers the questions before they form: the shared context, the benefit for each side, and the one action that follows. That is why length is not the real issue. A long note with a clear ask can be respectful; a short note with no ask is still a burden.
Use a three-line test before anything else. Line one names the people and the reason they are being connected. Line two states what each side gains. Line three gives the next step and an easy exit. If the note needs a fourth paragraph to explain the third line, the structure is not ready. The test is not a word limit; it is a check that the logic fits in a glance. Read the three lines aloud and ask whether a stranger could reply with one sentence. If not, rewrite until they can. Most inbox-friendly introductions pass this test before they pass a style guide.
Judge the note by reply quality, not by reply speed. A fast 'thanks, will follow up' may mean the reader is being polite while postponing a decision. A slower reply that names a time and a question is a better sign. Track which introductions produce a concrete next step and which produce only acknowledgement. That distinction tells you whether the note respected the reader's attention or merely avoided obvious mistakes. Speed matters, but it is a consequence of clarity. If you optimize for a quick response, you may reward pressure; if you optimize for a useful response, you build a habit that people trust.
Write the first line for a reader who is scanning. Name yourself, name the other person, and state the purpose in one sentence. Avoid openings such as 'I hope this finds you well', which delay the point and signal a template. A stronger opening reads: 'Mira, meet Tomas, who leads the vendor review you mentioned last week.' The reader now knows the cast and the reason. If the two people already know each other, say what changed and why the connection is worth renewing. The first line is not a greeting; it is the map. Everything after it can be shorter because the reader is already oriented.
The subject line should survive without the body. Use names and purpose, not mood. 'Mira and Tomas: vendor review' is fileable; 'A quick introduction' is not. Keep it under ten words, put the more familiar name first, and include the shared project or event when the connection is not obvious. Avoid words that promise more than the note delivers, such as 'urgent' or 'opportunity'. If the thread already exists, reply there instead of starting a new subject, so the reader keeps the history. A good subject line reduces the work of deciding what to do with the message, and that decision is where most introductions are lost.
Short sentences are not childish; they are considerate. A reader who is walking between meetings should not have to parse a sentence with three clauses and two parenthetical asides. Keep the average sentence under twenty words, and put the ask in its own sentence. When you dictate, speak in complete but compact units and let the app handle punctuation. If a sentence runs long, split it rather than deleting the detail. The goal is a rhythm that a tired reader can follow once. Read the draft aloud; if you run out of breath, the reader will run out of patience. Clarity is a form of respect that costs only a few extra edits.
Cut the material that exists to impress rather than to inform. A full career summary, a company description, and a list of mutual contacts all feel generous to the writer and look like homework to the reader. Keep one proof point per person, chosen because it explains the fit. Drop pleasantries that repeat the subject line and compliments that cannot be verified. If you met at an event, one detail about the conversation is enough; you do not need the agenda. The test is simple: does this sentence help the reader decide? If it only establishes the writer's diligence, remove it. The note becomes more credible as it becomes less crowded.
Timing shapes reception as much as wording. Send introductions during the recipient's working hours when you know them, and avoid the last hour of the day, when attention is gone and replies are deferred. For teams spread across regions, state the time zone in the note and propose two windows rather than one. If the introduction is not time-sensitive, say so; urgency that is not real reads as pressure. A Monday morning note competes with the week's planning, while a midweek note often gets a calmer read. You cannot control when someone opens a message, but you can avoid sending it when they are least able to act.
Keep one thread per introduction. Starting a new subject for each reply scatters the history and forces the reader to reconstruct the context. If the introduction moves to a scheduling conversation, keep the original thread and change the subject only when the topic truly changes. Do not forward a long chain and expect the reader to find the relevant part; summarize the two lines that matter at the top. When you add someone to the thread, say why they are joining and what you need from them. Thread discipline is a small courtesy with a large effect: it lets a reader catch up in one pass instead of five.
Be deliberate about who is copied. Every additional recipient increases the number of people who feel they must respond and the chance that nobody does. Put the two people being introduced on the main line, and copy only those who need to act or need to know. If a manager must be informed, say so in the note rather than copying them silently. Avoid reply-all when the message is only for the sender. Before you send, read the recipient list aloud and ask who will feel obligated by it. If the answer is 'everyone', the list is too wide for a simple introduction.
Sometimes two separate notes are kinder than one group message. If one side is senior and the other is early in their career, or if one person is being introduced for advice and the other for hiring, a shared thread can create mismatched expectations. Send each person a short note that names the other and explains the specific reason, then connect them only after both agree. This costs one extra message and prevents a public silence that feels like rejection. The group note is efficient when both sides want the same thing; separate notes are respectful when the goals differ. Choose based on the reader, not on your convenience.
Dictate the note in three passes rather than one long monologue. First say the who and why, then the benefit for each side, then the ask and the exit. Voiskey inserts each pass at the insertion point in your message window and removes filler, stutters, and false starts, so the text stays close to the three-line shape. Between passes, glance at the draft and delete anything that has already been covered. If you are unsure about the ask, say it twice in different forms and keep the shorter one. Dictation makes the structure audible, and an audible structure is easier to trim than a screen full of options.
Ask for brevity explicitly. Before you speak, say 'keep this under one hundred words' or 'write this as three short paragraphs'. Voiskey adapts punctuation, formatting, tone, and word choice to what you are trying to do, so a clear instruction produces a leaner draft than a general request for an introduction. If the first result is still long, do not rewrite from scratch; point at the extra sentence and ask for a shorter version. Then check that the cut did not remove the exit or the ask. Brevity is a target you set, not a quality the app guesses. A short note that keeps the exit is better than a long note that keeps every detail, so protect the shape as you trim.
Revise by voice, in place. Put the cursor on the sentence that feels heavy, press the shortcut, and say the replacement in full. Voiskey polishes the new sentence where you are writing, so the note never leaves the field and you never paste fragments from another window. Read the joined paragraph to check the seam, then move to the next weak point. Two or three spoken revisions are usually enough for a short note. If you find yourself rewriting every sentence, the problem is upstream: the ask or the context is unclear, and no amount of editing will make a vague note brief.
For mixed-language teams, dictate in the language you know best and ask for a translation into the recipient's language. Voiskey supports more than one hundred languages and translation, and it learns names, jargon, acronyms, and spelling preferences, which keeps product terms recognizable across versions. Compare the two versions for meaning rather than style, then send the one the reader will understand fastest. Keep the subject line consistent in both. When the note is ready, download Voiskey so the same three-pass routine is available on your next machine, and use it for the next introduction instead of starting from a blank page.
Build a pre-send checklist with five items: the subject line is fileable, the first line names both people, the benefit is specific to each side, there is one ask, and the exit is easy to use. Read the checklist aloud before every introduction until it becomes automatic. The list should take less than a minute, which means it has to be short enough to remember. Voiskey can hold the structure through shared workflows on a team plan, but the checklist is what keeps the structure honest. A note that passes all five items rarely needs a long explanation, and a note that fails one is usually worth rewriting.
Keep a small bank of openings organized by audience: peer, senior, candidate, client, and conference contact. Each entry should be a complete three-line shape, not a full message, so the writer still has to supply the specifics. Share the bank with the team and agree on names, product terms, and tone. Voiskey's shared vocabulary helps keep those terms consistent when several people dictate. Review the bank quarterly and delete lines that no longer match how the team works. The bank is a starting point for the first sentence, not a substitute for knowing why these two people should meet.
Prune templates using reply evidence. Mark every introduction that produced a concrete next step and every one that produced silence. Look for the difference in the benefit sentence and the ask. If a template works for peers but fails for senior contacts, split it into two versions with different openings. If a line has never helped, remove it rather than keeping it because it sounds polished. Revisit the subject patterns too; they are often the oldest part of a template and the least examined. The goal is a small set of openings that reliably respect attention, not a large library that nobody reads.
Make the routine portable. Download Voiskey on the machine you use for email and on the one you use when travelling, and keep the checklist and the opening bank in the place where you draft. After each batch, spend five minutes reading the sent notes as a reader would and note one improvement for the next batch. Share that improvement with anyone who writes introductions for the team. Over a month, the small corrections compound into a house style that is brief, specific, and easy to answer. Respect for the inbox is not a single well-written message; it is a habit that survives busy weeks.
Keep the note to three short parts: why you are writing, what the reader gains, and the next step. Speak them in your message window with the shortcut, and Voiskey removes filler and false starts while adapting tone. Read the result once, cut any sentence that does not change the reader's decision, and send only when the ask fits on one screen.
Yes. Voiskey supports more than one hundred languages and translation. Dictate the note in the language you think in, ask for a version in the recipient's language, and compare both before sending. Names and product terms stay recognizable because the app learns spelling preferences, which helps when an introduction crosses regions.
Remove anything the reader does not need in order to answer: company history, long credentials, several possible meetings, and hedges that hide the request. Keep the shared context, the benefit for each side, one next step, and an easy way to decline. If a sentence only makes you feel thorough, cut it before you send.
Open the draft in a narrow window and check that the first screen contains the reason and the ask. Confirm the subject line works without the body, names carry roles, and no link or attachment needs extra explanation. Read it once as the recipient, then speak any fix at the insertion point so Voiskey replaces the weak part in place.

Download Voiskey for Mac and Windows and turn a rough spoken draft into a clear, reply-ready note.
Use it across macOS, Windows, iOS, and Android