This guide explains how to work with your EasyITGuys support team, what “Triage” means, and how requests move through the right teams. Our goal is a support experience that is secure, fast, and consistent.
What is Triage #
Triage is our required starting point for most inbound support requests. Triage answers calls, validates identity, captures the right details, and attempts a fast fix. This creates a predictable support experience and prevents issues from getting stuck.
Why Triage is required #
Speed #
Triage is built for quick response, fast routing, and getting you to the right help right away.
Security #
Identity verification protects you from modern impersonation risks such as phone spoofing and AI voice cloning.
Consistency #
A structured first step prevents missing details, rework, and confusion about who owns the next step.
First Call Resolution (FCR) #
Triage is the best place to start because it drives strong First Call Resolution (FCR).
Many issues can be solved immediately without escalation.
- Identity verification: typically 1–2 minutes.
- Ticket creation or update: clear notes so you do not repeat yourself.
- Attempt to resolve: first-line troubleshooting and resolution.
- Typical FCR: 50% or higher is common for a strong triage function.
- Typical triage call: around 15 minutes depending on complexity.
What Triage does on every call #
- Answer the phone and confirm the request type.
- Validate identity before proceeding.
- Create or update the ticket with the right details.
- Confirm impact and urgency so the request is prioritized correctly.
- Attempt first-line troubleshooting and resolution.
- Set expectations for next steps and updates.
- Escalate to the correct team when needed.
Support tiers and team roles #
We use tiers because different work requires different focus and experience. This keeps service consistent and reduces downtime.
Triage (Required Start) #
First contact, identity verification, ticket creation, quick troubleshooting, and routing.
If it can be solved quickly, Triage will solve it on the spot.
- Answer and verify
- Document clearly
- Resolve or route
SupportDesk Escalations (Tier 2 and Tier 3) #
Tier 2 and Tier 3 are both SupportDesk escalation teams.
They handle deeper troubleshooting, complex issues, and high-impact technical problems.
- Advanced troubleshooting
- Recurring issues and deeper diagnostics
- Server, network, identity, cloud, and multi-system issues
Operations Team (Advanced Support and Coordination) #
The Operations Team handles advanced support beyond the standard SupportDesk.
This includes requests that require special access, account-level decisions, cross-team coordination,
or work that is not a typical end-user reactive support ticket.
- Access and permissions: admin rights, vendor portals, account ownership, approvals.
- Coordination: multi-team work, scheduling, change planning, and complex handoffs.
- Account management: service changes, ownership questions, coordination with leadership.
- Billing support: invoice questions, renewals, coverage validation.
- Routing: connecting SupportDesk work to Projects, Cybersecurity, or Compliance when needed.
Specialized teams you may hear about #
Cybersecurity #
Threat handling, suspicious activity review, containment steps, and security-related changes that require strict verification.
Compliance #
Regulated requirements, documentation, audits, scanning, and evidence collection (such as CMMC, HIPAA, FINRA).
Projects #
Planned changes, migrations, new installs, upgrades, scheduling, and change management.
How tickets move through the process #
- Start with Triage: verify identity, capture details, attempt fast resolution.
- Escalate within the SupportDesk if needed: Tier 2 and Tier 3 handle deeper technical work.
- Move to Operations when required: access, coordination, account management, billing, or non-standard work.
- Bring in specialized teams: Projects, Cybersecurity, or Compliance as needed.
What good handoffs look like #
When we escalate, we aim to keep you from repeating yourself. The ticket should capture the details needed for the next team.
- Your name, organization, and best callback number
- Identity verification completed (for calls)
- Device, user, and location details when relevant
- Clear problem statement in plain language
- Impact and urgency
- What was attempted and what happened
- Screenshots, errors, timestamps if available
- Who it is being escalated to and why