﻿<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Report Views on ~.UcClient.~ Unified Communications</title>
		<link>https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/</link>
		<description>Recent content in Report Views on ~.UcClient.~ Unified Communications</description>
		<generator>Hugo</generator>
		<language>en-gb</language>
		
		
		
		
			<atom:link href="https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Long Calls</title>
				<link>https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/longcalls/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/longcalls/</guid>
				<description>&lt;h1 id=&#34;long-calls&#34;&gt;&#xD;&#xA;  Long Calls&#xD;&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#long-calls&#34;&gt;#&lt;/a&gt;&#xD;&#xA;&lt;/h1&gt;&#xD;&#xA;&lt;p&gt;The Long Calls view identifies your longest interactions, ranked by duration. Call length is often a leading indicator of underlying issues — whether process bottlenecks, complex problems that require escalation, difficult customer situations, or inefficient handling.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-track-call-length&#34;&gt;&#xD;&#xA;  Why Track Call Length?&#xD;&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#why-track-call-length&#34;&gt;#&lt;/a&gt;&#xD;&#xA;&lt;/h2&gt;&#xD;&#xA;&lt;p&gt;&lt;strong&gt;Identifying process problems&lt;/strong&gt; — a sudden increase in call duration for a particular call type or queue often signals that something has changed — a system is slower, a process step has been added, or there is confusion about how to handle a scenario. Long calls cluster around specific issues, making them easier to spot than reviewing individual calls.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Lost Calls</title>
				<link>https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/lostcalls/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/lostcalls/</guid>
				<description>&lt;h1 id=&#34;lost-calls&#34;&gt;&#xD;&#xA;  Lost Calls&#xD;&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#lost-calls&#34;&gt;#&lt;/a&gt;&#xD;&#xA;&lt;/h1&gt;&#xD;&#xA;&lt;p&gt;The Lost Calls view identifies calls that were abandoned — customers who hung up before reaching a user. Every lost call represents a missed connection, and tracking them reveals whether customers are leaving due to wait times, routing confusion, system issues, or frustration.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-track-lost-calls&#34;&gt;&#xD;&#xA;  Why Track Lost Calls?&#xD;&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#why-track-lost-calls&#34;&gt;#&lt;/a&gt;&#xD;&#xA;&lt;/h2&gt;&#xD;&#xA;&lt;p&gt;&lt;strong&gt;Detecting routing and queue problems&lt;/strong&gt; — a sudden spike in abandoned calls in a particular queue often indicates sizing issues (too few users for call volume), routing misconfiguration, or system problems causing excessive hold times. Lost calls are an early warning signal.&lt;/p&gt;</description>
			</item>
			<item>
				<title>Repeat Calls</title>
				<link>https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/repeatcalls/</link>
				<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
				<guid>https://docs.na.xarios.cloud/desktop/en-gb/reports/reportviews/repeatcalls/</guid>
				<description>&lt;h1 id=&#34;repeat-calls&#34;&gt;&#xD;&#xA;  Repeat Calls&#xD;&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#repeat-calls&#34;&gt;#&lt;/a&gt;&#xD;&#xA;&lt;/h1&gt;&#xD;&#xA;&lt;p&gt;The Repeat Calls view identifies customers who contact you multiple times within a short period — a pattern that almost always signals an unresolved issue. When a customer calls back, it means your first attempt to help them did not succeed, representing both a customer satisfaction risk and an opportunity to improve.&lt;/p&gt;&#xA;&lt;h2 id=&#34;why-track-repeat-calls&#34;&gt;&#xD;&#xA;  Why Track Repeat Calls?&#xD;&#xA;  &lt;a class=&#34;anchor&#34; href=&#34;#why-track-repeat-calls&#34;&gt;#&lt;/a&gt;&#xD;&#xA;&lt;/h2&gt;&#xD;&#xA;&lt;p&gt;&lt;strong&gt;Measuring first-contact resolution&lt;/strong&gt; — repeat calls are the inverse of first-contact resolution (FCR). High repeat call volume indicates that your team is not resolving issues the first time, forcing customers to call back and frustrating them in the process. Tracking repeat calls helps you identify where resolution is breaking down.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
