A scheduling-first method for introduction emails

Intro Emails That Set up a meeting should begin with the meeting, not the introduction. The introduction is the reason the meeting can happen, but the meeting is what both readers need to evaluate. What is it for, how long is it, who needs to be there, and what will each person leave with? A note that answers those questions is easy to accept or decline. A note that only explains why two people should know each other leaves the reader to design the meeting themselves, which is work most people postpone. Start with the purpose and let the introduction support it.
Name the meeting type and the outcome. A first conversation, a working session, a review, and a decision meeting require different preparation and different attendees. Say which one this is and what should be true at the end: a shared understanding, a decision, a next step, or a list of open questions. That outcome sentence is what turns a vague invitation into a specific one. It also gives both readers a reason to prepare, and preparation is what makes a short meeting useful rather than polite. A reader who knows the outcome can decide in one pass instead of asking a clarifying question.
Put a number on the time and sketch the agenda in three lines. Thirty minutes is a different commitment from sixty, and a reader who knows the length can check a calendar honestly. The agenda does not need to be detailed; three short items are enough to show that someone has thought about the conversation. If the meeting is exploratory, say so and propose a structure anyway, such as introductions, current work, and possible next steps. An exploratory meeting with a structure is easier to accept than one described only as a chance to connect. That structure also makes the meeting easier to schedule.
Decide who needs to attend and who is optional. A meeting with four required people is much harder to schedule than one with two, and every extra attendee makes the purpose less clear. Name the two principals first, then add anyone whose presence is genuinely necessary. If a colleague would add context but is not needed for the decision, mark them optional and say what they would contribute. Fewer required attendees means faster scheduling and a better conversation, and it signals that you have thought about the reader's time. Fewer required people also means a shorter thread and a faster yes.
Offer two or three concrete slots instead of open availability. 'Let me know when you are free' pushes the scheduling work onto the reader and often produces a thread of counter-proposals. A short list of options, already checked against the calendars of the required attendees, makes the decision a choice rather than a project. Include the time zone for each slot. If one slot is strongly preferred, say so and explain why in a clause; a recommendation is helpful as long as the alternatives are real. State the zone once for each option so nobody converts it in their head.
Check the slots against the required attendees before you send. Nothing damages a scheduling note faster than offering a time that one principal cannot make. If you cannot see someone's calendar, ask them for two windows before you write the introduction, then present the overlap. This adds one message but saves three. A slot that has to be withdrawn looks careless, and a reader who has already agreed to a time that then changes is less likely to agree to the next one. A slot offered and then withdrawn also teaches readers to wait before they answer the next note.
Decide whether to use a scheduling page or a short list. A page is convenient when the reader's calendar is current and the meeting has flexible timing. A short list is better when the meeting is small, the attendees are senior, or the purpose depends on a particular sequence. In either case, name the slots in the message so the reader can decide without opening another tab. The tool should reduce friction, not add a step. If the page cannot show the right time zone, write the times in the message instead. The message should be enough on its own.
Give the offer an expiry. Say when you need an answer to hold the slots, and what happens if the date passes. A hold with a clear end is easier to accept than an indefinite offer, because it gives the reader a deadline without pressure. If neither slot works, ask for two alternatives and offer to rebuild the options. That request is small and specific, which makes it much more likely to produce a reply than a general invitation to suggest a time. Two named alternatives are easier to answer than an open request for any time that might work.
Name the person who will send the calendar invitation. Ambiguity about who acts next is the most common reason a promising introduction produces no meeting. Say whether you will send it, whether one of the principals will, or whether an assistant will handle it. Then say when it will arrive. A single sentence removes the pause where both readers wait for the other to move. Ownership is not bureaucracy; it is the difference between a plan and a pleasant exchange of messages. Say the same thing in the second line so nobody has to ask who is actually sending it.
Name a backup for the logistics. If the owner is traveling, on leave, or in a different time zone, someone else should be able to send the invitation and answer questions. Say who that is in the same sentence. This matters most when the introduction involves senior readers, whose calendars change often and whose assistants may need to coordinate. A backup also protects the meeting from a single point of failure, which is a quiet form of respect for everyone's time. Share the backup's name and time zone in the very same sentence as the owner's name and contact details.
State what each person should bring or prepare. A short meeting works when everyone arrives with the same expectation. One line per person is enough: a document, a question, a short update, or nothing at all. If nothing is needed, say that explicitly, because readers often assume preparation is required and delay the meeting to do it. Preparation instructions should be small enough to complete in fifteen minutes. If they are larger, the meeting is probably not the right next step. If a document is needed, name the section so the reader does not have to search through the whole document for it.
Decide how to handle a missed meeting. Say whether the slot can be moved once, who will propose the new time, and whether the introduction continues if the first attempt fails. A clear policy prevents the awkward silence that follows a no-show. It also lowers the stakes of accepting, because the reader knows a single conflict will not end the relationship. Keep the policy simple and generous; the goal is a conversation, not a perfect attendance record. Say it plainly in one short line near the slots so the reader can see the policy before deciding whether to accept.
Download Voiskey and dictate the note in the message window you already use. Put the cursor in the body, press the shortcut, and speak 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 the draft keeps the structure you planned. Speak the purpose, then the slots, then the owner. That order gives the reader a reason, a choice, and a next step in the first reading. The reader should never have to hunt for the purpose or the ask.
Describe the format before you speak. Say 'write this as a short introduction that sets up a thirty-minute meeting' and the app adapts punctuation, formatting, tone, and word choice to that instruction. Ask for a short list of slots and one sentence naming the owner. If the note needs both a warm opening and a precise logistics block, dictate them as separate sentences and keep both short. A meeting note fails when the warmth and the logistics compete for the same paragraph. One spoken instruction followed by one clear list always beats three instructions delivered in a single breath.
Let the app learn the names and time zones you use repeatedly. Attendee names, company names, and city names are the details that get misspelled, and Voiskey learns names, jargon, acronyms, and spelling preferences. Say each one once, check the draft, and correct it by voice. For meetings across regions, dictate in the language you know best and request a translation, then read the result. Voiskey supports more than a hundred languages and translation, which helps when one attendee works in a different language. Check both spellings in the draft before the note goes out to anyone outside your own small team.
Edit in three passes. First, confirm the purpose and outcome appear before the slots. Second, check that every slot is real and includes a time zone. Third, confirm that one person owns the invitation and that the expiry is stated. The Speak-Polish-Type-Edit workflow works best when you dictate the whole note and then cut, rather than composing sentence by sentence. A meeting introduction is a small operational document, and its quality is measured by whether the reader can act without asking a question. Read the whole note once after the third pass, because the cuts can leave a gap.
Send a short recap after the reader accepts. Repeat the purpose, the time with both zones, the length, the attendees, and who will send the invitation. This is not redundant; it is the moment when a loose agreement becomes a commitment. Keep the recap to five lines and put the details in the same order as the original note. A reader who can scan the recap and recognize every detail is a reader who will show up prepared. Confirmation is part of the introduction, not a separate administrative task. Keep it in the same thread so the history stays in one place.
Attach the agenda and any preparation in the recap, not before. Sending materials with the invitation asks the reader to process them before deciding, which slows the decision. Sending them after acceptance gives the reader a reason to prepare and a clear moment to do it. Name the one document that matters and say which section to read. If there is nothing to prepare, say so in one line. The recap should leave no ambiguity about what happens between now and the meeting. Name the deadline for the preparation as well, so the reader can plan the rest of the week.
Send one reminder a day before, with the same details. Include the time in the reader's zone, the link or location, and a name to contact if something changes. Keep it to three lines. A reminder is not a sign of distrust; it is a courtesy that saves the reader from searching through a thread. If the meeting has a hard start, say so. If a document is needed, link it again. Small consistencies like these are what make a first meeting feel organized. A reminder that repeats the same wording is always easier to scan than a freshly rewritten one.
Close the loop after the meeting. Send a short note with the decisions, the owners, and the next date, and thank both people for the time. Then update your record of the introduction: the date, the participants, the outcome, and whether the pairing was useful. That record is how you learn which introductions produce meetings and which produce polite interest. Over time, it turns meeting introductions from a series of one-off favors into a practice with visible results. Keep each record short: a name, a date, an outcome, and one line on what made the pairing actually work well for both people.
Speak the purpose first, then two or three dated slots, then the name of the person who will send the invitation. Voiskey removes filler and self-corrections, so the note reads as a short operational message rather than a pitch. Ask for a brief tone, check the time zones, and state when the offer expires before you send.
Yes. Say that you want a short introduction that sets up a thirty-minute meeting, and Voiskey adapts tone, formatting, and structure to that instruction. Ask for a short list of slots and one sentence naming the owner. Then check that the purpose, the length, and the expiry all appear in the draft.
Voiskey learns names, jargon, acronyms, and spelling preferences. Say each attendee's name, company, and city once, then check the draft and correct any misspelling by voice. Meeting notes travel to assistants and calendars, so a name error spreads further than it would in a personal message. Check every name before the note leaves your hands.
Send a five-line recap with the purpose, the time in both zones, the length, the attendees, and the owner of the invitation. Then attach the agenda and any preparation, and send one reminder a day before. Keep the recap in the same order as the original note so the reader can scan it quickly.

Download Voiskey for Mac and Windows and dictate a meeting-ready introduction.
Use it across macOS, Windows, iOS, and Android