How to dictate emails that still sound like you

Most replies are easier to say than to start writing. You already know whether Thursday works, why the draft is late, or which number needs correcting. The blank compose window makes the answer feel like a writing assignment.

Read the thread, say the answer first, add the context the recipient needs, and review the result before sending. That is enough structure for a useful dictated email.

Answer the actual question first

Suppose a client asks whether they can review a revised layout this week. You know the layout can be ready Thursday, but the photos have not arrived.

You might naturally say:

Hi Morgan, um, yes, we can get you the layout this week. Thursday should work. We still need the photos, though, so those will be placeholders. Can you confirm the page order by tomorrow afternoon?

A sensible final draft would be:

Hi Morgan,

We can send the revised layout on Thursday. The photos are still pending, so that version will use placeholders.

Could you confirm the page order by tomorrow afternoon?

The useful work happened before the cleanup: you supplied the date, the dependency, and the request. Punctuation makes the message easier to read, but it cannot supply those facts for you. This is an illustrative example, not a customer email.

Say the qualification while it is in your head

The tempting short reply is “Thursday works.” It also creates an expectation that the version will be complete. Mentioning the missing photos now saves a clarification later.

Dictation is useful for those qualifications. Say what the recipient can expect, what is still pending, and whether they need to do anything. Stop once that is clear. You do not need to narrate how you reached the decision.

If you change your mind halfway through a sentence, make the correction explicit. “Thursday, actually Friday” gives formatting software a clear revision to apply. Check that it kept the intended date.

Edit meaning before tone

Read the draft for four things: who it addresses, what it promises, when it happens, and what the recipient should do next. Those deserve more attention than making every sentence sound polished.

A friendly rewrite can accidentally turn “we expect” into “we will.” A shorter version can drop a condition. If you use Vokalu’s Command Mode to adjust the tone, compare the revised commitment with the original one before sending.

For ordinary replies, start with a lighter formatting level and increase it only if your drafts regularly need more cleanup. The goal is a message you would have written, including the degree of certainty you intended.

Keep the mail app’s jobs in the mail app

The recipient, subject, attachments, and send action still belong to your email client. Dictating “I have attached the file” does not attach anything. Saying a person’s name does not verify their address.

Place the cursor in the message body, not the address field. Draft there, then check the surrounding email controls. Leave sending as a separate step while you are getting used to voice input.

For a basic starting point, Microsoft documents Windows voice typing as speech input into a text box, started with Windows + H. Vokalu adds its own shortcut, formatting controls, and selected-text rewriting. Try both on a few ordinary replies and compare the editing you have left to do.

Try it on a reply you already understand

Do not start with an unfamiliar contract or a sensitive escalation. Pick a routine message where the answer is clear. Dictate it, read it once, and send only after checking the facts.

If the draft sounds like you and the recipient can act on it, keep that approach. You do not need a new writing personality just because you used a microphone.

See Vokalu’s email workflow for the shortcuts and team messages for adapting the same method to a channel update.