Where DEX Breaks Down: The Live Support Gap

A service desk manager pulls up the DEX dashboard and sees exactly what she expects: a segment of remote employees trending down, flagged devices, documented friction, timestamps on every event. Her team has been working through those tickets all morning. The score has not moved.

The DEX gap is not in the data. It lies in what happens after the data surfaces the problem.

Most organisations hit this structural problem after deploying a DEX platform and realising that detection is not the same as resolution. The investment in visibility pays off and friction becomes visible. The investment in fixing it still depends entirely on what happens inside the support session.

Why DEX Visibility Does Not Fix the Problem

DEX Platforms Were Built for Visibility, Not Resolution

Digital employee experience platforms were designed to solve a visibility problem. Before they existed, IT teams operated reactively, waiting for employees to log tickets, with no systemic view of endpoint health, software performance, or experience degradation across the fleet.

Platforms like Nexthink changed that. They introduced continuous monitoring across the endpoint estate, scoring the employee experience in real time and identifying friction before it became a support request. More importantly, Nexthink Flow enabled automated remediation for known, repeating issues: a misconfigured proxy silently corrected, a stale certificate renewed without a ticket being raised, a memory-hungry background process terminated before the employee notices lag, a software deployment failure caught and rerun automatically.

For these cases, the loop closes without a human ever touching the incident. For the class of problems DEX automation was designed to handle, it delivers.

Where Automation Reaches Its Limit

Automated remediation has a boundary, and that boundary is reached every day in every service desk.

Novel issues, unclear root causes, and failed Nexthink Flow remediations all terminate in the same place: a human session opening inside ServiceNow. At that exact moment, DEX score control passes from the automated layer to the IT service desk.

That transition is the inflection point the DEX dashboard does not show. The platform continues measuring the employee's experience, recording how long the incident remains open, whether the issue recurs, and whether the resolution moved cleanly or dragged through callbacks and escalations, though it has no influence over what happens next. That is now the agent's job, and the support tools the agent uses determine whether the DEX score recovers or drops further.

Why Nexthink and ScreenMeet Are Sequential, Not Competing Layers

ScreenMeet and Nexthink are designed as complementary layers:

• Nexthink - detection, scoring, automated remediation for known issues
• ScreenMeet - live human support for issues that require a person

The ServiceNow incident record is where those two layers meet. Nexthink surfaces the problem and scores the experience, ScreenMeet handles the live resolution, and what comes out of that session determines whether the DEX investment delivers its intended outcome.

The DEX gap is not a product failure. It is an architectural one: most service desks are still running legacy remote support tools that sit outside ServiceNow, which means every live session operates in a parallel environment with no connection to the incident record and no mechanism to write resolution data back. Identifying friction and addressing it are not the same operation, and the tools used for the latter were never built to close that loop.

Three Live Session Moments That Drop the DEX Score

Every service desk manager has watched these play out this week. They are not edge cases. They are the default behaviour of a support stack that was not designed with DEX measurement in mind.

Moment 1: The Employee Gets a Download Prompt

What happens:

The agent opens a remote support tool and initiates a session. The employee, sitting on a managed corporate device where IT policy blocks third-party installations, receives a download prompt they cannot complete. The agent calls back, or emails, or raises a second ticket to escalate. Resolution time extends significantly, and every minute of that loop registers as unresolved friction in the DEX platform.

Why it matters for the DEX score:

The download prompt is not a UX inconvenience but a measurable delay in time-to-resolution that the DEX platform records in real time. On managed devices, which make up a substantial share of corporate endpoints in enterprise environments, IT policy routinely blocks client-based remote support tools, and the employee experience during that failure is not neutral. It is actively negative.

What the alternative looks like:

ScreenMeet delivers the remote support session entirely in the browser. There is no client to install, no download prompt, no IT policy conflict. The session begins the moment the employee clicks the link, on any device, managed or unmanaged, regardless of local admin rights. The time-to-connect drops from several minutes, or a complete failure, to seconds. That difference registers directly in the DEX score.

Moment 2: The Agent Leaves ServiceNow

What happens:

The agent opens a legacy remote support tool, TeamViewer, Bomgar, or LogMeIn. These exist as separate applications, outside ServiceNow. The agent launches the tool, leaving the incident record behind, and works in a parallel environment with no connection to the ServiceNow record. Device context from the incident record does not carry into the remote session. When the session ends, the agent returns to ServiceNow and types whatever they remember into the notes field, if they type anything at all. The resolution, if there was one, now lives only in the agent's memory.

Why it matters for the DEX score:

An incomplete incident record has two immediate consequences for DEX. First, Now Assist cannot generate a knowledge article from a sparse notes field, so the institutional knowledge that would prevent the next agent from repeating the same troubleshooting process never enters the system. Second, recurring incidents follow directly from that knowledge gap. The same employee raises a new ticket, the DEX platform records another instance of friction for that device and that user, and the score reflects each recurrence individually.

