Remote IT Support for Municipalities: A Staff Session Checklist

Start with a clear request and a known contact

Imagine a township employee trying to open a meeting packet from the approved shared folder. The document will not open, and the support technician needs to see the error. A remote session can help the employee explain what is happening. The office also needs a clear way to confirm who is connecting, what they will see, and how the session ends.

For Michigan townships, villages, and cities, start through the municipality’s established support channel. Provide the affected computer or asset tag, application, observed error, and time the problem began. Explain which office task is blocked and what you have already tried. Keep the request number if one is issued, and agree on how the technician will contact you for the next step.

Verify the person through a channel you already know

A familiar display name or a message saying IT support does not establish the sender’s identity. Microsoft’s guidance on helpdesk impersonation recommends verifying unexpected support contact through a known channel before granting remote access. If a call or chat was not expected, contact your established helpdesk using details already held by the office, then ask it to confirm the request and technician.

Use the same process when a caller says the problem is urgent. A ticket number can help locate the work, but verification should follow the office’s agreed method. Give employees a primary and backup municipal contact for questions. They should be able to pause a connection request and obtain confirmation without having to judge whether a caller sounds technically knowledgeable.

Use the support tool the municipality has approved

Ask the verified technician which tool is needed and how to obtain it. Black Rock’s Remote Support page provides Windows and Mac agent downloads for people working with the support team. Use that established page when directed by your Black Rock technician and choose the download for your computer. Confirm the instructions before proceeding with installation or permission prompts.

A managed computer may already have its approved support software. Ask before installing another application. Microsoft notes that organizational policy can restrict installation of Quick Assist and directs affected users to their IT administrator. Follow your own organization’s approved process when a download or permission is blocked; report the prompt to IT so it can determine the appropriate next step.

Prepare what the technician will see

Save current work and close unrelated documents, browser tabs, and messages before sharing. Ask what screen or displays the support tool makes visible. Leave the relevant application and error ready to demonstrate. For the meeting-packet problem, identify an approved sample document if it can show the same fault without exposing unrelated resident or employee information.

Microsoft’s remote assistance guidance advises against sharing credentials to websites or applications. Do not read out or send passwords or account sign-in verification codes in a support chat. If authentication or an administrator prompt is needed, ask the technician to explain the approved procedure. Staff should understand the requested step and use the municipality’s established authentication process.

Understand viewing and control before granting access

As one platform example, Microsoft’s Windows Quick Assist documents separate steps for allowing screen sharing and allowing full control. Ask your verified technician to explain the permissions requested by the municipality’s actual support tool. Know which control lets you stop the interaction before accepting it. Keep the assistance tied to the reported issue and ask for clarification when an unfamiliar action is proposed.

Stay available to describe the problem and answer questions. Agree on any interruption before it happens, including a restart or a temporary loss of access to the application. Explain if the computer is serving residents at the counter so the technician and municipal contact can coordinate the work. If the interaction becomes suspicious, disconnect and contact your established IT team through the known reporting channel.

Check the task and confirm the session has ended

When the technician is ready, repeat the affected workflow using approved sample work. Confirm that the document opens from the intended shared location and that the employee can continue the task. Record any remaining issue, agreed follow-up, and request number. If another vendor or an onsite visit is needed, confirm who owns the next step and how staff will receive an update.

Then ask the technician to confirm that active screen sharing and control have ended. Quick Assist distinguishes Cancel control from Leave, which is used when help is finished. Have IT explain the equivalent ending procedure for your tool and any separately approved ongoing device management. Follow its instructions for installed agents; do not assume that closing a chat removes software or changes the municipality’s management arrangement.

Keep this checklist with the support contact

Useful IT support for municipalities gives employees a repeatable session process. At your next Michigan IT services review, confirm these steps with the helpdesk and a staff member who uses remote support.

• Start with the established support channel and describe the blocked task.
• Verify unexpected contact through the known helpdesk before connecting.
• Use the approved support tool and installation process.
• Prepare relevant screen content and keep credentials private.
• Understand requested access, interruptions, and how to disconnect.
• Verify the work, record follow-up, and confirm the session has ended.