Double Opt-In Introductions Done Right

Run a double opt-in intro with two clean requests and one tight bridge message.

Voiskey Voiskey Team
Email IntroductionsIntro TemplatesDouble Opt-In Introductions

Why the Double Opt-In Sequence Works

Double Opt-In Introductions Done right begin before you write a single line to either person, because permission is the first deliverable. The pattern is simple: ask one person whether they want the connection, ask the second, and send a bridge message only when both have said yes. That extra step changes what you can promise. Nobody is ambushed by a stranger in the thread, the person being introduced can decline without explaining, and the eventual message carries the weight of two explicit yes answers. The cost is two short requests and a little waiting. Treat those requests as part of the introduction rather than as overhead, and the quality of the connection rises before anyone has met.

Name the three artifacts before you start, because a double opt-in fails when people improvise the order. The first artifact is a request to the person who proposed the connection. The second is a request to the person being introduced. The third is the bridge message that carries both names. Give each artifact a status you can see at a glance: proposed, asked, agreed, declined, or introduced. A simple list with one row per introduction is enough. When the status is visible, you stop sending a bridge message to someone who never answered, and you stop asking the same person twice because you forgot the earlier reply.

Set the bar for asking before you speak to either person. You need a verifiable overlap and one sentence about each person that the person themselves would recognize. The overlap should be something both can check in a line, such as a current hiring need, a shared customer segment, or a decision one person is making and the other has solved before. The one-liner should describe work, not praise character. Draft both one-liners yourself, then ask each person to correct their own before it appears in any message. This prevents the most common double opt-in failure: a flattering description that the subject would rather not have repeated.

Decide what happens when one person declines, and say it out loud in your own process notes. A decline ends the sequence: no bridge message, no quiet introduction, no forwarding of the thread. Send the other person a short note that the connection will not proceed this time, without repeating the reason. Keep the declined row in your list so you do not propose the same pairing next month. Also set a reasonable window for an answer, for example three working days, after which you treat silence as a no for now. These rules protect both people and keep the process from drifting into repeated nudges.

Drafting the Two Permission Requests

Draft each permission request with four parts: the reason you are writing, one line about the other person, the specific ask, and an easy way to decline. Keep the whole note under ninety words. A workable shape is: I am writing because you mentioned you are rebuilding the onboarding flow; my colleague Ana runs support for the same segment and solved a similar problem last year; would you like me to introduce you; if not, no explanation needed. Say the note in the order above and do not add background before the reason. The ask should be answerable with one word.

Dictate the two requests separately rather than adapting one from memory. The person who proposed the connection usually gets a warmer note with a reference to the earlier conversation. The person being introduced usually needs a little more context about who is asking and why now. Speak each version in the field where you will send it, so the text lands with the greeting and closing already in place. Keep your pace steady and say names slowly, because a misspelled name in a permission request is the error most likely to be forwarded and noticed. Read once, fix one phrase, send.

Check the description of the other person before you send, especially any claim about their work. A permission request is not a recommendation yet, so keep the line factual and modest: role, current focus, and one relevant result that the person has already shared publicly or with you. Avoid adjectives that imply an endorsement you have not been asked to give. If you are unsure, send the one-liner to that person first and ask whether they would change anything. That single check takes a minute and prevents a correction in front of a stranger, which is the kind of small embarrassment that makes people avoid introductions.

Make declining easy and record the answer the same day. Add one sentence that removes social pressure, such as no need to explain, and a second that keeps the door open, such as I can ask again next quarter if that is better. When the reply arrives, update the row immediately rather than trusting your memory. If the answer is yes, note the exact wording of any condition, for example after the launch or once the role is filled. If the answer is a no, note only that the connection was declined. Conditions matter later when you write the bridge message.

Reviewing the Sequence and Passing It On

Review the sequence on a fixed cadence, for example every Friday for ten minutes. Count how many requests were sent, how many were answered, how long the gap was between the two answers, and how many bridge messages produced a reply. A low answer rate points to a weak reason in beat one. A long gap points to a timing problem. A bridge message that gets no reply often has a vague action in beat four. Pick the weakest number and change one artifact, not all three. Write those four numbers in the same note as the standard so trends are visible across several weeks.

Refine with the same discipline you would use for any written process. Change the permission request first if answers are slow, then the bridge message if conversations stall. Keep the previous wording beside the new one and send five introductions with each. Compare the answer rate and the reply rate, and write the result next to the version. Do not declare a win from one good week, because a single warm contact can make any wording look effective. Two versions and ten introductions give you a defensible comparison. Keep the old drafts until the comparison closes, and treat an improvement that only helps one warm contact as noise rather than proof.

Write a one-page standard for anyone who introduces people on your behalf. Include the three artifacts, the four parts of each request, the word limits, the status values, and the rule that no bridge message goes out without two recorded yes answers. Add one example of a good request and one example of a message that should have waited. Walk a colleague through the sequence once, then ask them to draft a request for a real but low-stakes pairing and review it together. The standard is complete when they can run the sequence alone. Keep the review short, and do not rewrite the standard during the walkthrough; note the gaps and fix them afterward.

Keep improving the pattern with evidence from real threads. At the end of each month, read the three bridge messages that produced the fastest replies and mark the sentence that did the work. Add that shape to your example, not the whole message, because the specific names will not transfer. Then read one message that stalled and identify the missing condition, the vague action, or the weak overlap. Download Voiskey, dictate your next double opt-in request from the four-part shape, and record the answer in the same table. Keep the reply log beside that table so the next review starts from evidence rather than recollection.

FAQ s

Voiskey is an AI voice typing app that works at the system level. Press a shortcut, speak the four parts of the request, and polished text appears at the insertion point in your message window. It removes filler words, stutters, false starts, and self-corrections, and it adapts punctuation, formatting, tone, and phrasing to the request, so the note reads as a short written message.

Yes, within limits. Voiskey learns names, jargon, acronyms, and spelling preferences, so the second request is less likely to misspell the person described in the first. Speak both requests in the same session and review each at the insertion point before sending. It also adapts tone to what you are doing, which lets a note to a senior contact and a note to a peer share one structure.

Four parts in order: the reason you are writing, one factual line about the other person, the specific ask, and an easy way to decline. Keep it under ninety words. With Voiskey you can speak those parts at your normal pace and review the polished text once before sending. Record the answer the same day, because the bridge message waits until two yes answers exist.

Yes. Voiskey composes in the field where you already type, so you can speak the request directly in a chat window or a message field with no copy-paste step. It removes filler words and false starts and adapts punctuation and formatting to the field you are using. The same four-part shape applies whether the reply will arrive as a short message or a longer 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 run the double opt-in sequence from one spoken draft.

Use it across macOS, Windows, iOS, and Android

Use it across