Co-Managed IT
Define the recurring responsibilities an internal IT team keeps and the work Root supports.
Service scope
IT Helpdesk and Technical Support for Employees
Root provides technical support for employees dealing with accounts, devices and business applications. A useful helpdesk combines a clear request route, enough context to investigate and a defined escalation path when the issue reaches beyond the first engineer.
Make the support request easier to move forward
A locked account, an application error, or an incomplete new-hire setup can interrupt an entire day. Root provides human technical support for routine requests and complex escalations, connecting user issues to the wider managed environment when needed.
Employees should not need to identify the failing technical layer before asking for help. The support process can collect the application, device, error and business impact, then determine whether the issue belongs to endpoint support, identity, an application vendor or infrastructure operations. Keeping ownership visible is particularly useful when several organizations participate in the resolution.
What employee support can cover
Accounts and access
Password and sign-in issues, employee onboarding and offboarding, and access changes need a reliable approval path. The person requesting a permission change may not be the person authorized to approve it. Root’s support scope connects account work to the managed environment.
Devices and applications
Remote-first support helps investigate endpoint and application problems using the details the employee provides. Microsoft 365 and other business applications may also involve tenant settings or vendor responsibilities. Define the supported environment and where specialist application work begins.
Escalations and onsite needs
Some issues require infrastructure expertise, vendor involvement or onsite dispatch. Root’s scope includes onsite dispatch when needed, subject to the engagement. Agree on coverage and coordination instead of assuming that every ticket follows the same route or timetable.
Follow a request through the support process
Describe the interruption
Include who is affected, what they cannot do, the relevant application, the error text and when the issue started. Mention recent changes and whether others see the same behavior. Avoid sending passwords, recovery codes or unnecessary sensitive records.
Confirm impact and investigate
The engineer needs to distinguish one user’s issue from a shared service problem. The business impact helps establish priority; technical symptoms help establish the investigation. A clear contact method makes it easier to confirm findings and request an appropriate next step.
Escalate with context
If another team or vendor must act, transfer the findings, actions already taken and the remaining question. A useful handoff reduces repeated troubleshooting and tells the employee who currently owns the issue.
Validate and learn
Confirm that the employee can complete the affected task. Root’s scope includes satisfaction tracking on closed tickets. Repeated requests can also reveal a training, configuration or infrastructure problem that deserves a more durable fix.
Business-hours support and critical escalation are different
Root lists business-hours helpdesk coverage with 24/7 critical escalation. Agree on the systems, users, support channels, and response targets in your SLA. When submitting a request, include the error message, when it started, and any recent changes. Do not send passwords or recovery codes. Current clients can use the homepage support center for the existing ticket and remote-session request workflows.
The agreement should explain what qualifies as a critical incident, which contact route applies and what commitments cover that response. The public site’s support center offers email-based ticket and remote-session requests. A prospective customer should discuss service coverage before treating those routes as an established support agreement.
Treat onboarding as a coordinated access change
A new employee may need a device, identity, licenses, application permissions and a manager’s approval. Plan the request around a start date and a defined role rather than a loose list of accounts. Offboarding needs equally deliberate coordination so access removal, device handling and ownership of business information follow the approved process.
Managed IT supplies the wider inventory and operating model; cybersecurity helps define protection and response boundaries. For a system-wide interruption, monitoring and NOC can connect employee reports to infrastructure signals. These links are operational responsibilities to agree, not assumptions that every service is automatically bundled.
Information that makes a support handoff useful
A short, factual description usually helps more than a guessed diagnosis. Keep credentials and sensitive customer information out of the request.
- The exact business task that is blocked and the number of affected people.
- Device and application details, the relevant error message and the approximate start time.
- Changes already attempted and whether those steps changed the behavior.
- A contact method and an appropriate time to reproduce the issue together.
- The application owner or manager who can approve any required access change.
Work through the next service decision
Employee support and onboarding questions
How do I request help now?
Use the Client Support Center or email [email protected]. Include a contact method and a description of the business impact. The current site routes ticket and remote-session requests through email.
Is routine support available around the clock?
The published scope distinguishes business-hours helpdesk support from 24/7 critical escalation. Confirm the applicable coverage and escalation procedure in your agreement instead of assuming every request receives after-hours handling.
Can an internal IT team retain part of the support work?
Discuss the split between internal support, Root and application vendors. Define which requests go where, how shared records are maintained and when a handoff is complete. Clear boundaries help a shared arrangement avoid duplicate work and unresolved ownership.
What if the same issue keeps coming back?
Keep the related ticket history and describe the recurring conditions. Repetition can justify a configuration review, training improvement or infrastructure investigation. The next step should address the cause where it can be established, rather than relying indefinitely on the same workaround.
Give your team a clearer route to technical help
Describe your users, applications and the requests that currently stall. We can discuss support scope, approvals and how escalations should work alongside your existing vendors or internal team.