An employee gets a phone call from someone claiming to be “IT.” The caller knows the employee’s name, says a computer needs an urgent update, and asks for a remote-support code. Should the employee continue?
Remote access is useful when a trusted technician needs to diagnose a problem without traveling to the office. The same capability becomes risky when an employee cannot verify who is on the other side. For a Rio Grande Valley business, the answer should not depend on whether the caller sounds confident. It should depend on a written support process.
Trust the process before the tool
Microsoft’s Quick Assist guidance for administrators, updated September 30, 2025 and checked September 18, 2026, says users should allow a helper to connect only when they initiated the interaction by contacting Microsoft Support or their own IT support staff directly.
That principle applies beyond one product. Employees should know the approved support phone number, email address, ticket portal, or internal contact. If a technician contacts an employee unexpectedly, the employee should stop and verify the request through that known channel. Caller ID, a familiar logo, or knowledge of the employee’s name is not enough by itself.
Create a simple rule: no remote session begins until there is an identifiable request, an expected technician, and a way to call back through the approved support path.
Explain what the employee is approving
Remote-support tools can provide different levels of access. Microsoft’s current Quick Assist user instructions distinguish between sharing the screen and granting full control. The user enters a time-limited code, approves screen sharing, and receives a separate prompt if the helper requests control.
Train employees to slow down at each prompt. Before selecting Allow, they should confirm the technician’s name, the ticket or issue being addressed, and whether view-only access is enough. If control is requested, the technician should explain why. Employees should never read out passwords, MFA codes, payment information, or other credentials during a remote session.
An urgent tone should not override the process. Microsoft warns that anyone controlling a device may be able to take actions on it or install applications. If the technician’s identity or request changes unexpectedly, the employee should disconnect and contact the approved support channel.
Keep sensitive work out of view
Before screen sharing begins, close customer records, payroll documents, banking pages, personal email, and unrelated business applications. Pause the session before entering a password or reviewing information the technician does not need.
Microsoft’s tech-support scam guidance says Microsoft does not make unsolicited calls or send unsolicited messages offering to fix a computer. It also warns that scammers may use legitimate remote-access applications after creating a false sense of urgency. The lesson for a business is broader: the software can be genuine while the person asking to use it is not.
Document and close the session
When the work is complete, the employee should end the session rather than simply minimizing the window. The support record should note the requester, technician, device, issue, start and end time, work performed, and any follow-up needed. If software was installed or security settings changed, record that too.
For recurring support, ask whether the organization needs a managed tool with named technicians, access controls, session records, and a defined approval policy. Product and licensing decisions should follow the business’s actual environment and risk requirements.
Remote-support verification checklist
- Publish one approved way for employees to request IT help.
- Require a ticket, request number, or recognizable internal contact before connecting.
- Verify unexpected technicians through a known phone number or support portal.
- Explain whether the session is view-only or requires control.
- Close unrelated sensitive information before sharing the screen.
- Never share passwords, MFA codes, or payment details in the session.
- End the connection when work is complete.
- Record what was accessed, changed, installed, and still needs follow-up.
- Report suspicious contact to management and the authorized IT provider.
Give employees a support process they can follow
Remote support works best when employees know exactly how help begins, what they may approve, and how a session ends. Zilla IT Consulting provides managed business IT and remote support for Pharr, McAllen, Edinburg, and Rio Grande Valley businesses. We can help establish a practical support workflow around the computers and applications your team uses.
Veteran owned and operated. Learn more at zillaitconsulting.com.
Call or text us today: 956-420-0055.