Learn Cue · task-based tutorial

Write a Project Follow-Up Email by Voice with Cue

Keep the email you are answering in view. Say what needs to happen next, supply the relevant facts, and turn the result into a draft you can check before sending.

By the Cue product team · Updated . Written from product-source review. Exercises and outputs are illustrative, not recorded Cue runs. Follow the controls shown in your installed version.

How do you write a follow-up email by voice?

Open the relevant conversation, use Cue Dictation to speak your wording or Cue Agent to turn a supplied note into a draft, then check the names, dates and requested action before sending. Keep a proposed deadline separate from a date the recipient has agreed to.

Need: Cue set up on your computer, an editable draft, and the facts you are authorized to use. Result: a reviewable subject and body with one clear request; sending remains your decision.

Prepare the source and choose a mode

A useful follow-up answers three questions: what is already true, what you need from the recipient, and when you need it. Voice is a convenient way to explain those relationships while the conversation is still in front of you. The goal is a specific next step, not a longer, more polished version of an unclear request.

  1. Open the relevant email or project note. Keep only the portion needed for this reply visible. If you are practicing, use the fictional note below in a blank document instead of a real inbox.
  2. Separate confirmed facts from your proposed next step. “The review is finished” and “Could you review it?” mean different things. Resolve pronouns such as “she,” “it,” and “next week” before asking for a draft.
  3. Use Dictation when you already know the wording: focus the email body, start the shortcut shown in Cue Settings, wait for the recording state, and speak the message. Check where the text landed.
  4. Use Agent when you want Cue to transform the note into a reply. Invoke it with your configured Agent shortcut while working in the app, identify the source, and ask for a draft only. If Cue cannot read the relevant text, paste the short excerpt into the task yourself.

Bringing the Agent into this workflow means starting from the email you are handling, not assuming it can search your whole mailbox. Current-app context depends on permissions, the installed version and what is actually available. A shortcut can launch a task even when the app does not expose the content the task needs.

Practice: ask for a decision without inventing a promise

Use this fictional source note. The requested date is a proposed deadline, not a commitment from the recipient.

Source note E-01: Project Cedar has 8 onboarding questions. Mina sent draft 2 on 16 November 2026. Rowan has not approved the questions. We want Rowan to review questions 3 and 6 by 18 November 2026 at 14:00 UTC. The pilot date is not decided. No attachment has been added to the email.

If you want to dictate the message directly, focus an empty draft body and say:

Hi Rowan. Mina sent draft two of the eight onboarding questions on sixteen November. Could you review questions three and six by eighteen November twenty twenty-six at fourteen hundred UTC? The pilot date is still undecided. Please let me know if that review time works for you.

For an Agent-generated draft, supply E-01 and say this request instead. Keep instructions out of Dictation unless you intend to insert those words as text.

Use only source note E-01. Draft a concise project follow-up to Rowan, with one subject line and an email body. Request a review of questions 3 and 6 by 18 November 2026 at 14:00 UTC. Make clear this is a request, not an agreed deadline. Preserve the undecided pilot date. Do not claim there is an attachment or that anyone approved the questions. Draft only; do not send or change the inbox.

Illustrative draft, not a recorded Cue result:

Subject: Cedar: review questions 3 and 6?

Hi Rowan,

Mina sent draft 2 of the 8 onboarding questions on 16 November. Could you review questions 3 and 6 by 18 November 2026 at 14:00 UTC? Please let me know whether that timing works for you.

The pilot date is still undecided.

Thanks!

The exact wording can vary. Compare the names, question numbers, dates and uncertainty against E-01. A polite message that invents approval fails the exercise; a plain message that preserves the facts and makes the request clear passes.

Revise the tone without rewriting the facts

A narrow follow-up is easier to verify than “make it better.” Keep the source and draft together in the current task, then change one property at a time.

  • Shorter: “Keep the subject. Reduce the body to three sentences. Preserve both question numbers, the requested time and the undecided pilot date.”
  • Less formal: “Use a friendly internal-team tone. Do not add enthusiasm about a launch or imply Rowan agreed.”
  • More actionable: “Put the review request before the background. Keep one request; do not add a meeting invitation.”

When the source changes, supply the change explicitly: “E-02 replaces the requested review time with 19 November 2026 at 10:00 UTC; all other E-01 facts are unchanged.” Do not expect a new chat or another Agent to know the revision. Check that the final draft has one current time, not both the original and revised times.

For a real email, a subject line, the last relevant reply and your intended action are often a better starting bundle than an entire inbox thread. Add older context only when it changes the answer. Remove unrelated personal information before handing material to a different Agent or service.

Check the draft before sending

  • Facts: Mina, Rowan, 8 questions, draft 2, questions 3 and 6, and the dates must match E-01.
  • Commitments: the requested time is not a confirmed deadline. No sentence may imply approval or announce a pilot date.
  • Recipient and attachment: select the correct recipient yourself, check To/Cc, and verify any attachment is actually present before mentioning it.
  • Placement: confirm the text appears once in the intended draft, not in the subject field or an unrelated conversation.
  • Send: read the final draft in the email app and send it yourself when ready. A generated answer is not proof of delivery.

This tutorial does not configure automatic email sending or a mailbox integration. If you later authorize a supported app action, specify the exact draft and verify the destination afterward. Do not broaden access just because a first attempt cannot find an email.

Recover without duplicate messages

The email is fluent but factually wrong

Name the error and the authoritative note: “E-01 says the pilot date is undecided. Remove the launch date you added.” Ask for the draft again and recheck all facts, not only the sentence you corrected.

My instruction appeared in the email body

You may have used Dictation for an Agent request. Remove only the unintended text after checking the draft. Switch to Agent for transformation, or dictate the message itself. Use the mode and shortcut displayed in Cue Settings.

No text appeared, or the app seems to have stalled

Inspect the draft first. Wait for processing to finish before retrying. If Cue visibly offers Copy, copy once and paste into the intended field after confirming it is still empty. Do not repeat a send request when delivery status is uncertain.

Next, try turning a meeting record into an action list before drafting the follow-up, or visit the email workflow overview.

Try it with Cue

Use your configured shortcut and verify the active mode in Cue Settings. Available app context and actions depend on permissions, version and account. Read the privacy policy before providing confidential material; this guide does not promise all processing stays on your device.

Get Cue for your computer · Current plans

Need help or found an error? Contact Cue support or email eli@sophoninc.com. Include your Cue version, platform, mode and a redacted example. Do not send passwords, tokens or private meeting material.