Talking back

What it is

Talkback lets a squad leader answer the command channel from an opted-in party channel. The squad bot receives that channel's encrypted packets, but the gate opens only for one authorised person asserting the floor; their encoded packets are played in the command channel and never decoded.

Switch it on

On the board, open Field plan and use the Talkback switch on a party channel's row. The first switch you turn on shows a confirmation explaining that the squad bot will stop being deafened, the channel's encrypted voice will reach Warcaller, and only an authorised person holding the floor will be played. Talkback is on every plan, and each channel is opted in on its own: switching it on for one party channel does nothing to the others.

Who may talk back

In Who may call, add members' roles to May talk back. Only a member with one of those roles can open the reply floor, whatever key they hold.

Holding the floor

On desktop, set Discord's input mode to Push to Talk and bind a key to Push to Talk (Priority) under Keybinds. That is all a member needs: they do not need Discord's Priority Speaker permission, which only decides whether other people's voices duck while they speak. The key does nothing in Voice Activity mode or on mobile, where Discord sends no priority flag.

That is the only way in: there is no button in the dashboard and no slash command, so a member on Voice Activity, or on a phone, cannot talk back. Discord sends the priority flag only from its desktop apps in push-to-talk mode.

What the channel experiences

While talkback is on, the squad bot appears undeafened and the channel's encrypted packets reach it. Only one person's packets are decrypted at a time, and nothing is decoded in either direction. Use a headset in the party channel to avoid an acoustic loop.