Play With Friends, Private Lobbies, and Voice Chat

Form the party before the queue

Choose one leader, send invitations from the current in-game party surface, and wait until each player appears in the group. The exact menu labels can differ by platform or update, so this guide does not preserve an undocumented button sequence. The observable checkpoint is the roster: every intended account should be visible before the leader selects a mode or begins matchmaking.

Update every client first. For a mixed PC, PS5, and Xbox Series X|S group, confirm crossplay is enabled wherever the current build exposes that choice and make sure each console account satisfies its platform's online multiplayer requirement. A received invitation does not prove that the player joined the roster, and a complete roster does not prove that the queue has found a server; keep those stages separate.

If one player is absent, do not cycle the queue. Have that player return to the party surface, confirm the intended account and current game version, then recreate the group under the same leader. One clean rebuild gives a clearer result than several invitations from different leaders.

Choose public or private play

The official update feed in the source snapshot records private lobbies as an existing feature. Use public matchmaking when filling open slots matters and the group accepts other Responders joining. Use a private lobby when the invited roster wants controlled practice or does not want the queue to add public teammates.

Private describes who can enter through the selected lobby path; it does not make a networked session offline, waive platform account requirements, or guarantee that every invite will resolve. It also does not replace group consent about recordings, streaming, or external voice channels. Read the current lobby labels and roster state before launch rather than assuming an old screenshot still matches version 1.0.3.1.

If the party is smaller than the intended run group, decide before queueing whether public fill or a fixed private roster is more important. Switching that choice after a failed attempt changes the test condition and can hide the original invite problem.

Test voice where it operates

The official Steam listing in the 2026-08-20 snapshot confirms proximity voice chat. Proximity means the useful voice path depends on in-game distance, so test input and output after spawning near a teammate rather than from opposite ends of a route. Keep the first check simple: one player speaks a short phrase, another confirms reception, and then the roles reverse.

Use short calls for route direction, resources, infection, regrouping, and extraction. When the squad separates, silence may reflect distance rather than a failed microphone. If the group requires continuous voice regardless of in-game position, choose a platform or external party channel deliberately; this source set does not claim that the in-game channel guarantees long-range communication.

Voice presence is not a complete privacy or moderation specification. The official listing confirms the feature but the local snapshot does not document every mute, reporting, recording, parental-control, or platform-permission behavior. Use the current client and platform controls for those settings instead of assuming parity.

Run a pre-session check

Before a planned session, confirm six things in order: every client is current, each intended account can access online multiplayer, the crossplay choice matches the platform mix, one leader owns the party flow, the roster is complete, and the selected public or private state matches the group plan. After spawning, test proximity voice while nearby.

Record the earliest failed checkpoint and any exact error text. That evidence points to the next action without making unsupported guesses about server health, account bans, NAT behavior, or platform outages.

Recover a broken group without mixing causes

If a member is absent from the party list, stop before queueing. Have that player return to the main party surface, recreate the group under one leader, and confirm the roster again before testing a match.

If invitations fail before the roster forms, continue with the invite-problem guide. If the complete roster enters a queue but cannot reach a session, compare the dated server and known-issue record. If only voice fails, retest at close in-game distance and inspect the current device, platform permission, and mute state without changing the lobby at the same time.

This procedure is bounded to the official feature and update sources captured on 2026-08-20. It does not promise that menu layouts, subscription names, voice controls, or service state will remain unchanged after the next patch.