Pylon Metric
Customer Support
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.
PylonCustomer SupportIssue Recurrence Rate
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.
How to calculate issue recurrence rate
Why issue recurrence rate matters for Pylon users
A recurring issue is a symptom of a product or process failure that support is patching with workarounds rather than fixing at the root. Every recurrence consumes agent time, frustrates customers, and compounds the cost of not fixing the underlying problem.
For Pylon teams, recurrence data provides compelling evidence for product improvement requests. When support can quantify "this issue has cost us 200 hours of agent time over the past quarter", product teams are far more likely to prioritise a fix.
Understand and act on issue recurrence rate with KPI Tree
Aggregate issue category data from Pylon over time in your warehouse and compute recurrence rates in KPI Tree. Link recurrence to support cost per contact and customer satisfaction in your metric tree.
Assign RACI ownership to the product-support liaison and use recurrence data to build evidence-based product improvement proposals.
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.
Repeat Contact Rate
Customer SupportMetric Definition
Repeat Contact Rate = Customers with Repeat Contacts / Total Customers Contacting Support × 100
Repeat Contact Rate measures the percentage of customers who reach out about the same or a closely related issue within a defined window after their initial conversation was resolved. It reveals incomplete resolutions, temporary workarounds, and systemic product issues that generate recurring support demand.
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.
Support Cost per Contact
Customer SupportMetric Definition
Cost per Contact = Total Support Costs / Total Conversations Handled
Support Cost per Contact calculates the fully loaded cost of handling a single support interaction across all Pylon channels, including agent compensation, tooling costs, management overhead, and infrastructure. It provides the economic foundation for automation ROI calculations and channel strategy decisions.
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 DistributionKnowledge 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.
