The Center of CX
Subscribe
Education: IT Help Desk & Learning Technology

IT Help Desk & Learning Technology CX Stack Framework

University IT help desks support students, faculty, and staff across a technology landscape that includes LMS platforms, campus WiFi, email, lab computers, classroom AV, research computing, and personal device support. The CX challenge is seasonal intensity: the first week of classes, midterms, and finals create surge volume that dwarfs normal operations.

Map your current capabilities across all 7 layers: 35 checkpoints. Mark what you have, what you need and what is planned. Your answers stay in this browser tab.

Figures for this segment

No public benchmark exists for these figures in this segment. Measure your own with the tool named beside each.

IT Help Desk & Learning Technology: the 7-layer CX stack

For each capability, mark whether you have it, need it or have it planned.

0 of 35 marked

Layer 7: Analytics & Governance

0 of 5 in place

Measure and govern. Vendors in this layer include ServiceNow, NICE, Qualtrics.

  • Ticket volume trending by system, building, and time of semester
  • LMS uptime and performance correlated with help desk volume
  • Faculty vs student vs staff satisfaction by service category
  • Knowledge base effectiveness: which articles deflect tickets
  • SLA compliance by priority level and service category

Key risk: LMS performance degradation invisible until a whole class cannot submit assignments

Layer 6: Routing & Orchestration

0 of 5 in place

Route the work. Vendors in this layer include ServiceNow, NICE CXone, Cisco.

  • Tier 1/2/3 routing by issue complexity and system affected
  • LMS-specific routing to learning technology specialists
  • Faculty priority routing during class preparation and exam periods
  • Research computing routing to HPC and data services specialists
  • Classroom technology emergency routing for active class disruptions

Key risk: Faculty with a classroom projector failure during a lecture waiting in the general queue

Layer 5: Conversation Management

0 of 5 in place

Hold the conversation. Vendors in this layer include ServiceNow, Confluence, custom portals.

  • Self-service password reset and MFA enrollment
  • LMS help resources integrated into the LMS interface itself
  • Proactive system status notifications during outages and maintenance
  • Device setup guides for campus WiFi, email, and VPN
  • Knowledge base with searchable troubleshooting articles

Key risk: System outage during registration or exams without proactive communication

Layer 4: Reasoning & Planning

0 of 5 in place

Decide the next step. Vendors in this layer include ServiceNow Virtual Agent, Ada, custom bots.

  • Password reset and account unlock bots with identity verification
  • WiFi and network troubleshooting bots with device-specific instructions
  • LMS FAQ bots (submission, grading, discussion, video uploads)
  • Software access and installation guide bots
  • System status bots with real-time outage information

Key risk: Bot resolving a password reset without proper identity verification

Layer 3: Policy & Guardrails

0 of 5 in place

Set the rules. Vendors in this layer include NIST frameworks, institutional policy.

  • FERPA compliance for student data in IT systems
  • HIPAA compliance for health center IT systems
  • CJIS compliance for campus police systems
  • PCI DSS compliance for payment processing systems
  • Data classification and handling policies for research data

Key risk: Help desk agent accessing student records in a system they shouldn't have access to

Layer 2: Workflow Execution

0 of 5 in place

Do the work. Vendors in this layer include ServiceNow, Jira Service Management, Freshservice.

  • Incident management workflow: detect, triage, assign, resolve, close
  • Service request workflow: software access, account creation, equipment loan
  • Change management workflow for system updates and maintenance windows
  • Major incident workflow for campus-wide outages and security events
  • Onboarding workflow for new student, faculty, and staff account provisioning

Key risk: Major LMS outage during finals with no incident command workflow

Layer 1: Data Access

0 of 5 in place

Know the customer. Vendors in this layer include ServiceNow, Canvas/Blackboard, Cisco (network), Active Directory.

  • ITSM: tickets, knowledge base, asset inventory, and SLA tracking
  • Identity management: Active Directory, SSO, MFA enrollment
  • LMS: Canvas, Blackboard, Moodle user accounts and course data
  • Network management: WiFi performance, device registration, bandwidth
  • Asset management: lab computers, classroom technology, and loaner equipment

Key risk: Agent unable to see which systems the student is having trouble with

Mark at least 18 capabilities to see your profile (0 of 35 so far).

Sources and assumptions

Every figure on this page is a published figure checked on the publisher's own page, a labelled planning assumption you can test with your own numbers, or a worked example.

No public benchmark

  • Average handle time, university IT help desks. No regulator or trade body publishes handle time for this service area. Measure yours in AHT Decomposition.
  • First contact resolution, university IT help desks. No regulator or trade body publishes first contact resolution for this service area. Measure yours in FCR Leakage Diagnostic.
  • Customer satisfaction, university IT help desks. No public CSAT percentage exists for this service area.
  • Self-service containment, university IT help desks. No regulator or trade body publishes self-service containment for this service area. Measure yours in AI Deflection Reality Check.