Blog

Remote Support in ServiceNow Agent Workspace: How It Works

Your agent has an incident open in ServiceNow Agent Workspace, with every detail of the issue gathered on one screen. The employee's laptop still needs hands-on troubleshooting, so the agent leaves the workspace to open a separate remote support console. After the fix, someone has to retype what happened into the incident, and the record holds only what that person remembers to write.

The workspace itself is changing too, because ServiceNow has deprecated ITSM Agent Workspace and published a utility for moving to Service Operations Workspace. This guide walks through how a remote support session runs inside either workspace, from launch to the closed incident. For the case behind running support inside ServiceNow rather than beside it, read our breakdown of native vs. standalone remote support.

TL;DR

Remote support works inside ServiceNow when the session starts, runs and closes on the incident or case the agent already has open. ScreenMeet runs in Service Operations Workspace, Agent Workspace and the Classic UI, so agents can launch sessions in either workspace during and after a migration. The table below follows one Remote Support session from launch to close.

Session stage What happens in ServiceNow What ServiceNow keeps
Launch The agent opens the incident or case, selects the ScreenMeet tab and chooses Remote Support, in Service Operations Workspace, Agent Workspace, CSM/FSM Configurable Workspace, HRSD or the Classic UI. The session is listed in the record's ScreenMeet sessions table, linked to that task or case.
Join The employee enters a PIN at myhelpscreen.com, clicks a generated link or opens a pre-installed MSI, then runs a per-session application. The session PIN and the session code.
Troubleshoot The agent troubleshoots with Remote Support features such as remote control, chat and screenshot, and the employee can pause the session or transfer files. Session logs of events such as remote control approval, shortcuts run and chat activity, plus transferred files as attachments.
Close The session closes and stays linked to the incident or case in the record's ScreenMeet sessions table. Duration, duration connected and a recording link, with recordings attached to the session or parent record, and AI Summarization work notes on the incident with AI Plus enabled.
Access ServiceNow roles and groups decide who can use which remote support features. Authentication through ServiceNow, with session logs open to the ScreenMeet Admin, Agent and Session Viewer roles.

This guide covers the following six parts of the workflow, in order:

  1. What ServiceNow Agent Workspace is and where Service Operations Workspace fits
  2. Where remote support sits inside a ServiceNow workspace
  3. How to set up remote support in Agent Workspace or Service Operations Workspace
  4. How a remote support session works, step by step
  5. What the incident record holds after a remote support session
  6. How ServiceNow roles control remote support access

What ServiceNow Agent Workspace Is and Where Service Operations Workspace Fits

ServiceNow describes a workspace as a suite of tools for agents, case managers, help desk professionals and managers. According to ServiceNow's documentation, agents see every detail related to an issue in one place.

Agent assist sits in the Contextual side panel of the workspace. ServiceNow preconfigures it to search the Incident, Problem, Change, Knowledge and Case tables for possible solutions, using a field from the record the agent has open.

The ITSM version of Agent Workspace is now on its way out. ServiceNow's Store listing for its Migration Utility for Service Operations Workspace states that ITSM Agent Workspace has been deprecated and is no longer supported. The free utility moves common configurations and customizations across, either all at once or a few features at a time. A feature that has been migrated cannot be migrated again, so the order of migration deserves a plan.

ServiceNow's Workspaces page lists Service Operations Workspace for IT services and operations teams that resolve incidents with visibility into issues and outages. Other workspaces on the platform, such as HR Agent Workspace, serve other functions.

Workspace Status on ServiceNow's own pages Remote support with ScreenMeet
ITSM Agent Workspace ServiceNow's Store listing for its migration utility states that ITSM Agent Workspace has been deprecated and is no longer supported. Admins move configurations with the free Migration Utility for Service Operations Workspace, in a partial or complete migration. ScreenMeet's Store listing names Agent Workspace as a place where technicians launch sessions, access tools and view session data.
Service Operations Workspace ServiceNow's Workspaces page lists Service Operations Workspace for IT services and operations teams to resolve incidents with visibility into issues and outages. ScreenMeet's Store listing names Service Operations Workspace, and ScreenMeet's interactive demo starts a Remote Support session there from within ServiceNow ITSM.

Where Remote Support Sits Inside a ServiceNow Workspace

Remote support belongs on the record the agent is already working, not in a second window beside it.

