Pylon Metric
Customer Support
Tag Usage Patterns examines how conversation tags are applied across Pylon, measuring tag frequency, consistency, coverage, and co-occurrence. Consistent tagging is essential for reliable topic-level reporting, routing automation, and trend analysis. Inconsistent tagging undermines every downstream metric that depends on categorisation.
PylonCustomer SupportTag Usage Patterns
Tag Usage Patterns examines how conversation tags are applied across Pylon, measuring tag frequency, consistency, coverage, and co-occurrence. Consistent tagging is essential for reliable topic-level reporting, routing automation, and trend analysis. Inconsistent tagging undermines every downstream metric that depends on categorisation.
Why tag usage patterns matters for Pylon users
Tags are the foundation of categorised analytics. If agents apply them inconsistently - or not at all - every report built on tag data is unreliable. This silent data quality issue can lead to misguided strategic decisions based on incomplete information.
For Pylon teams, tag patterns also reveal workflow issues. If a new tag category is rarely used, it may indicate poor training. If two tags frequently co-occur, they may need to be merged. Regular analysis keeps the taxonomy healthy and the data trustworthy.
Understand and act on tag usage patterns with KPI Tree
Extract tag data from Pylon conversations in your warehouse and analyse patterns in KPI Tree. Track coverage rate, consistency, and taxonomy health as metrics in your support operations tree.
Assign RACI ownership to the support analytics lead and conduct quarterly taxonomy reviews to retire low-use tags and introduce new categories based on emerging patterns.
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
Custom Field Utilisation
Customer SupportMetric Definition
Custom Field Utilisation = Conversations with Field Populated / Total Conversations × 100
Custom Field Utilisation measures the percentage of conversations where custom fields - such as product area, issue severity, or account tier - are populated by agents or automation. High utilisation ensures reliable data for routing, reporting, and analytics. Low utilisation undermines the value of custom fields entirely.
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.
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.
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 RateKnowledge Gap IdentificationMessage Response Time by PriorityPeak Hours AnalysisRepeat Contact RateAverage Resolution TimeSupport Cost per ContactTeam 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.
