Pylon Metric
Customer Support
Knowledge Gap Identification surfaces topics where support agents consistently struggle - evidenced by high escalation rates, long resolution times, or low satisfaction scores for specific issue categories. It pinpoints where documentation, training, or tooling is insufficient to enable first-tier resolution.
PylonCustomer SupportKnowledge Gap Identification
Knowledge Gap Identification surfaces topics where support agents consistently struggle - evidenced by high escalation rates, long resolution times, or low satisfaction scores for specific issue categories. It pinpoints where documentation, training, or tooling is insufficient to enable first-tier resolution.
Why knowledge gap identification matters for Pylon users
Knowledge gaps are invisible until they are measured. Agents compensate by asking colleagues, searching ad hoc, or escalating - all of which add time and reduce quality. Systematic gap identification transforms reactive problem-solving into proactive capability building.
For Pylon teams, knowledge gaps directly impact the multi-channel support experience. An agent who lacks knowledge about a topic will struggle equally whether the conversation is on Slack, email, or in-app, making the gap a systemic rather than channel-specific issue.
Understand and act on knowledge gap identification with KPI Tree
Cross-reference issue categories with resolution time, escalation rate, and CSAT from Pylon in your warehouse. Model knowledge gap scores in KPI Tree and link them to training investment and agent specialisation.
Assign RACI ownership to the training lead and prioritise gap closure based on the volume and impact of affected conversations.
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
Issue Category Distribution
Customer SupportMetric Definition
Issue Category Distribution breaks down support conversations by topic or category - billing, technical, onboarding, feature requests - to reveal which areas generate the most volume. It informs product improvement priorities, training focus areas, and automation investment decisions.
Escalation Rate
Customer SupportMetric Definition
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.
Agent Specialisation Analysis
Customer SupportMetric Definition
Agent Specialisation Analysis examines how individual agents perform across different issue categories, channels, and customer segments. It identifies natural specialisations - agents who consistently resolve billing issues faster, or who achieve higher CSAT on technical queries - enabling smarter routing decisions.
Issue Recurrence Rate
Customer SupportMetric Definition
Recurrence Rate = Recurring Issue Conversations / Total Conversations × 100
Issue Recurrence Rate measures how frequently the same issue categories reappear across different customers or accounts over time. Unlike repeat contact rate which measures per-customer repeats, recurrence rate identifies systemic problems affecting multiple customers that warrant permanent product or process fixes.
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 ScoreEscalation RateFirst Response TimeIssue Category DistributionIssue Recurrence RateMessage 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.
