Reviewing an Intro Email Before You Send It

A read-aloud review method for introduction emails

Voiskey Voiskey Team
Email IntroductionsIntro TemplatesReviewing Intro Email

Read It as the Busiest Reader

Reviewing an Intro Email is a reading task before it is an editing task. Before you change a sentence, read the draft the way the busiest recipient will: on a phone, between meetings, with no memory of why you wrote it. Read once without stopping, then close it and ask what you were being offered. If you cannot answer in one sentence, the note is not ready. Most weak introductions are not badly written; they bury the offer under context, credentials, and courtesy. The review begins when you can name the offer in a single line. That line is the standard the rest of the draft has to meet.

Set a time limit of ninety seconds and a position: standing in a hallway with a phone in one hand. That constraint is not a gimmick; it reproduces the conditions under which most introductions are actually read. If the note needs a chair and a second screen, it is too long for its job. While you read, mark the first sentence where you understood why the two people should meet. If that sentence appears after the halfway point, move it earlier. Then mark the last sentence that made you want to reply. If there is none, the draft explains without inviting.

Every introduction asks the reader to make one decision: reply, forward, wait, or decline. Read the draft and underline the sentence that makes that decision possible. In a strong note it is the sentence that names the next step and its size. In a weak note the decision is spread across three paragraphs, and the reader has to assemble it. If the decision is not visible in one place, the review has found its first real problem. Fix that before you touch the adjectives. A note that makes the decision obvious can survive plain language; a beautifully written note that hides the decision cannot.

Read the draft as each recipient in turn, not as the author. The first pass asks whether you would feel respected if this arrived in your inbox on a Monday. The second asks whether you would feel described fairly, including any detail you would not have chosen to highlight. Introductions are small public statements about two people, and the review has to protect both of them. If a sentence would embarrass either reader in front of the other, cut it now rather than hoping it reads as praise. Tone is easier to fix at this stage than after the note has been forwarded.

Check Names, Roles, and Recipients

Check every name before anything else, because names are what readers look for first and remember longest. Read each full name against a current source rather than last year's thread. Confirm the spelling, the preferred form, and the order of given and family names. Then check the role that follows each name: a promotion, a move, or a new title changes how the sentence lands. If one person's description includes a title and the other's does not, add or remove so the pair matches. Names and roles are the parts of an introduction that cannot be argued with, so they have to be right.

Check that every description is true this month, not when you first met the person. Work changes quickly, and an introduction that describes someone's previous job reads as careless to the person doing the new one. Ask each recipient to confirm the clause that describes them, and give a day for a correction. This is not bureaucracy; it is the cheapest way to avoid a note that misrepresents someone in front of a stranger. If a person does not reply, keep the description modest and factual. A short clause that is accurate is worth more than a long one that flatters.

Check the recipient list before the wording. Decide who needs to act, who needs to know, and who would only be watching. Copy the people who will handle scheduling or who must approve the meeting, and leave out everyone else. A large copy list turns an introduction into an announcement and invites replies that fragment the thread. Check that no one who should be informed is missing, and that no one who was not mentioned in the body is on the list. A reader who appears in the copy field but nowhere in the text wonders why they are there. Fix that before you send.

Check the subject line and the first line together, because they are read as one unit in a list of messages. The subject should say what the note is: an introduction, a request, or a meeting setup. It should name at least one person or one project, so the reader can find it later. The first line should repeat the subject's promise rather than start a new topic. If the subject says introduction and the first line begins with background, the reader has to reconcile two openings. Align them, then read the pair aloud. A subject and a first line that agree set the reader's expectation correctly for everything that follows.

Test the Ask and the Exit

Find the ask and measure it. A good ask can be answered in one action: reply yes, pick a slot, forward a document, or say no. If the reader has to do two things, the ask is too big for an introduction and belongs in a follow-up. Read the ask aloud and ask how long it would take to complete. If the answer is more than a minute, cut it down or split it. The size of the ask should match the size of the relationship. A large ask in a first note reads as a demand, no matter how warm the language around it.

Check that the exit is explicit, because a note with no exit feels like pressure even when the author meant none. One clause is enough: a short no is fine, no reply needed if the timing is wrong, or happy to revisit later. The exit should appear near the ask, not buried in a final courtesy line. Read the last two sentences and see whether the reader could decline without writing an explanation. If declining requires an excuse, the exit is not working. An easy exit is what makes a fast yes possible, because the reader is not weighing the cost of saying no.

Test the ask against each recipient separately, because an introduction can be welcome to one person and a chore to the other. For each reader, ask what they are being asked to do and what they get in return. If one side is doing all the work and the other is only receiving, say so plainly or reframe the note as a request. Read the same paragraph from each side and note whether either version sounds like an obligation. When one side sounds thinner, rewrite that clause before you rewrite the ask. A fair ask is easier to accept than a flattering one.

Test the note against the relationship it is meant to create. A first contact between strangers needs more context and a smaller ask than a note between people who already know each other. Read the draft and ask whether it assumes a familiarity that does not exist, or explains a connection the reader already has. Both errors are common: too much background for a close pair, too little for strangers. Adjust the amount of context, not the warmth. The review should leave the note calibrated to this pair, which is the one thing a reusable template cannot do for you.

