<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Agent Occupancy and Churn</title>
	<atom:link href="http://chriscrosby.net/blog/2009/04/01/agent-occupancy-and-churn/feed/" rel="self" type="application/rss+xml" />
	<link>http://chriscrosby.net/blog/2009/04/01/agent-occupancy-and-churn/</link>
	<description>Be the Change</description>
	<lastBuildDate>Tue, 31 Aug 2010 15:02:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Honest Analyst</title>
		<link>http://chriscrosby.net/blog/2009/04/01/agent-occupancy-and-churn/comment-page-1/#comment-823</link>
		<dc:creator>Honest Analyst</dc:creator>
		<pubDate>Wed, 06 May 2009 01:51:18 +0000</pubDate>
		<guid isPermaLink="false">http://chriscrosby.net/blog/2009/04/01/extrapolating-agent-occupancy-part-1/#comment-823</guid>
		<description>I have always looked at Occupancy as an agent metric. Even if it was summed up by the skill group it is still tied to the agents answering those calls. It is the agent &quot;sweat factor&quot; and there are coeralations between pushing agents too hard and shrink/attrition/customer satisfaction.

Also I am not fan of benchmarking stats. A lot of factors dictate what an appropriate occupancy is.</description>
		<content:encoded><![CDATA[<p>I have always looked at Occupancy as an agent metric. Even if it was summed up by the skill group it is still tied to the agents answering those calls. It is the agent &#8220;sweat factor&#8221; and there are coeralations between pushing agents too hard and shrink/attrition/customer satisfaction.</p>
<p>Also I am not fan of benchmarking stats. A lot of factors dictate what an appropriate occupancy is.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
