Data & BI · Python · statsmodels · Power BI

CloudDesk — Support Resolution Root Cause Analysis (Python & Power BI)

A root-cause analysis of 2,400 SaaS support tickets: where resolution time is actually spent, which factors are associated with long resolutions, and how that relates to customer satisfaction and renewal. Analysis in Python (pandas, SciPy, statsmodels) with a four-page Power BI management dashboard.

TypePortfolio analysis of a SaaS support scenario (CloudDesk)
ToolsPython · pandas · NumPy · SciPy · statsmodels · Jupyter · Power BI
Data2,400 support tickets (one row per ticket) + release-notes log
ModelRobust log-transformed regression, R² 0.709 (adjusted 0.707)
CloudDesk Power BI executive overview: 2,400 tickets, median resolution 7.80 hours, P90 18.10 hours, median investigation 6.15 hours, first response 1.53 hours, average CSAT 4.52
Executive Overview page of the Power BI dashboard (screenshot from the repository).

Problem

Support tickets were taking several hours or longer to resolve. Leadership’s working hypothesis was that documentation gaps were the main bottleneck. The project tested that hypothesis against alternatives: reassignment, team, ticket category, channel, priority, customer segment, FAQ status and release windows.

Data and method

  • Resolution broken into stages: creation, first response, investigation and resolution.
  • Profiling, cleaning and transformation in Jupyter notebooks (01_data_ingestion, 02_data_cleaning, 3_business_impact), producing an analytical dataset and a dashboard dataset.
  • Because resolution time is right-skewed, a robust log-transformed regression was used; Variance Inflation Factor checks found no serious multicollinearity. An interaction model added little, so the simpler model was kept.

Results

Resolution timeline across 2,400 tickets
MeasureValue
Median resolution7.80 hours
Mean resolution9.74 hours
P90 resolution18.10 hours
Median first response1.53 hours
Median investigation6.15 hours
Average CSAT4.52
Renewal rate97.38%
Factors associated with longer resolution (median hours)
FactorComparison
Documentation available5.89 with documentation vs 12.22 without
Reassignments6.42 (0) · 11.77 (1) · 21.68 (2)
TeamTier 1: 9.63 (1,176 tickets, 3 agents) vs Tier 2: 6.39 (1,224 tickets, 11 agents)
CategoryPerformance/Latency 22.02 · Webhook Failures 12.32 · Security/Compliance 11.24 (overall 7.80)
CloudDesk Power BI root cause analysis page showing documentation availability, reassignment, team and category effects on resolution time
Root Cause Analysis page of the dashboard.

Customer impact

Resolution time is negatively associated with CSAT (Pearson −0.419, Spearman −0.328, p < 0.001). Average CSAT falls from 4.73 in the fastest quarter of tickets to 4.20 in the slowest. Tickets linked to non-renewal had a median resolution of 27.55 hours versus 7.70 for renewed, but there are only 63 such tickets, so this is reported as an association, not a cause.

Recommendations

The findings were turned into an eight-item operational backlog with success metrics, covering a documentation audit and improvements, reassignment and routing, ownership and escalation rules, a team workload review, diagnostic workflows for Performance/Latency and Webhook Failures, and an investigation-time KPI.

Limits

  • All results are statistical associations, not causal estimates.
  • Channel, priority, segment, FAQ status and release-window status showed limited independent explanatory value in the multivariate model.
  • Renewal effects rest on 63 non-renewal tickets and should be retested at customer level.

What this project demonstrates

  • Python analytics: a reproducible notebook workflow from ingestion to business impact.
  • Statistics: robust regression on a skewed outcome, multicollinearity checks and correlation testing, with careful causal language.
  • Power BI: a four-page management dashboard built on the processed Python output.
  • Operational recommendations: findings converted into a prioritised backlog with measurable success metrics.

Written by Emmanuel Abolade, Data Analyst, Business Intelligence Developer and Full-Stack Software Developer based in Hull, UK. Every figure on this page comes from the linked public repository or live demo.