Write a Project Follow-Up Email by Voice with Cue

This English prompt includes the fictional source and the request. Try it unchanged first. For your own task, replace the entire source note and update the names, facts and requested time together.

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.

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.

Copying only copies text. It does not open Cue, run a task or send an email. You can also select and copy the text manually.

02 · Make a reviewable draft

How to use

1. Prepare a blank draft

   Keep the E-01 source nearby. Use a blank document for practice, so no real recipient or inbox is involved.

2. Open Cue Agent

   Use the Agent control or shortcut shown in your installed Cue Settings. Supply the source explicitly; if Cue cannot read it from the app, paste the short excerpt into the task yourself.

3. Ask for the draft

   Give Agent the request above. For a spoken request, wait for the recording indicator. Use Agent for instructions; Dictation inserts the words you speak.

4. Check, then place the text

   Compare the response with E-01 before copying it into your draft. Confirm the requested time stays a request, the pilot date stays undecided, and no attachment is invented. Sending remains your decision.

The exercise below shows an illustrative draft, not a recorded Cue run.

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.

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

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.

Illustrative draft, not a recorded Cue result:

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

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

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.