Skip to main content
DSE Support Library

What to expect during a DSE remote support session

Public support documentation available without signing in.

Support Library  /  Customer Support Center Guide / Scheduling, Projects, and Billing
Last updated 5 days ago

Summary: Know how a legitimate DSE remote session starts, what the technician may do, how your privacy is protected, and how to confirm the session has ended.

AudienceDSE customers and authorized contacts
Procedure4 guided sections
Checklist16 specific actions
ReviewedJuly 16, 2026
Visual walkthrough4 visual references for this procedure
Illustrated DSE remote and onsite scheduling workflow.
Illustrated example based on the production scheduling workflow; all records are fictional.
Numbered step path for What to expect during a DSE remote support session.
Mobile-readable step map matching the guided sections in this article.
Verification and closeout guide for What to expect during a DSE remote support session.
Mobile-readable verification, escalation, and handoff checkpoints for this procedure.
Annotated DSE walkthrough for What to expect during a DSE remote support session with three numbered red callouts.
Sanitized, production-faithful walkthrough. Follow the numbered red boxes and arrows to confirm context, complete the action, and verify the result.
01Before the session starts
  1. Confirm there is an open DSE ticket, scheduled support window, or approved maintenance activity for the affected computer.
  2. Verify the technician name and purpose through the ticket, an expected callback, or another known DSE contact path.
  3. Save your work and close unrelated email, messages, documents, password managers, financial systems, and private browser tabs.
  4. Tell the technician about any business-critical process, recording restriction, regulated data, or action that requires your approval before control begins.
02During attended support
  1. Remain available when practical and describe the failing workflow in your own words before the technician changes anything.
  2. The technician may view the screen, move the pointer, type, use approved keyboard shortcuts, transfer specifically requested clipboard text, or open diagnostic tools.
  3. Ask for an explanation before any disruptive action such as restarting an application, signing out, rebooting, changing a security setting, or interrupting service.
  4. Use the ticket for decisions and follow-up; do not place passwords, MFA codes, recovery keys, or sensitive business data in chat or clipboard transfer.
03Unattended and elevated work
  1. Unattended access is used only on enrolled devices and within DSE authorization, the customer agreement, and an approved support or maintenance purpose.
  2. Administrative prompts, the secure Windows desktop, or Task Manager may be used when required to diagnose or repair the approved issue.
  3. A technician should minimize viewing unrelated content and record the reason, work performed, result, and any follow-up in the DSE work record.
  4. If the requested action is outside the agreed scope, the technician must stop and obtain the correct approval before continuing.
04End and verify the session
  1. Ask the technician to summarize the work, tests, remaining risk, and next step before the session ends.
  2. When the session closes, remote pointer and keyboard control stop and temporary session data is cleared by the viewer and endpoint agent.
  3. Confirm the affected application or device now works, or document the exact remaining symptom while the context is fresh.
  4. If you believe control continues after the technician says the session ended, disconnect the computer from the network if safe and contact DSE immediately through a known channel.

Content owner: DSE Service Operations · Production review: July 16, 2026

Please Wait!

Please wait... it will take a second!