ScreenMeet's ServiceNow Store listing names five places where technicians launch sessions, access tools and view session data. Those places are Service Operations Workspace, CSM/FSM Configurable Workspace, HRSD, Agent Workspace and the Classic UI.

The entry point is a ScreenMeet tab on the open record. Administrators choose which tables display the ScreenMeet headset icon, so remote support appears only on the records of those tables.

ScreenMeet's guided setup lets admins add the product to forms, related lists and workspace components, including a workspace sidebar component. The Store listing describes no separate application and a one-click launch from any workflow.

Agents also install nothing on their own machines to run a session. The ScreenMeet remote support software page states the point directly: "Zero separate agent installations required."

How to Set Up Remote Support in Agent Workspace or Service Operations Workspace

ScreenMeet's documentation lists three prerequisites: a standard ServiceNow deployment, a ScreenMeet account and an admin to install the application. The Store listing adds ServiceNow Utah or later and a modern browser, with Chrome recommended. The current listing shows compatibility with the Australia, Zurich and Yokohama releases.

Setup then follows the order set out in ScreenMeet's ServiceNow documentation:

  1. Install the ScreenMeet application in the ServiceNow instance, choosing ScreenMeet rather than ScreenMeet for CSM or ScreenMeet for ITSM.
  2. Run the guided setup, which assigns user roles, configures the ScreenMeet service account and configures the UI for Classic and Workspace.
  3. Open Configure Visibility and select the tables that should show ScreenMeet.

Part of the guided setup also happens in the ScreenMeet console, where an administrator configures and validates the ServiceNow integration.

ScreenMeet provides a 30-day fully functional trial after installation in ServiceNow. ScreenMeet supports versions of its ServiceNow package released within the last two years, and its documentation recommends upgrading every four to six months.

Agents still need no installed console on their own machines to run sessions. The reasons behind that model are covered in our look at why IT teams are moving to browser-based remote support consoles.

Devices with no employee present need Beam, an optional paid add-on to ScreenMeet Support. The Beam client is installed on each device and bound to a Beam Group, which controls who can access that device. For how that model compares with legacy jump clients, see our guide to secure unattended access.

How a Remote Support Session Works in ServiceNow Agent Workspace, Step by Step

Every step below runs from the incident or case record, with no separate application for the agent to open.

Step 1: Open the Incident and Choose a Session Type

The agent opens the record, selects the ScreenMeet tab and picks a session type. ScreenMeet's documentation lists four session types: CoBrowse, Live, Remote Support and Replay. This walkthrough follows a Remote Support session from start to finish.

Step 2: Invite the Employee to Join the Remote Session

ScreenMeet's end-user documentation gives the employee three ways to join the session:

  • Enter the session PIN at myhelpscreen.com.
  • Click the generated myhelpscreen.com link the agent sends.
  • Launch a pre-installed MSI and enter the PIN.

After entering the PIN, the employee is prompted to download the ScreenMeet application, open it and click allow to start the session. Depending on the antivirus in use, the employee may need to approve the executable file. The application works at a per-session level, and the employee does not need to uninstall any program afterwards. A thin red border appears on the employee's screen, so the employee can see that the session has started.

ServiceNow's internal help desk pre-installed Remote Support on 18,000 employee devices. According to the ServiceNow case study, the team saves 6 minutes per session in connection time.

Step 3: Troubleshoot With Remote Control and In-Session Tools

Inside a Remote Support session, administrators can switch on individual features through ServiceNow roles. ScreenMeet's role documentation lists features such as remote control, chat, screenshot, reboot, safe reboot, privacy curtain, UAC and Windows tools.

Across all of its session types, ScreenMeet's Store listing names four real-time tools available from any ServiceNow workflow: voice and video chat, screen share, co-browse and remote desktop takeover.

The employee keeps a say on the other side, and can pause the session, start a file transfer or end the session at any time.

Agents can also use AI Assist in Remote Support sessions, a real-time chat that helps them troubleshoot. With Knowledge Base Search enabled, AI Assist can search the knowledge base and reference the record's short description, description and notes.

Step 4: Close the Session on the Incident Record

The session ends, and the session record stays linked to the incident or case in the record's ScreenMeet sessions table.

What the ServiceNow Incident Record Holds After a Remote Support Session

A closed session leaves a record that anyone with the right ServiceNow role can open and review.

The incident or case shows a ScreenMeet sessions table, which lists every session linked to that record with these details:

