Speak nudges, progress summaries, and decision requests in the original thread

Dictating Follow-Ups Directly Under the original thread keeps every piece of context in one place. The reader sees what was asked, what was promised, and what you are adding now. That is a better experience than a fresh message that forces them to search for the history. The mechanic is the same as any reply: open the thread, click reply, put the cursor in the body, press the shortcut, and speak. The difference is discipline, not technology. A follow-up should be short, specific, and easy to answer, and dictating in place makes all three easier because the history stays visible while you write.
Decide before you write whether the follow-up is a nudge, a summary, or a decision request. A nudge asks for a status. A summary reports progress and confirms what remains. A decision request names the choice and the deadline. Mixing the three produces a message that is hard to act on, and hard-to-act-on messages are why threads stall. Say the type out loud to yourself, then write only that type. One clear purpose per follow-up is the single most reliable way to get a response. When a message tries to be all three, pick one and send the others in a separate note.
Pick the right moment. A follow-up sent too early reads as pressure; one sent too late loses the thread. Use the commitment in the thread as your clock: if someone said Thursday, follow up Friday morning. If no date was given, give one in your follow-up rather than asking for one vaguely. Directly under the thread, the earlier promise is visible, so you can reference it without sounding accusatory. This is a social advantage of replying in place, not just a technical one. A date you set yourself is better than a vague question about someone else's timing, because it gives the reader something concrete to accept or move.
Keep a simple record of what you sent so you do not repeat yourself. If you follow up twice with the same wording, the reader notices, and the thread starts to feel like a queue rather than a conversation. Vary the ask: the first follow-up requests a status, the second offers a shorter path, the third proposes a decision. This escalation is a courtesy and it moves the thread. Write the three levels in your notes once, and use them in order. Three levels are enough; more than that starts to feel like a process for its own sake.
A good nudge has three parts: the reference, the ask, and the ease. The reference points to the earlier message in one line. The ask states exactly what you need. The ease offers a way to answer quickly, such as a yes or no, a date, or a link. Say all three in order. Under the thread, the reference can be short because the history is right there. The ease is the part people skip, and it is the part that most increases the chance of a reply, because it lowers the effort of responding. If the easy path is missing, the reader has to invent a reply format, and invention is friction.
Speak the nudge in a calm, matter-of-fact tone. Tone is easy to misjudge in writing, and follow-ups are where it matters most. Voiskey adapts tone and word choice to the task, but your delivery is still the input, so say it the way you would say it to the person across a table. Avoid adverbs that increase pressure, and avoid apologies that make the ask feel burdensome. A nudge should read as a normal part of working together, not as an accusation or an apology. A calm sentence is easier to answer than a clever one, and the goal is an answer.
Keep the nudge to three sentences where possible. Sentence one references the earlier note. Sentence two makes the ask. Sentence three offers the easy path or names a date. If you need a fourth sentence, ask whether the follow-up is really a nudge or a summary wearing a nudge costume. Three sentences are also easier to review, which matters because a rushed nudge is the kind of message people regret. Read it once before sending and cut anything that does not serve the ask. Cut a sentence that repeats the reference, because the thread already holds it in plain view.
Send the nudge and then leave the thread alone. The temptation is to send a second message within the hour to explain or soften, and that usually weakens the first. If the person is busy, two messages read as pressure. If they missed the first, one clear nudge plus a second at a sensible interval is enough. Write the interval in your notes so the decision is made in advance rather than in a moment of impatience. Patience is easier when it is planned. Write the interval down, and let the calendar enforce it instead of your patience, so the decision is made once rather than every hour.
A progress summary is a different message from a nudge, and it should look different. Open with what is done, then what is in progress, then what is blocked and who can unblock it. Say each part as its own short burst and pause between them so the structure holds. Under the thread, the reader can check the earlier messages if they want more detail, so the summary can stay tight. This format respects the reader's time and gives them a clean picture of where things stand without making them reconstruct the sequence. A reader should be able to answer from the summary without opening the earlier messages.
Use names and dates instead of vague status words. On track and in progress sound reassuring and communicate nothing. Asha sent the draft Tuesday; review closes Friday; the vendor reply is the open item. Concrete statements are easier to verify and harder to misread. Voiskey learns names and jargon, so a short correction pass keeps those names spelled the way your team expects. The summary is only as useful as its specificity, and specificity is easy to speak. Say the name exactly as the team writes it, then read the line once to confirm the spelling is right, and once more for the date.
End the summary with the one thing you need from the reader, even if that thing is nothing. No action needed is a complete and useful sentence; it closes the loop and tells the reader they can move on. If you need something, name it and name the date. A summary without a closing line invites a question, and a question reopens a thread you were trying to close. The closing line is the cheapest way to end a conversation cleanly. A closing line is a courtesy and a boundary at the same time. It tells the reader the message is complete and tells you the thread is finished.
Send progress summaries on a predictable rhythm rather than when you remember. Every Friday, every other Tuesday, after each milestone. A rhythm tells the reader when to expect an update and reduces the number of status questions you field. Dictating the summary takes a few minutes because the structure is familiar, and familiarity is the point. A template you can speak from memory is worth more than a clever one you have to look up, especially on a busy afternoon. The rhythm also makes the summary easier to write, because the shape is already in your head and the details are easier to find.
A stalled thread needs a decision, not another nudge. Ask whether the work still matters, who can decide, and what the smallest next step is. If the work still matters and the other person is the blocker, offer two paths and a deadline. If the work no longer matters, say so and close the thread. Replying under the original thread keeps the history visible, which makes the closure credible. A stalled thread that ends with a clear decision is better for everyone than one that lingers for months. Write the three questions on a card and answer them before you open the thread.
When you offer paths, make them genuinely different. One path might be to proceed with the current draft; another might be to pause and revisit next month. Say what happens under each path, including what happens if no one responds. A default outcome named in advance prevents the thread from stalling again, because silence now has a meaning. This is a firm move, and it is easier to make in a calm voice than in a frustrated one, which is another reason to dictate when you are composed. Name the default in the message so silence has a meaning from the first day.
Do not use the thread to relitigate the original decision. A stalled thread is about the next step, not about who was right. Keep the reference short, state the choice, and move on. If a history of missed commitments exists, address it outside the thread with the person directly rather than in a message that others may read. Dictating under the thread makes it easy to say too much because the words flow; the discipline is to stop after the decision and let the message be short. Keep the decision in the thread and the relationship conversation outside it, in a direct message.
Close stalled threads explicitly. Thanks, closing this for now, we can reopen in January is a complete message. It removes the thread from the mental list, and it tells the other person that silence is acceptable. If you reopen later, reply under the same thread so the history returns with the new message. Explicit closure is a courtesy that also protects your attention, because an open thread you have decided to abandon still costs something every time you see it. A closed thread also frees the attention you were spending on it every morning. Write the closure down so you do not reopen it by accident.
A follow-up rhythm is a schedule, not a mood. Decide which threads get a follow-up after two days, which after a week, and which never. Write the rule where you will see it during triage. Then dictating the follow-up becomes a small, predictable task rather than a decision you make under pressure. Rhythms also protect relationships, because a follow-up that arrives on a predictable schedule reads as process rather than impatience. The person on the other side learns what to expect, and expectations reduce friction. A written rhythm also makes it easy to explain the pattern to a colleague.
Block ten minutes for follow-ups at the same time each day. During the block, open the threads on your list, reply under each one, and move on. Do not draft new messages during this block; the point is to keep existing threads moving. If a thread needs a longer reply, move it to a separate block and leave a one-line note in the thread so the reader knows you saw it. This keeps the follow-up block short and honest. A block that expands into general writing stops being a rhythm. A block that ends on time is a block you will still keep next month.
When you add a device, Download Voiskey for macOS and Windows and confirm the reply flow before the first follow-up block. The rhythm depends on the shortcut firing immediately, because the block is short and interruptions are expensive. Test the reply body with one sentence, then run the block. Keep the schedule and the thread list in the same place on every device so the routine does not fork. A rhythm that only works on one computer is a habit waiting to break. If the layout differs, write the new position into the note before the first block, and test it once.
Review the rhythm at the end of each month. Which follow-ups got replies, which needed a second message, which threads closed cleanly? Adjust the intervals based on what happened, not on what you assumed would happen. If most follow-ups need a second message, the first one is probably too vague. If most close cleanly, the rhythm is working. Keep the review short: three questions, ten minutes, one change at most. A rhythm that is adjusted slowly is more likely to last than one that is redesigned every week. Keep the review notes next to the schedule so the next adjustment starts from evidence.
Reference the earlier note in one line, state exactly what you need, and offer an easy way to answer, such as a yes, a date, or a link. Speak the three parts in order. Because the thread is visible, the reference can stay short and the ask can stay specific.
Open with what is done, then what is in progress, then what is blocked and who can unblock it. Use names and dates instead of vague status phrases. End with the one thing you need, even if that thing is nothing, so the thread can close cleanly.
When the thread has stalled and another status request will not move it. Offer two genuinely different paths with a deadline and say what happens if no one responds. A named default outcome gives silence a meaning and prevents the thread from stalling again.
Pick a fixed time each day and keep the block to about ten minutes. Work only threads on a written schedule, such as two days or one week, and move longer replies to a separate block. A short, predictable block keeps existing conversations moving without becoming general writing time.

Download Voiskey for Mac and Windows and keep every follow-up in its thread.
Use it across macOS, Windows, iOS, and Android