<?xml version="1.0" encoding="UTF-8"?>        <rss version="2.0"
             xmlns:atom="http://www.w3.org/2005/Atom"
             xmlns:dc="http://purl.org/dc/elements/1.1/"
             xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
             xmlns:admin="http://webns.net/mvcb/"
             xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
             xmlns:content="http://purl.org/rss/1.0/modules/content/">
        <channel>
            <title>
									Using Call History to improve agent performance - How To				            </title>
            <link>https://community.callin.io/community/how-to/using-call-history-to-improve-agent-performance/</link>
            <description>Callin.io Community Discussion Board</description>
            <language>en-US</language>
            <lastBuildDate>Tue, 18 Aug 2026 17:24:27 +0000</lastBuildDate>
            <generator>wpForo</generator>
            <ttl>60</ttl>
							                    <item>
                        <title>RE: Using Call History to improve agent performance</title>
                        <link>https://community.callin.io/community/how-to/using-call-history-to-improve-agent-performance/#post-8121</link>
                        <pubDate>Mon, 08 Sep 2025 07:43:20 +0000</pubDate>
                        <description><![CDATA[I had the same question when I launched my first agent. At first, I just looked at whether calls connected or not, but that doesn’t really tell you if the agent is performing well. Once I st...]]></description>
                        <content:encoded><![CDATA[<p data-start="807" data-end="1101">I had the same question when I launched my first agent. At first, I just looked at whether calls connected or not, but that doesn’t really tell you if the agent is <em data-start="994" data-end="1011">performing well</em>. Once I started using Call History properly, I realized it’s basically my control room.</p>
<p data-start="1103" data-end="1130">Here’s how I approach it:</p>
<ul data-start="1132" data-end="2334">
<li data-start="1132" data-end="1399">
<p data-start="1134" data-end="1399"><strong data-start="1134" data-end="1160">I always filter first.</strong> Raw data can be messy, so I use filters like “Completed + Human = No” if I want to see how it handles voicemails, or “Completed + Appointment = Yes” when I want to check booking flows. That way I’m only looking at the calls that matter.</p>
</li>
<li data-start="1401" data-end="1653">
<p data-start="1403" data-end="1653"><strong data-start="1403" data-end="1428">Transcripts are gold.</strong> Reading a couple of transcripts per day shows me if the agent is following the prompt. For example, I once saw it skipping over user responses too quickly—easy fix by adding more <strong data-start="1608" data-end="1636"></strong> in the prompt.</p>
</li>
<li data-start="1655" data-end="1861">
<p data-start="1657" data-end="1861"><strong data-start="1657" data-end="1691">Recordings tell another story.</strong> Transcripts don’t show tone or pacing. When I noticed the greeting sounded clipped, I just increased the welcome delay from 800 to 1200 ms and the problem disappeared.</p>
</li>
<li data-start="1863" data-end="2115">
<p data-start="1865" data-end="2115"><strong data-start="1865" data-end="1903">Extracted data = real performance.</strong> If I expect emails, names, or appointment dates and the fields are blank, I know the prompt isn’t guiding the AI enough. Adding phrases like <em data-start="2045" data-end="2078">“let me spell that back to you”</em> made the capture rate much better.</p>
</li>
<li data-start="2117" data-end="2334">
<p data-start="2119" data-end="2334"><strong data-start="2119" data-end="2153">Exports help with big picture.</strong> Once a week, I export the CSV and look at average call duration and completion rate. Short calls often mean hang-ups or poor prompts; long calls show me where the agent is stuck.</p>
</li>
</ul>
<p data-start="2336" data-end="2563">Honestly, before I started digging into Call History, I thought my agent was doing “fine.” After two weeks of reviewing transcripts and exports, performance clearly improved: better appointment rates and fewer confused users.</p>
<p data-start="2565" data-end="2753">So if you want to know how your agent is really doing, don’t just look at whether it answers calls—spend time in Call History. It’s the best tool to turn a decent agent into a great one.</p>]]></content:encoded>
						                            <category domain="https://community.callin.io/community/how-to/">How To</category>                        <dc:creator>Ronald27</dc:creator>
                        <guid isPermaLink="true">https://community.callin.io/community/how-to/using-call-history-to-improve-agent-performance/#post-8121</guid>
                    </item>
				                    <item>
                        <title>Using Call History to improve agent performance</title>
                        <link>https://community.callin.io/community/how-to/using-call-history-to-improve-agent-performance/#post-8120</link>
                        <pubDate>Mon, 08 Sep 2025 07:38:23 +0000</pubDate>
                        <description><![CDATA[My AI agent is running, but I don’t know how to measure if it’s actually doing a good job. I see the Call History tab in Callin.io—how do you use it to track performance and make improvement...]]></description>
                        <content:encoded><![CDATA[<p>My AI agent is running, but I don’t know how to measure if it’s actually doing a good job. I see the Call History tab in Callin.io—how do you use it to track performance and make improvements?</p>]]></content:encoded>
						                            <category domain="https://community.callin.io/community/how-to/">How To</category>                        <dc:creator>Rober1985</dc:creator>
                        <guid isPermaLink="true">https://community.callin.io/community/how-to/using-call-history-to-improve-agent-performance/#post-8120</guid>
                    </item>
							        </channel>
        </rss>
		