Approved session
Begin remote access only after communication with the SysFirms support team.

Start a secure remote support session after speaking with the SysFirms team.
Remote access should only begin after the support request and technician are confirmed. Never share a remote session code with an unknown caller or through an unverified message.
Remote support provides an approved, supervised route for diagnosing computer, application, email, account and configuration issues without requesting passwords through public forms or chat.
Scope is confirmed after the systems, dependencies, business impact and immediate priorities are understood.
Begin remote access only after communication with the SysFirms support team.
The customer can observe the session and end access when required.
Use remote access to inspect configuration and reproduce the reported issue.
Project-specific and account-specific requests should be opened through the client portal.
Sensitive credentials should not be pasted into public forms or chat.
Remote access ends when the approved support work is complete.
The exact sequence changes with urgency and scope, but the working principles remain consistent: understand the impact, prioritise correctly, implement safely and document the result.
Explain the problem and confirm the technician.
Use the approved remote support application or link supplied by SysFirms.
Share the temporary session code only with the confirmed technician.
End the session and retain the support reference.
These answers explain the usual approach. The final scope is always based on the actual environment and business requirement.
The approved tool or session link will be provided by the SysFirms support team for the specific request.
Yes. Use the Client Login link to access the SysFirms portal and submit account-specific support requests.
Not unless it is explicitly required, approved and documented for an ongoing support arrangement.