Pylon Metric
Customer Support
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.
Issue Category Distribution
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.
Why issue category distribution matters for Pylon users
Not all support volume is equally addressable. Some categories can be automated, others need product fixes, and some require skilled human agents. Without understanding the distribution, improvement efforts are unfocused and their impact is unpredictable.
For Pylon teams, category distribution reveals the biggest opportunities for volume reduction. If 30% of conversations are about a single confusing feature, fixing that feature will reduce volume more effectively than hiring additional agents.
Understand and act on issue category distribution with KPI Tree
Extract conversation categories from Pylon into your warehouse and model distribution in KPI Tree. Link high-volume categories to resolution time and satisfaction to identify the most impactful improvement opportunities.
Assign RACI ownership to the product-support liaison and review distribution monthly, feeding insights into the product team's prioritisation process.
Get started with your Pylon data
Pull 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
Knowledge Gap Identification
Customer SupportMetric Definition
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.
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.
Conversation Volume Trends
Customer SupportMetric Definition
Conversation Volume = Count of New Conversations in Period
Conversation Volume Trends tracks the number of new support conversations initiated across all Pylon channels over time. It reveals patterns, seasonal variations, and anomalies that inform staffing decisions and operational planning. Sudden spikes often correlate with product releases, incidents, or marketing campaigns.
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
Empower 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.