You are reading a draft and know what needs changing: the introduction is too long, the main point arrives late, and one section sounds too technical for the reader.
You could stop, move to the chat box, and type all of that. Sometimes it is easier to say it while the document is still in front of you.
Voice in Upfyn gives you another way to work with the same assistant, project, and available tools.
Start with a moment where speech helps
Voice is useful for describing an outcome, giving feedback, capturing an idea, or asking for an explanation. You can use it across Analyst and Developer.
Try a short request while reviewing a document:
Shorten the introduction. Keep the main finding and the source reference, then move the background detail into the next section.
Or ask for help understanding a result:
Explain the three unresolved items in the latest report. Tell me which one needs my decision first and why.
The benefit is being able to give direction while your attention stays on the work.
Name the thing you are talking about
In person, you might point and say “change that.” An assistant needs a reliable target. Name the document, section, file, or task, especially when several things are open.
“Rewrite the conclusion of the customer brief” gives more context than “make the ending better.” If a value must remain exact, say that too.
You can move between speech and typing. A long identifier or URL is often easier to paste. Voice works best when it complements the way you already explain things.
Check what was heard before exact actions
Names, dates, times, and figures can be misheard. If you dictate a schedule for Tuesday at nine, review the written timing before saving it. If you mention a customer name, check the intended record before an update.
For a document paragraph, ask for light editing after dictation. That can tidy sentence breaks while preserving the meaning you wanted to capture.
Correct the transcription and paragraph breaks. Keep my phrasing and do not add new claims.
This is a useful way to retain your own voice in the final writing.
Keep action permissions consistent
A spoken instruction uses the same mode and tool permissions as a typed one. If the task involves a connected app or computer action, its normal access and review requirements still apply.
You can set a clear stopping point:
Prepare the reply using the approved dates in this note. Read the draft back before sending.
Fill the form from this record and stop before submission.
That helps distinguish preparing the work from completing an external action.
Use speech for short corrections during longer work
You may not need to dictate the entire task. A quick correction can be enough: “Use the latest brief,” “Keep the original title,” or “Explain what is still missing.”
Review the assistant's response to confirm it understood the change. The conversation should make the updated direction clear for the rest of the work.
Start with a familiar document or report. Try one spoken instruction, inspect the result, and use voice where it helps you stay focused on the task.