Pylon Metric
Customer Support
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.
PylonCustomer SupportCross-Channel Journey Analysis
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.
Why cross-channel journey analysis matters for Pylon users
Pylon's core value proposition is unifying support across channels, but unification does not automatically mean seamless experiences. Customers who switch channels often do so because the current channel is failing them - the issue is too complex for chat or the response time on email is too slow.
Understanding cross-channel journeys reveals where channel transitions add value (escalating a complex issue to a call) versus where they indicate failure (a customer giving up on chat and trying email instead). This distinction guides channel strategy and routing investment.
Understand and act on cross-channel journey analysis with KPI Tree
Track customer journeys across channels in Pylon via your warehouse and model channel-transition patterns in KPI Tree. Link journey complexity to resolution time and customer satisfaction in your metric tree.
Assign RACI ownership to the support experience lead and use journey data to identify the most common failure-driven transitions for process improvement.
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
Channel Performance Analysis
Customer SupportMetric Definition
Channel Performance Analysis compares key support metrics - response time, resolution time, CSAT, and volume - across the communication channels managed by Pylon, including Slack, email, in-app chat, and social media. It reveals which channels deliver the best customer experience and where investment should be directed.
Conversation Handoff Analysis
Customer SupportMetric Definition
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.
Customer Effort Score
Customer SupportMetric Definition
CES = Sum of Effort Ratings / Total Responses
Customer Effort Score (CES) measures how much effort a customer must expend to get their issue resolved through Pylon's support channels. It is captured via post-conversation surveys and strongly predicts customer loyalty - lower effort correlates with higher retention.
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.
All Pylon metrics
Account Health ScoreAgent Productivity ScoreAgent Specialisation AnalysisChannel Performance AnalysisConversation Handoff AnalysisConversation Sentiment AnalysisConversation Volume TrendsCustom 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.
