Pylon Metric
Customer Support
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.
PylonCustomer SupportConversation Handoff Analysis
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.
Why conversation handoff analysis matters for Pylon users
Every handoff is a moment of friction for the customer - they must re-explain their issue, wait for the new agent to get up to speed, and trust a stranger with their problem all over again. Minimising handoffs is one of the most impactful ways to improve the support experience.
For Pylon teams managing multi-channel support, handoff analysis reveals whether routing rules are effective, whether agents have the skills to resolve issues without escalation, and where cross-channel transitions create the most friction.
Understand and act on conversation handoff analysis with KPI Tree
Track conversation assignment changes and channel transitions in Pylon via your warehouse. Model handoff frequency and impact in KPI Tree and link it to resolution time and customer satisfaction.
Assign RACI ownership to the support operations lead and use handoff data to refine routing rules, improve agent training, and reduce unnecessary transfers.
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
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.
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.
Cross-Channel Journey Analysis
Customer SupportMetric Definition
Cross-Channel Journey Analysis maps the paths customers take across support channels - starting in Slack, moving to email, and ending in a video call, for example. It measures the frequency of channel-switching, the reasons behind it, and the impact on resolution time and satisfaction.
Customer Satisfaction Score
Customer SupportMetric Definition
CSAT = Positive Ratings / Total Ratings × 100
Customer Satisfaction Score (CSAT) measures the percentage of customers who rate their support experience positively after a Pylon conversation. It is the most widely used indicator of support quality and directly reflects whether agents are meeting customer expectations across all channels.
All Pylon metrics
Account Health ScoreAgent Productivity ScoreAgent Specialisation AnalysisChannel Performance 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 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.
