Audio in Remote Support

Prev Next
This content is currently unavailable in French. You are viewing the default (English) version.

In-Session Audio lets you talk with end users through your computer microphone and speakers or headphones during ScreenMeet Remote Support and Beam sessions. This article explains how agents start an audio-enabled session, use the audio controls, and resolve common audio issues.


Prerequisites

Confirm the following requirements before you start an audio-enabled session.

  • Product: ScreenMeet Remote Support or ScreenMeet Beam (attended sessions only).

  • End user operating system: Windows or macOS. Linux, iOS, and Android clients do not support audio.

  • Client version: ScreenMeet client version

    • Windows version 3.139.32 or later.

    • MacOS version 3.141.1828 or later.

  • Connection type: WebRTC. Audio is disabled if the session falls back to Tiles mode.

  • Hardware: A working microphone and speakers or headset on both the agent and end user devices.

  • Organization policy: Your administrator has set Session Audio to Agent's Choice or Always Required.

CRM Required Roles and Permission Sets

If your organization uses custom roles in ServiceNow or custom permissions in Salesforce, your administrator must assign you the audio role or permission set.

Platform

Role or Permission Set

Grants

ServiceNow

x_prois_sm.x_feature_remotesupport_sessionaudio

Base access to use audio.

ServiceNow

x_prois_sm.x_feature_remotesupport_sessionaudio_agent_choice

Ability to turn audio on or off when you create a session. Requires the base role.

Salesforce

screenmeet.remotesupport Session Audio

Base access to use audio.

Salesforce

screenmeet.remotesupport Session Audio Agent Decide

Ability to turn audio on or off when you create a session. Requires the base permission set.

Missing Audio Toggle

When the organization policy is Agent's Choice, you need both the base audio permission and the agent choice permission to see the audio toggle. If the toggle does not appear, contact your ScreenMeet administrator.


Start an Audio-Enabled Session

Audio is set when you create the session and stays fixed for the entire session. You cannot turn audio on after the session starts.

  • Agent Console: When you create a Remote Support or Beam session, turn on Enable audio.

  • ServiceNow or Salesforce: Select the audio option in the ScreenMeet support widget before you generate the session invitation.

If your organization policy is Always Required, audio is enabled automatically for every eligible session and no toggle appears.

What the End User Sees

When the end user opens the session link, the consent window states that audio is active: "[Agent Name] will be able to talk with you during this session. Your microphone will start muted."

After the end user clicks Approve or Join, the session starts and audio connects automatically. All participants join muted.

Audio Cannot Be Added Later

If you created the session without audio, end it and start a new session with audio enabled.


Use the Audio Controls in the Viewer

The ScreenMeet Viewer provides an audio footer for quick actions and an Audio Settings dialog for device configuration.

The audio footer sits at the bottom of the Viewer window. It shows connection status, speaking indicators, and a Mute / Unmute toggle. The footer stays available when the Viewer toolbars are collapsed.

Audio Settings

Use the Audio Settings dialog to choose devices and test audio.

  1. In the Viewer, open Support Tools > Audio.

  2. Select your microphone and speaker devices.

  3. Test your microphone input and run the speaker test sound.

  4. Review the connection health indicators.

Default disconnect behavior

If your selected USB or Bluetooth headset disconnects during the session, ScreenMeet switches to your system default device. When the headset reconnects, ScreenMeet switches back to it.

End User Microphone Privacy

You cannot unmute an end user's microphone, even when the end user has granted full remote control. If the end user needs help unmuting, direct them to the Mute / Unmute button in the participant bar at the top of the ScreenMeet client. The end user can also select devices and test audio on the client Audio page.


Add Agents to the Audio Conversation

Up to four agents can join the audio conversation with the end user at the same time, for example when you escalate to a tier 2 specialist.

  • Joining agents connect muted so they do not interrupt the conversation.

  • Speaking indicators show who is talking.

  • If a fifth agent joins, the session displays Agent audio limit reached. That agent can still view and assist with the screen session without audio.


Audio in Session Recordings

If your organization has session recording enabled, ScreenMeet records audio from the end user and all participating agents and synchronizes it with the screen video. Replay the recording in the Session Details player in the Agent Console or the CRM record.

Combined Audio Track

Recordings mix all speakers into a single audio channel. Individual speaker tracks are not available.


Troubleshoot In-Session Audio

Use the audio status indicator in the Viewer to identify the connection state and the action to take.

Status

Meaning

Action

Audio connected

The audio connection is healthy and active.

None.

Connecting audio

ScreenMeet is establishing the secure audio connection.

Wait a few moments for the connection to complete.

Audio reconnecting

ScreenMeet detected a temporary network interruption.

Wait while ScreenMeet reconnects automatically.

Microphone unavailable

No microphone is detected, or browser or OS permissions are denied.

Check the device connection and confirm the browser or OS allows microphone access.

Speaker unavailable

No audio output device is found.

Check the headset or speaker connection and confirm the output device in Audio Settings.

Unstable network connection

ScreenMeet detected high jitter, packet loss, or latency.

Check local bandwidth or switch from Wi-Fi to a wired connection. Audio controls remain active.

Audio paused with session

You paused the screen sharing session.

Resume the session. Audio resumes automatically.

Unsupported

The end user is on an unsupported OS or an older client version where Audio is unsupported.

Confirm the end user runs a supported Windows or macOS client. The session continues without audio.

Review Audio Statistics

To diagnose audio quality during an active session, click the caret next to User is connected in the Viewer. End users can open the same data from Session statistics on the client Audio page.

  • Packet Loss: The percentage of dropped audio packets. Loss above 5% can cause robotic or cut-off speech.

  • Jitter: The variance in packet arrival timing. Jitter above 50 ms indicates an unstable network route.

  • Latency / Round-Trip Time: The delay between endpoints.

ScreenMeet applies echo cancellation, noise suppression, and packet loss concealment automatically. If the session falls back to Tiles mode, audio disconnects and the screen session continues.


Limitations

  • You cannot enable audio after a session starts.

  • You cannot unmute an end user's microphone.

  • Audio is not supported on Linux, iOS, or Android. Sessions on these platforms continue as screen-only sessions.

  • Audio requires a WebRTC connection and is unavailable in Tiles mode.

  • A maximum of four agents can participate in audio at once.

  • Beam audio is intended for attended sessions where the end user is present at the device.