Field What it shows
Duration and duration connected How long the session ran and how long it was connected
Concurrent users The users who joined the session
Task or case The record the session relates to
Session PIN The PIN used for the session, where relevant
Recording link A link to the session recording
Session code The ScreenMeet code for the session

Each ScreenMeet Sessions record opens into four sections: Details, Device Information, Session Logs and Attachments. Details and Device Information show context such as the session PIN, the agent, the status and the connected device.

Session Logs record the actions taken during the session, such as an agent entering, remote control being approved, shortcuts being run and chat transcript activity. Recordings and transferred files appear under Attachments, on the session record or on the parent record, depending on configuration.

AI Summarization adds a written account of what happened during the session. AI Summarization summarizes the key events of a Remote Support session and posts the summary as work notes on the incident, with AI Plus enabled for the organization. Our guide to AI-powered remote support for ServiceNow covers the four phases AI should handle across a support session.

ScreenMeet's Store listing describes those structured notes as the data foundation that strengthens Now Assist and the knowledge base. That question gets a full test in does your remote support tool actually feed your ServiceNow KB.

The Store listing also states that session data, system info, recordings and transferred files are stored within ServiceNow, not in a separate system.

How ServiceNow Roles Control Remote Support Access in the Workspace

Access to remote support follows ServiceNow roles and groups, layered on a baseline set in the ScreenMeet console. Services authenticate through ServiceNow, and the Store listing states that every command requires an authenticated session to run.

ScreenMeet's role model uses three kinds of role inside the ServiceNow instance:

  • Product roles switch on a whole product, such as Remote Support, for a licensed user.
  • Feature roles switch on a single feature within that product, such as remote control or recording.
  • Agent choice roles let the agent decide whether to use a feature in a given session.

Administrators can assign these roles to ServiceNow groups, and group members inherit them. Settings in the ScreenMeet console set the baseline, so a role cannot switch on a feature the console has disabled. Feature-level control takes effect once the x_prois_sm.control_features_with_roles system property is set to true.

Three roles can review session logs: ScreenMeet Admin, ScreenMeet Agent and ScreenMeet Session Viewer. For how session-scoped access works as a security model, see our guide to just-in-time (JIT) access for remote IT support.

ScreenMeet supports SOC2, ISO27001 and GDPR compliance, with geo-fencing available for data sovereignty needs. The remote support product page also lists detailed consent tracking and comprehensive audit trails for security teams.

Frequently Asked Questions About Remote Support in ServiceNow Agent Workspace

1. Is ServiceNow Agent Workspace deprecated?

ServiceNow's Store listing for its Migration Utility for Service Operations Workspace states that ITSM Agent Workspace has been deprecated and is no longer supported. Administrators can use the free utility to move common configurations and customizations to Service Operations Workspace.

2. Can remote support run in Service Operations Workspace?

Remote support runs in Service Operations Workspace through ScreenMeet, which its Store listing names alongside Agent Workspace, CSM/FSM Configurable Workspace, HRSD and the Classic UI. ScreenMeet's interactive demo starts a Remote Support session from within ServiceNow ITSM in Service Operations Workspace.

3. Does the employee need to install software for a remote session?

The employee enters the session PIN at myhelpscreen.com, clicks a generated link or launches a pre-installed MSI, then runs the ScreenMeet application for that session. The application works at a per-session level, and the employee does not need to uninstall any program afterwards.

4. Where are remote session recordings stored in ServiceNow?

Recordings appear under Attachments on the ScreenMeet Sessions record or on the parent record, depending on configuration. ScreenMeet's Store listing states that recordings, session data and transferred files are stored within ServiceNow.

See a Remote Session Run Inside a ServiceNow Incident

Agent Workspace and Service Operations Workspace already bring the incident onto one screen for the agent. Remote support belongs on that same record, from the first click to the closed session and the notes it leaves behind. Take the interactive tour of a Remote Support session in Service Operations Workspace to see each step run inside ServiceNow.

Ready to Replace Your Legacy Solutions?
Start Your Journey Here

Try The Guided Tour

See It In Action: Experience our comprehensive in-browser demo showcasing all core remote support capabilities and platform integrations.

Product Overview

Watch A 4-Minute Product Overview: Quick overview covering key benefits, security features, and integration capabilities for busy IT leaders. 

Talk To A Specialist

Ready To Get Started? Speak with our platform experts about your specific ServiceNow, Salesforce, or Tanium integration requirements.

Book A Demo