Revising the Draft with Voiskey

Download Voiskey and dictate the revision instead of typing it. Put the cursor where the new version belongs, press the shortcut, and speak the change at a normal pace; the text appears at the insertion point with no separate recorder and no copy-paste step. Voiskey removes filler words, stutters, false starts, and self-corrections, so a spoken revision arrives closer to the sentence you meant. Say the fix out loud, for example 'move the ask to the second sentence and cut the biography'. Then read the result and keep it only if it is shorter than the original. Revision should reduce length, not add it.

Describe the target version before you speak. Say 'rewrite this as a shorter introduction with the ask in the second sentence' and the app adapts punctuation, formatting, tone, and word choice to that instruction. Ask for plain sentences and one small next step. If the draft still runs long, dictate the same instruction with a tighter limit and compare the two versions side by side. Speaking the target first is what keeps a revision from drifting back into the habits of the original. Read both versions aloud and keep the one a busy reader could answer in a single line.

Use the name handling to protect the details that a revision can quietly damage. Voiskey learns names, jargon, acronyms, and spelling preferences, so say each name once, check the draft, and correct any misspelling by voice. Revision is exactly when a name gets shortened or a title gets dropped, so check both after every pass. For a note that crosses languages, dictate in the language you know best and request a translation, then read the result. Voiskey supports more than a hundred languages and translation. Check that the translation kept the names, the roles, and the size of the ask.

Revise in passes, not in one long edit. First, cut anything the reader does not need to make the decision. Second, move the ask and the exit so they sit close together. Third, read the result aloud and fix the places where you stumble. The Speak-Polish-Type-Edit order works best when you dictate the whole note and then subtract, because speaking keeps the sentence rhythm natural while cutting keeps the note short. Make at most three structural changes per pass, then read the whole draft again. A note revised in passes stays coherent; a note rewritten sentence by sentence tends to lose its opening.

Sending, Following Up, and Recording

Send one version, in one thread, and keep the subject stable from the first note to the thank-you. Before you send, read the final draft on a phone screen, because that is where many readers will meet it. Check that the ask, the exit, and the names all fit in the first screen with no scrolling. If the note needs a second screen, cut rather than shrink the type. Send it at a time when the recipients are likely at their desks, and avoid the end of the week when replies slide into the next one. One clean send is better than a corrected follow-up.

Follow up once, in the same thread, after the window you stated has passed. Repeat the offer in one sentence, restate the ask, and add nothing new. Do not resend the whole note or change the subject; a reader who missed the first message can scroll up and find it. If the reply is a no, thank the person briefly and say the introduction can wait for a better moment. If it is a yes, confirm the next step in writing the same day. One follow-up is a courtesy; two is pressure. The review you did before sending is what makes one follow-up enough.

Record what you sent and what came back, in a place you will look again. Note the date, the two names, the reason you gave, the size of the ask, and the answer. If a reader replied, note which sentence they responded to, because that tells you which part of the draft did the work. If no one replied, note that too, without assuming the note was wrong. Over a few months the record shows which openings, asks, and exits produce replies and which produce silence. That pattern is the most useful review of all, because it measures the note against real readers.

Turn each review into a short checklist you can reuse. Keep the six or seven checks that actually caught problems: the offer in one line, the ask in one action, the exit near the ask, the names verified, the recipients correct, the subject aligned. Run the list before every introduction, and drop any item that has not caught anything in months. A checklist made of your own mistakes is faster than a general guide, because it targets the errors you actually make. Review the list twice a year, and update it after any note that went wrong. The habit is the point, not the document.

FAQ s

Dictate the revision instead of typing it. Say the change out loud, such as moving the ask to the second sentence, and Voiskey removes filler and self-corrections so the new version arrives closer to the sentence you meant. Ask for a shorter form before you speak, then read both versions aloud and keep the one a busy reader could answer in a single line.

Voiskey learns names, jargon, acronyms, and spelling preferences. Say each name once, check the draft, and correct any misspelling by voice. Revision is when a name gets shortened or a title gets dropped, so check both after every pass. If the note crosses languages, request a translation and confirm that the names, the roles, and the size of the ask all survived the rewrite.

It helps you shorten them. Read the ask aloud and count the actions it requires; if there are two, dictate a single-action version. Then read the last two sentences and confirm the reader could decline without writing an explanation. Speak the exit next to the ask it belongs to, and use Voiskey to trim anything between them, so the two sit close enough to see together.

Note the date, the two names, the reason you gave, the size of the ask, and the answer. If a reader replied, note which sentence they responded to, because that shows which part of the draft did the work. If no one replied, record that without assuming the note was wrong. Over a few months this record shows which openings, asks, and exits produce replies, and that pattern is the most useful review of any note.

Say less. Get more
Say less. Get more
Say less. Get more
Say less. Get more
VoiskeyVoiskey

Your voice, amplified.

Download Voiskey for Mac and Windows and review your next introduction before you send it.

Use it across macOS, Windows, iOS, and Android

Use it across