How to use Claude voice mode and keep your next steps

To start Claude voice mode, open a chat and select the sound-wave symbol: at the lower right on web or Desktop, or beside the microphone in the mobile input field. You speak and hear replies; Anthropic’s voice guide↗ (opens in a new tab) distinguishes this from dictation, which turns speech into typed text. After a useful conversation, fenbs can keep the decisions and next steps you choose to save, so the work can continue beyond that chat.

Where do you start a voice conversation?

Use this short setup for the device in front of you. Anthropic documents voice as a beta on web, Claude Desktop, iOS, and Android, with the experience designed to work best on phones. Its guide covers all current plan families; regular usage limits still apply.

1. On web or Desktop, sign in, start a chat, and select the sound-wave symbol at the lower right.
2. On iOS or Android, open the Claude app and select the sound-wave voice icon next to the microphone in the input field. Choose a voice when prompted.
3. Check that Claude has permission to use the device microphone, then ask one short question you can easily judge.
4. Listen to the reply and ask a follow-up. Begin with an ordinary question before discussing work that needs exact names, numbers, or dates.

A useful first test is, “Help me prepare three questions for a design review.” Check whether the reply answers that request before moving to a more complicated discussion. For choosing a client rather than using voice itself, see Claude app versus website.

How do you control listening and switch to typing?

The documented voice controls↗ (opens in a new tab) include hands-free and push-to-talk. Hands-free listens for your speech and responds to pauses. Push-to-talk lets you hold a button while speaking and release it when you finish, which is useful when background conversation keeps interrupting your thoughts.

Switch to text when an exact spelling matters. You might say the problem aloud, then type the document title or the sentence you want reviewed. Anthropic says switching between voice and typing keeps the same conversation context, so you can choose the input that makes each part easiest.

On web and Desktop, Stop ends voice. To change the voice there, the guide names Settings > Capabilities > Voice settings, with Settings > General as an alternate layout. Choosing a voice is separate from deciding what belongs in the work record: a comfortable conversation still needs a checked conclusion.

What should you check when the audio is not working?

Start with a small test rather than repeating a long explanation. Say one sentence, check that Claude understood it, and change one thing at a time. That makes it easier to tell whether the problem is microphone access, recognition, or the response you hear.

• No useful input: check the device microphone permission for Claude. Use the settings for your own device rather than assuming every phone and computer has the same path.
• Misheard words or interruptions: move somewhere quieter or try push-to-talk. Repeat only the unclear part.
• Choppy replies: check the connection, competing resource use, and battery. Try the same short question again after addressing the likely cause.
• No response: check usage limits, then leave and re-enter voice. If this is an Enterprise account, its owner can also check whether the organization has disabled voice.

Those checks come from Anthropic’s troubleshooting advice↗ (opens in a new tab). A problem in the spoken session does not establish that the rest of the app is broken. For a separate Desktop display problem, use the Claude Desktop blank-screen guide.

How do you get a useful outcome instead of a long conversation?

Give the discussion one small job. For example: “Help me compare these two introductions. Ask what the reader needs, then suggest one revision.” That is easier to review than asking for broad advice about an entire presentation, research assignment, or client meeting at once.

At natural pauses, ask for a recap with three parts: what you agreed, what still needs checking, and the next action. Read that recap before treating it as a decision. If Claude turns a suggestion into something that sounds approved, correct the wording while the distinction is fresh.

For a research discussion, keep the source and your interpretation separate. “This passage says X” and “we should do Y” need different checks. Our guide to Claude for qualitative research covers that broader research workflow; here, the immediate goal is a short, accurate outcome from the conversation you just had.

What remains after you stop talking?

Anthropic says textual transcripts are saved in chat history↗ (opens in a new tab). That gives you something to review after speaking. It does not establish that the original audio recording is available to download, or that a separate list of action items has been exported for you.

Review names, dates, and any conclusion you plan to reuse. A transcript is a record of the exchange; your lasting work record should say which parts you accepted. Save the goal, the checked result, an unresolved question, and the next step in your own words. For important work, read the final recap once more yourself.

This is where a record outside the conversation helps. How fenbs works explains how connected assistants read the same saved work when you return. The wider AI at work guides cover similar ways to keep useful outcomes from everyday AI sessions.

How to keep your voice-session next steps with fenbs?

Keep the part you want to carry on with, so you can return on another device or in another AI without explaining everything again. A few checked sentences are usually more helpful than every word you said.

1. Create a free account.
2. Connect Claude to fenbs. Anthropic supports custom connections, with account and organization controls described in its connector guide.
3. Save what you learned, what you decided, and the next thing to do. Correct any names or dates before saving.
4. When you return, ask your connected assistant to read the saved work and tell you where to start. Add what changed before you finish again.

Anthropic’s custom connector guide↗ (opens in a new tab) explains its connection permissions. fenbs does not import your Claude chats or preserve an audio recording. If all you need is to reread one transcript in Claude, its own chat history may be enough. For messages arriving in a coding session, see Claude Code channels.