Dictating Prompts for Email Rewriting

A spoken method for rewriting email without losing facts, promises, or tone.

Voiskey Voiskey Team
Voice PromptingChatGPT WorkflowDictating Prompts Email

Decide What the Rewrite Must Preserve

Dictating Prompts for Email rewriting starts with a preservation list. Before you speak, decide what the rewritten message must keep: the commitment you made, the deadline, any figure or name that cannot change, and the reason you are writing at all. Say that list first in the prompt, then say what may change, such as length, greeting, or level of detail. A rewrite that preserves the wrong thing is worse than no rewrite, because it reads smoothly while quietly changing the deal. Keep the list to five items and speak it as plain statements. The assistant should treat those statements as fixed points and build every option around them.

Separate facts from phrasing before you dictate. Facts include who agreed to what, when it happens, and what the reader must do next. Phrasing is everything else: sentence length, courtesy, structure, and sign-off. Dictate the facts in short statements and label them as facts. Then ask for a rewrite that may change only phrasing. This separation gives you a clean test later: scan the result for each fact and confirm it survived. It also stops the assistant from softening a hard deadline into a vague hope, which is a common and expensive rewrite failure. When a fact is uncertain, mark it as uncertain rather than letting the draft decide.

Name the reader, the relationship, and the history. A note to a client who is already frustrated needs a different opening than a note to a colleague who missed a review. Say the reader's role, what they already know, and what they last heard from you. Include one line about the outcome you want: an apology accepted, a meeting moved, a decision confirmed. The assistant can then choose a tone that fits the relationship instead of a generic professional voice. If the history is complicated, summarize it in one sentence rather than pasting the whole thread. A short, accurate context line produces a better rewrite than a long, ambiguous one.

State what the rewrite must not do. Common bans include adding new promises, apologizing for things you did not do, inventing a reason for the delay, or turning a firm no into a maybe. Say these bans explicitly, because a fluent rewrite will otherwise smooth over tension by adding language you never approved. Add a length limit and a format limit, such as three short paragraphs with one clear ask. If the message must sound like you, say which phrases are yours and should stay. The bans are the guardrails of the task, and they are easiest to speak before the draft exists. Keep them short, specific, and in the order you would check them.

Describe the Reader and the Tone

Tone is a set of choices, not an adjective. Instead of asking for a friendly email, describe the choices: open with the point, use the reader's first name, keep sentences under twenty words, and close with one action. Add what to avoid, such as exclamation marks, jargon, or passive constructions. Say whether the message should be warm, neutral, or formal, and give an example sentence in that register. A single example does more than three adjectives, because it shows the assistant the rhythm you want. Speak the example slowly and check that the punctuation lands where you intended, since punctuation carries much of the tone.

Match the channel and the relationship. A short internal note can skip the greeting; an external message may need a formal opening and a clear subject line. Say the channel, the reader's seniority, and whether this is a first contact or a reply in an ongoing exchange. If it is a reply, state what you are responding to and what you are not addressing. This prevents the rewrite from answering a question that was never asked. For sensitive messages, ask for a version that is direct but courteous, and check that it does not read as cold. Tone that fits the channel gets read; tone that fits only the writer's mood gets ignored.

Ask for a specific emotional target and a specific restraint. For example: acknowledge the delay without groveling, and keep confidence without sounding indifferent. The pair matters, because a rewrite asked only to be apologetic tends to overcorrect into weakness. Say which sentence carries the emotion and which sentence carries the request, and ask the assistant to keep them separate. Readers can forgive a firm request if the acknowledgment feels sincere. They distrust a message that mixes apology and demand in the same breath. Naming both targets gives the assistant a narrow path instead of a vague instruction to sound better.

Read the tone out loud before you judge it. A rewrite that looks fine on screen can sound stiff or sharp when spoken, especially if the sentences are long or the punctuation is heavy. Place the draft in your message window, then read it back and listen for the point where your attention slips. That point is usually where the reader will stop trusting the message. Adjust the prompt, not just the sentence: if the opening is slow, ask for the ask in the first line. Tone improves fastest when you test it with your ear rather than your eye, and a short spoken sample usually reveals a problem faster than a reread.

Dictate Rewrite Options, Not One Draft

Ask for three versions with different strategies rather than one polished rewrite. A useful trio is shortest version, warmest version, and most formal version. Each version should preserve the same facts and the same ask, changing only emphasis and register. Speaking the trio takes a few extra seconds and saves a round of revision, because you can compare approaches instead of imagining alternatives. Label the versions in the prompt and ask the assistant to keep them in that order. A single draft invites tinkering; a small set invites a decision, and decisions are faster than endless polishing. The set also shows which strategy the reader is likely to accept without a second note.

Put the ask in a fixed place across all versions. If the message requests a meeting, a payment, or an approval, say that every version must state the ask in the final paragraph and repeat it in the subject line. This consistency lets you compare tone without losing the purpose. Ask the assistant to number the versions and to add a one-line note describing the strategy of each. The notes help you explain your choice to a colleague who reviews the message. When the versions differ in substance rather than style, stop and fix the facts in the prompt before choosing.

