<?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: Skill level based routing.</title>
	<atom:link href="http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/</link>
	<description>The blog about customer service and the customer service experience.</description>
	<pubDate>Thu, 08 Jan 2009 12:51:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Service Untitled &#187; Dell Customer Service Ideas - customer service and customer service experience blog</title>
		<link>http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/comment-page-1/#comment-43415</link>
		<dc:creator>Service Untitled &#187; Dell Customer Service Ideas - customer service and customer service experience blog</dc:creator>
		<pubDate>Fri, 18 May 2007 18:36:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/#comment-43415</guid>
		<description>[...] &#8220;Geek to Grandma&#8221; support aka skill-level based routing (which we talked about here). [...]</description>
		<content:encoded><![CDATA[<p>[...] &#8220;Geek to Grandma&#8221; support aka skill-level based routing (which we talked about here). [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: IVR Blog &#187; Skills-Based Routing vs. Skill-Level-Based Routing&#8230; see the difference?</title>
		<link>http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/comment-page-1/#comment-36599</link>
		<dc:creator>IVR Blog &#187; Skills-Based Routing vs. Skill-Level-Based Routing&#8230; see the difference?</dc:creator>
		<pubDate>Fri, 11 May 2007 12:34:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/#comment-36599</guid>
		<description>[...] A nice blog I&#8217;ve recently come accross that I recommend reading is the Service Untitled customer service blog.  One topic they&#8217;ve spoken about recently is the concept of Skill-level-based routing and given a pros/cons list on the idea.  This topic came up again in an interview they have with Dell&#8217;s VP of support, and it&#8217;s an interesting topic.  [...]</description>
		<content:encoded><![CDATA[<p>[...] A nice blog I&#8217;ve recently come accross that I recommend reading is the Service Untitled customer service blog.  One topic they&#8217;ve spoken about recently is the concept of Skill-level-based routing and given a pros/cons list on the idea.  This topic came up again in an interview they have with Dell&#8217;s VP of support, and it&#8217;s an interesting topic.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Service Untitled</title>
		<link>http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/comment-page-1/#comment-35778</link>
		<dc:creator>Service Untitled</dc:creator>
		<pubDate>Thu, 10 May 2007 13:32:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/#comment-35778</guid>
		<description>Thanks for your comment, Dave! 

I agree that saving the information would be quite valuable. Maybe ask for an update every year or so (because I'm sure some skill levels change). Reps could also update it if they feel the customer was more or less experienced than the automatic system though.</description>
		<content:encoded><![CDATA[<p>Thanks for your comment, Dave! </p>
<p>I agree that saving the information would be quite valuable. Maybe ask for an update every year or so (because I&#8217;m sure some skill levels change). Reps could also update it if they feel the customer was more or less experienced than the automatic system though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/comment-page-1/#comment-35758</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Thu, 10 May 2007 12:34:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/skill-level-based-routing/2007/05/09/#comment-35758</guid>
		<description>Great post!  Rating yourself on skill level for routing to the appropriate agent is definitely an interesting idea, and one that I could see employed in a number of companies.  I would caution making the IVR system too long / long-winded with a lot of questions or definitions of the skill levels, but these could work if kept brief.  Consumers are notoriously impatient with lots of automated talking and choices. 

I think this could be taken a step further to help repeat callers though.  By asking the caller questions to determine their skill level the first time, then saving this skill level into a CRM system through a database integration with the IVR, the next time the caller calls he/she can be recognized with the saved skill level value and not put back through the questioning process.  

I work at a company called &lt;a href="http://www.angel.com/" title="Angel.com IVR Solutions" rel="nofollow"&gt;Angel.com IVR Solutions&lt;/a&gt; and we push our customers to develop an integration with their customer database to provide a more "personalized" experience for the caller.  By integrating a database, the IVR system can identify the caller based on caller ID, pull their info from the database and automatically decide how to best handle the call based on certain parameters -- such as the skill level saved in the database for the caller.  We've developed a set of "turn-key" integrated solutions with CRM systems like Salesforce.com, Netsuite and SugarCRM specifically for this.

I think you're right that the first step is how to appropriately route consumers to the proper place.  I think the next step is to help the consumer out and not make them jump through the same hoops the next time when you can capture the data the first time.  Can't wait to see the article on your interview with Dell!</description>
		<content:encoded><![CDATA[<p>Great post!  Rating yourself on skill level for routing to the appropriate agent is definitely an interesting idea, and one that I could see employed in a number of companies.  I would caution making the IVR system too long / long-winded with a lot of questions or definitions of the skill levels, but these could work if kept brief.  Consumers are notoriously impatient with lots of automated talking and choices. </p>
<p>I think this could be taken a step further to help repeat callers though.  By asking the caller questions to determine their skill level the first time, then saving this skill level into a CRM system through a database integration with the IVR, the next time the caller calls he/she can be recognized with the saved skill level value and not put back through the questioning process.  </p>
<p>I work at a company called <a href="http://www.angel.com/" title="Angel.com IVR Solutions" rel="nofollow">Angel.com IVR Solutions</a> and we push our customers to develop an integration with their customer database to provide a more &#8220;personalized&#8221; experience for the caller.  By integrating a database, the IVR system can identify the caller based on caller ID, pull their info from the database and automatically decide how to best handle the call based on certain parameters &#8212; such as the skill level saved in the database for the caller.  We&#8217;ve developed a set of &#8220;turn-key&#8221; integrated solutions with CRM systems like Salesforce.com, Netsuite and SugarCRM specifically for this.</p>
<p>I think you&#8217;re right that the first step is how to appropriately route consumers to the proper place.  I think the next step is to help the consumer out and not make them jump through the same hoops the next time when you can capture the data the first time.  Can&#8217;t wait to see the article on your interview with Dell!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
