Skip to content
Guide · Single official source

Voice Chat Setup and Calls

A build-safe audio checklist for testing the microphone, choosing the squad channel and making short battlefield calls.

First-match systems guide
Short answer

Use the current audio settings to select and test your microphone, then make short calls about position, direction and intent. The guide avoids a universal push-to-talk key because bindings can differ by platform and build.

Quick facts

GameplaySystemsBeginnerTechnical
Recommended call format
Position → direction → intent
Keybind policy
Confirm the current platform binding in-game
Official boundary
Communication is a launch tip; exact audio UI is build-sensitive
Party Voice Chat
Lobby only; in-match channels are Proximity, Unit and Command
Action chain

Do this in order

4 steps
  1. Select the correct input device

    Open the current audio settings and choose the microphone you actually use. Confirm the input meter reacts to your voice.

    Success signal: The selected microphone shows input activity without changing the device outside the game.

    Failure check: If the meter is silent, check the operating-system permission and the input device before changing in-game keybinds.

  2. Test the channel in a safe moment

    Join a squad and send a short test message before the first push. Keep the message about position, objective or request for help.

    Success signal: At least one squad member acknowledges the message or the voice indicator shows that the transmission is active.

    Failure check: If squadmates cannot hear you, verify the selected channel and mute state in the current UI.

  3. Use short battlefield calls

    Report location, direction and intent in that order. Avoid filling the channel with narration during an active engagement.

    Success signal: A squad member can act on the call without asking you to repeat the entire situation.

  4. Recheck after a patch or device change

    Repeat the input test after a new patch, headset change or platform switch because exact audio labels and controls are build-sensitive.

    Success signal: Your microphone, channel and output device still work in the current build.

Keep calls actionable

A useful call lets a squad member decide what to do next. “North side, moving to the objective” is more useful than a long description that arrives after the situation has changed.

Audio failure check

Separate microphone input, channel selection, mute state and output volume. Test one variable at a time and keep the platform/build in the note. A community clip can show one working setup, but it does not establish the default keybind for every player.

Lobby versus match channels

The official Community Update says Party Voice Chat is currently available in the lobby only. Once a match starts, use the current Proximity, Unit or Command channel shown by the game instead of waiting for a party channel to carry the call.

  • Test the microphone and mute state in the current audio settings first.
  • Use Unit chat for the squad-level call and Command chat only when your role and channel access require it.
  • If a channel is missing or distorted, record platform, build and channel before reporting the issue.