Dictate a revision instruction as a sentence, not a mood. After you see the options, say which one is closest and what to change: shorten the second paragraph, move the apology after the explanation, replace the phrase about timing with the exact date. Vague instructions such as make it better produce another generic draft. Specific instructions produce a targeted edit you can verify. If the assistant changes something you did not ask about, restore it and repeat the instruction with a boundary. The goal is a controlled edit, and control comes from naming the exact sentence and the exact change.

Keep the original message beside the options while you choose. The best rewrite is the one that a reader can act on without rereading, and comparison is easier when the original is visible. Check that each option still carries the commitment, the date, and the ask. Check that no option introduces a promise or a reason that was not in your brief. If two options are close, pick the shorter one and test it aloud. Length is not a virtue by itself, but a shorter message with the same content is easier to answer. Choose once, then edit the chosen version directly instead of blending all three into a fourth draft.

Compare Versions and Choose the Edit

Put the three versions in a single view and score them against your preservation list. For each version, tick every fixed fact, every ban, and the ask. Then read for the one quality you care most about in this message: clarity, warmth, or brevity. A version that wins on style but loses a fact is out. This scoring takes less time than reading each version twice, and it turns a taste argument into a visible checklist. If no version passes, the prompt is the problem, not the drafts. Rewrite the brief with the missing element and generate a fresh set rather than patching a failing draft.

Edit the chosen version in the field where you will send it. This is where a system-level tool earns its place: press the shortcut, speak the corrections, and the revised language appears at the insertion point in your message window. There is no export, no second app, and no copy-paste step that can drop a paragraph. Read the final message once for names and dates, then send. If you need to explain the change to a reviewer, dictate a short note beside the draft. Teams that want this workflow can download Voiskey and run one rewrite end to end before adopting it.

Check the edges that rewrites often break. Greetings, subject lines, attachment references, and sign-offs are easy to lose when the body is rebuilt. Confirm that the subject still matches the body, that any promise to attach something is either fulfilled or removed, and that the closing name is correct. If the message includes a thread, confirm that the rewrite does not contradict what you already said. These edges look minor until a reader notices that the attachment is missing or the subject promises a decision the body does not request. A thirty-second edge check protects the credibility of the whole message.

Keep a small record of what worked. For each rewrite, note the reader, the purpose, the version you chose, and the one instruction that made the difference. After a dozen messages, patterns appear: certain readers respond to a short opening, certain requests need the ask in the subject line, certain apologies need the explanation first. Turn those patterns into default lines in your prompt. The record does not need to be elaborate; a short list in a notes file is enough. What matters is that the next rewrite starts from evidence rather than from memory. A record of decisions is more useful than a folder of discarded drafts.

Keep Rewrite Prompts for Recurring Email

Build a template for each recurring message type: the delay notice, the meeting request, the status reply, the polite follow-up. Each template should carry the preservation list, the tone target, the format limits, and the bans. Leave slots for the reader, the date, the ask, and the specific reason. Speak the template once, save the text, and edit the slots before each use. A template is not a canned message; it is a brief you fill in, and the rewrite still adapts to the reader. Five templates cover most routine email, and each one takes minutes to set up.

Test each template on a real message before you rely on it. Speak the prompt with actual facts, generate the options, and choose one. If the result needs more than two corrections, the template is missing a constraint. Add the constraint and test again with a different message of the same type. Keep the examples beside the template so a colleague can see what good output looks like. When a message breaks the pattern, write a new template rather than forcing the old one. Templates earn their keep only when they survive real use, not when they look tidy in a document.

Share the templates with the people who write the same messages. Put them in the team space with a short note on when to use each one and which facts must always be preserved. The team plan offers shared vocabulary and workflows, so names, terms, and tone choices stay consistent across writers. Ask each person to run one template on a real message and report the correction they had to make. Collect those corrections into a monthly update. Shared templates reduce the range of tone in customer-facing messages and make review faster, because reviewers know what the standard looks like.

Review the library each quarter and delete what you no longer send. A template for a process that ended last year is a trap for whoever finds it next. Keep the current set small, dated, and owned by a named person. If a template keeps producing drafts that need heavy edits, retire it and rebuild from a message that worked. Anyone can start with one template and one real message: download Voiskey, speak the brief into the message window, and compare the result with the version you would have typed. The comparison tells you whether the template is ready to share.

FAQ s

Voiskey is an AI voice typing app that works in the message window you already use. Press a shortcut, speak what the message must preserve, who reads it, the tone, and the bans, and the prompt appears at the insertion point. Filler words, stutters, and self-corrections are removed, so the rewrite brief is clean.

Voiskey learns names, jargon, acronyms, and spelling preferences, so people, projects, and dates stay as you say them while you dictate the preservation list. It also removes false starts and self-corrections, which keeps the fixed facts from arriving twice in different forms. Review the brief once before the assistant responds.

Yes. Voiskey is system-level, so text appears at the insertion point in any app or text field. You can dictate the rewrite brief and then the corrections in the same message window, with no export or copy-paste step. The draft and the final message stay in one place, which makes the preservation check easier.

Voiskey supports more than one hundred languages and translation. You can dictate the rewrite brief in one language and ask for the message in another, while keeping names, dates, and commitments in their original form. Ask a fluent reader to review the result before sending, because courtesy and formality differ across languages.

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 rewrite your next email by voice.

Use it across macOS, Windows, iOS, and Android

Use it across