The cognitive load problem:

Asking agents to manually reconstruct what happened in a support session, after the session has ended, while already moving to the next ticket, consistently produces incomplete documentation. This is a workflow design problem, not an agent performance problem: the documentation step was placed at the wrong point in the process and made entirely manual.

What the alternative looks like:

ScreenMeet runs inside the ServiceNow incident record. The agent opens the session from the incident. They conduct the session from the incident. They close the session inside the incident. There is no application switch. The device context is present throughout. And when the session ends, the documentation is handled automatically — which brings us to the third moment.

Moment 3: The Ticket Closes With "Fixed It"

What happens:

The agent returns to ServiceNow after a session. The resolution notes field contains two words: "Fixed it." No steps documented, no resolution path recorded, no device state captured, no root cause noted. The ticket closes.

The cost of two words:

"Fixed it" is the most expensive phrase in the service desk vocabulary, not because it closes the ticket, but because of what it forecloses. The next agent who encounters the same issue starts from zero. Now Assist has no resolution path to work from, so no knowledge article gets generated. The knowledge base stays static. The incident recurs for the same employee or a different one on the same device configuration, and each recurrence registers as a new friction event in the DEX platform.

The compounding effect:

The DEX score does not reflect individual incidents in isolation. It reflects patterns. An employee whose device has the same issue resolved three times with no structural fix and no knowledge captured has a DEX profile that signals persistent friction. A recurring incident is a recurring DEX hit, and every recurring DEX hit was once a ticket that closed without a complete record.

What the alternative looks like:

When ScreenMeet's AI Session Summary runs at the end of a session, the agent does not need to type anything. The summary writes automatically to the ServiceNow incident record: steps taken during the session, tools used, device state at session start and end, the resolution path from symptom to fix, and relevant error codes and system data. That record is ready for Now Assist to act on the moment the ticket closes.

ServiceNow's Now Assist depends entirely on the incident record being complete, and an incident that closes with "Fixed it" gives it nothing to work with. The organisations that see the most value from their Now Assist investment are not the ones with more disciplined agents. They are the ones whose support architecture captures resolution data automatically, at the point where it exists, inside the session.

Legacy Stack vs. ScreenMeet: What Each Failure Mode Looks Like

‍

The DEX Score Is Set in the Support Session, Not the Dashboard

Most organisations invest significant time in the DEX dashboard, building reports, tracking trends, escalating low-scoring segments to the service desk. That analysis identifies where to focus. It does not change the score. The score changes when an employee connects in seconds rather than minutes, when an agent resolves the issue on the first call, when a resolution is documented completely enough that the same issue does not come back.

DEX platforms show where the experience breaks down. ScreenMeet determines whether it gets fixed and whether that fix becomes structured data that prevents the next occurrence. The DEX gap is not a measurement problem. It is a resolution problem, and specifically a documentation problem that compounds every time a ticket closes without a complete record.

Five Questions That Locate the DEX Gap in Your Environment

If the DEX score is flat despite the investment in detection tooling, these five questions locate the gap:

• Are agents leaving ServiceNow to launch a separate remote support tool?
• Are employees on managed devices receiving download prompts they cannot complete?
• Are incident records consistently incomplete at the time of closure?
• Is Now Assist generating knowledge base articles from closed incidents, or is the knowledge base largely static?
• Are the same issues recurring for the same employees or device types?

If more than two of those answers are yes, the gap is not in the dashboard. It is in the support session.

See how ScreenMeet closes the DEX gap inside ServiceNow

FAQs

1. What is the DEX gap?

The disconnect between what a DEX platform detects and what the service desk can actually resolve and document. Detection is not resolution, and most support stacks were never built to close that loop.

2. Why doesn't my existing remote support tool fix it?

Tools like TeamViewer, Bomgar, and LogMeIn were built for remote access, not ServiceNow integration. When an agent leaves ServiceNow to launch one, device context is lost, session data goes undocumented, and Now Assist has nothing structured to work with.

3. How does ScreenMeet improve DEX scores?

It eliminates the three moments where the score drops most: the failed download prompt, resolved by a browser-based connection with no install required; the context switch, resolved by keeping the agent inside ServiceNow throughout; and the empty closure note, resolved by AI Session Summary writing structured resolution data automatically at session end.

4. Does ScreenMeet replace Nexthink?

No. Nexthink handles detection and automated remediation for known issues. ScreenMeet handles the live human sessions that follow when automation reaches its limit. They are sequential layers in the same workflow, not competing products.

5. What does AI Session Summary write to the incident record?

Steps taken, tools used, device state, and the full resolution path, written automatically at session close with no agent input. That structured record is what Now Assist needs to generate a knowledge base article in one click.

6. How does a recurring incident affect the DEX score?

Every recurrence is a new friction event for the same employee. An undocumented root cause makes a systemic fix impossible, and the DEX score reflects each occurrence individually. One poorly documented closure can produce multiple DEX hits.