Pylon Metric
Customer Support
Escalation Rate = Escalated Conversations / Total Conversations × 100
Escalation Rate measures the percentage of support conversations in Pylon that are escalated from first-line agents to senior specialists, managers, or engineering teams. High escalation rates indicate gaps in first-tier training, documentation, or tooling that prevent frontline resolution.
Full guide: definition, formula, and benchmarksPylonCustomer SupportEscalation Rate
Escalation Rate measures the percentage of support conversations in Pylon that are escalated from first-line agents to senior specialists, managers, or engineering teams. High escalation rates indicate gaps in first-tier training, documentation, or tooling that prevent frontline resolution.
How to calculate escalation rate
Why escalation rate matters for Pylon users
Every escalation adds delay and introduces handoff friction. When escalation rates are high, senior agents and engineers spend their time on issues that could have been resolved at the first tier, reducing their capacity for genuinely complex problems.
For Pylon teams, tracking escalation reasons reveals specific knowledge gaps. If a particular product area consistently escalates, creating a dedicated playbook or training module can reduce escalations and free senior capacity for strategic work.
Understand and act on escalation rate with KPI Tree
Track conversation escalation events in Pylon via your warehouse. Model escalation rate in KPI Tree and link it to resolution time, agent productivity, and account health in your support quality tree.
Assign RACI ownership to training leads and use escalation reason data to build targeted training programmes that address the most common first-tier knowledge gaps.
Get started with your Pylon data
MCPPull metrics from Pylon directly through the Model Context Protocol.
Connect your existing warehouse where Pylon data already lands.
Our professional services team can build you turn-key AI foundations in a matter of weeks. Data warehouse on Snowflake/BigQuery, ELT with Fivetran, all modelled in dbt with a semantic layer.
Related Pylon metrics
Agent Productivity Score
Customer SupportMetric Definition
Agent Productivity Score is a balanced composite metric that evaluates support agent effectiveness across multiple dimensions including conversations handled, resolution time, first-response speed, customer satisfaction, and escalation rate. It avoids over-indexing on volume by equally weighting quality indicators.
Conversation Handoff Analysis
Customer SupportMetric Definition
Conversation Handoff Analysis measures the frequency, reasons, and impact of conversation transfers between agents, teams, or channels within Pylon. It quantifies the additional resolution time and satisfaction impact caused by each handoff, identifying opportunities to reduce unnecessary transfers.
Average Resolution Time
Customer SupportMetric Definition
Resolution Time = Conversation Resolved Timestamp − Conversation Created Timestamp
Resolution Time measures the total elapsed time from when a customer opens a conversation across any Pylon channel to when it is marked as resolved. It encompasses first response time, investigation, back-and-forth exchanges, and any internal waiting periods. It is a primary indicator of support efficiency.
Account Health Score
Customer SupportMetric Definition
Account Health Score is a composite metric that evaluates the support health of each customer account by weighting conversation volume trends, sentiment patterns, resolution times, and escalation frequency. It provides an early warning system for accounts whose support experience is deteriorating and may be at risk of churn.
Explore escalation rate across integrations
All Pylon metrics
Account Health ScoreAgent Productivity ScoreAgent Specialisation AnalysisChannel Performance AnalysisConversation Handoff AnalysisConversation Sentiment AnalysisConversation Volume TrendsCross-Channel Journey AnalysisCustom Field UtilisationCustomer Contact FrequencyCustomer Effort ScoreCustomer Satisfaction ScoreFirst Response TimeIssue Category DistributionIssue Recurrence RateKnowledge Gap IdentificationMessage Response Time by PriorityPeak Hours AnalysisRepeat Contact RateAverage Resolution TimeSupport Cost per ContactTag Usage PatternsTeam Workload DistributionEmpower your team to understand and act on Pylon data
Map what drives your metrics, measure progress at any grain, prove what works statistically, and deliver personalised action plans to every team member.
