<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" 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>Contact Center Strategies</title>
<link>http://blog.tmcnet.com/contact-center-strategies/</link>
<description></description>
<dc:language>en-us</dc:language>
<dc:rights>Copyright 2013</dc:rights>
<dc:date>2009-03-30T16:57:55+00:00</dc:date>
<admin:generatorAgent rdf:resource="http://www.movabletype.org/?v=4.38" />
<sy:updatePeriod>hourly</sy:updatePeriod>
<sy:updateFrequency>1</sy:updateFrequency>
<sy:updateBase>2000-01-01T12:00+00:00</sy:updateBase>

<item>
<title>The Evolving Contact Center Architecture</title>
<link>http://blog.tmcnet.com/contact-center-strategies/2009/03/the_evolving_contact_center_architecture.html</link>
<guid isPermaLink="false">40313@http://blog.tmcnet.com/contact-center-strategies/</guid>
<description><![CDATA[<p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><font face="Cambria">So many things in our daily world have been changed by technology, and mostly for the positive. Advancements in radio technologies paved the way for the mobile telephone; research in compression technologies helped usher VoIP to our desktops and ultimately laptops; and now we have combined the best of each of these on the supercomputers we each carry in our pocket - the smart phone.<span style="mso-spacerun: yes">&#160; </span>"Why does this matter for the contact center?" you ask.<span style="mso-spacerun: yes">&#160; </span></font></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><o:p><span style="font-size: medium"><font face="Cambria">&#160;</font></span></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><font face="Cambria">Contact Center architectures are a hybrid of technologies; call routing engines, dialers, databases, phone systems, analytics and reporting tools - just to name a few.<span style="mso-spacerun: yes">&#160;&#160; </span>In many cases, these tools are interconnected using various protocols that provide integration under the guise of CTI (Computer/Telephone Integration).<span style="mso-spacerun: yes">&#160; </span>This integration has provided the glue that allows contact centers to provide for the rather <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal">transactional</i></b> nature in which they operate.<span style="mso-spacerun: yes">&#160; </span>Merging customer databases into outbound dialing campaigns; enabling "screen pops" for agents handling incoming customer calls; capturing sales trends and close ratios for agents while mapping this to customer detail.<span style="mso-spacerun: yes">&#160; </span>All of this requiring rather complex CTI scripting and ultimately, customer routing along the way.<span style="mso-spacerun: yes">&#160; </span></font></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><o:p><span style="font-size: medium"><font face="Cambria">&#160;</font></span></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><span style=""><font face="Cambria">No longer is the simple transaction the simple transaction.<span style="mso-spacerun: yes">&#160; </span>In much the same way that telephony matured to provide for mobility and the mainframe matured to provide for mobile computing, customer's expectations have matured along with these trends of increased intelligence.<span style="mso-spacerun: yes">&#160; </span>No longer is it acceptable just to manage the transaction.</font></span></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><o:p><span style="font-size: medium"><font face="Cambria">&#160;</font></span></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><span style=""><font face="Cambria">This is requiring contact centers to evolve their architectures and processes for serving their customers.<span style="mso-spacerun: yes">&#160;&#160; </span>The move towards a <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal">managed</i></b> contact center began a number of years ago as they began to see the need for measuring agent performance, customer satisfaction, and automated support.<span style="mso-spacerun: yes">&#160; </span>The implementation of measurement allows for the easy transition into an <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal">optimized</i></b> contact center model where the performance and customer data can now be used to make real time decisions. </font></span></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><o:p><span style="font-size: medium"><font face="Cambria">&#160;</font></span></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><font face="Cambria">Many companies operate contact centers in this optimized manner today and they're able to balance their investments and customer satisfaction.<span style="mso-spacerun: yes">&#160; </span>However, as the end-customer's expectations are again changing, contact centers too will have to evolve.<span style="mso-spacerun: yes">&#160; </span>I'm calling the next phase of this architectural revolution <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal">enterprise integrated</i></b>.</font></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><o:p><span style="font-size: medium"><font face="Cambria">&#160;</font></span></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><span style=""><font face="Cambria">In the enterprise integrated contact center, technology deployment allows for front and back-office integration with business systems.<span style="mso-spacerun: yes">&#160; </span>The entrance of speech analytics, automated agent selection, non-traditional agent usage models, and a deep integration with CRM systems are more of the advancements we'll see in those contact centers operating in this model.<span style="mso-spacerun: yes">&#160; </span>Today, there are very few who can honestly place themselves in this model.</font></span></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><o:p><span style="font-size: medium"><font face="Cambria">&#160;</font></span></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><font face="Cambria">As technology evolves, we'll move into the <b style="mso-bidi-font-weight: normal"><i style="mso-bidi-font-style: normal">customer integrated</i></b> model.<span style="mso-spacerun: yes">&#160; </span>Here, real-time customer treatment is possible - leveraging every breadcrumb left behind from every interaction to provide the best possible experience for end customers.<span style="mso-spacerun: yes">&#160; </span>This will require significant integration of the legacy systems I talked about in the transaction-based model.<span style="mso-spacerun: yes">&#160; </span>We're making progress in the direction to allow for this and are able to provide many of the tools today.<span style="mso-spacerun: yes">&#160;&#160; </span></font></span></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><o:p><span style="font-size: medium"><font face="Cambria">&#160;</font></span></o:p></p><p class="MsoNormal" style="margin: 0in 0in 0pt"><span style="font-size: medium"><span style=""><font face="Cambria">Today at VoiceCon, we are announcing new technologies and solutions that enable this transformation to occur.</font></span></span></p>]]><![CDATA[<p>
Tags: 
Related tags: <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact center" title="contact center" rel="tag">contact center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact centers" title="contact centers" rel="tag">contact centers</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/abreast latest" title="abreast latest" rel="tag">abreast latest</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/keeping architecture" title="keeping architecture" rel="tag">keeping architecture</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/technologies brought" title="technologies brought" rel="tag">technologies brought</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/customer" title="customer" rel="tag">customer</a>
<br>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/avaya" title="avaya" rel="tag">avaya</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/ contact center" title=" contact center" rel="tag"> contact center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/ call center" title=" call center" rel="tag"> call center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/ unified communications" title=" unified communications" rel="tag"> unified communications</a><br>
<ul>

</ul>
<b>Related Entries</b>

 <a href="http://blog.tmcnet.com/contact-center-strategies/2009/03/the_evolving_contact_center_architecture.html#trackback">TrackBacks</a>
 | <a href="http://blog.tmcnet.com/contact-center-strategies/2009/03/the_evolving_contact_center_architecture.html#comments" title="Comment on: The Evolving Contact Center Architecture">Comments</a> | <a href="http://del.icio.us/post?url=http://blog.tmcnet.com/contact-center-strategies/2009/03/the_evolving_contact_center_architecture.html&title=The%20Evolving%20Contact%20Center%20Architecture">Tag with del.icio.us</a> | <a href="http://blog.tmcnet.com/contact-center-strategies/">Contact Center Strategies Home</a> | Permalink: <a href="http://blog.tmcnet.com/contact-center-strategies/2009/03/the_evolving_contact_center_architecture.html" title="The Evolving Contact Center Architecture">The Evolving Contact Center Architecture</a></p>
<!--end-->
Copyright <a href="http://blog.tmcnet.com/contact-center-strategies/">Contact Center Strategies</a>

<p><map name="google_ad_map_090330165755">
<area shape="rect" href="http://imageads.googleadservices.com/pagead/imgclick/090330165755?pos=0" coords="1,2,367,28"/>
<area shape="rect" href="http://services.google.com/feedback/abg" coords="384,10,453,23"/></map>
<img usemap="#google_ad_map_090330165755" border="0" src="http://imageads.googleadservices.com/pagead/ads?format=468x30_aff_img&client=ca-pub-8317963745003590&channel=0771188340Call with FONcall™0771188340Connecting...Connected!Error: could not place callbug?&output=png&cuid=090330165755&amp;url=http%3A%2F%2Fblog.tmcnet.com%2Fcontact-center-strategies%2F2009%2F03%2Fthe_evolving_contact_center_architecture.html"/></p>]]></description>

<dc:subject>avaya</dc:subject>
<dc:subject> contact center</dc:subject>
<dc:subject> call center</dc:subject>
<dc:subject> unified communications</dc:subject>
<dc:subject>contact center</dc:subject>
<dc:subject>contact centers</dc:subject>
<dc:subject>abreast latest</dc:subject>
<dc:subject>keeping architecture</dc:subject>
<dc:subject>technologies brought</dc:subject>
<dc:subject>customer</dc:subject>

<pubDate>Mon, 30 Mar 2009 16:57:55 +0000</pubDate>
<dc:date>2009-03-30T16:57:55+00:00</dc:date>

</item>

 

<item>
<title>When Self-Service Applications Fail to Deliver</title>
<link>http://blog.tmcnet.com/contact-center-strategies/2009/02/when_self-service_applications_fail_to_deliver.html</link>
<guid isPermaLink="false">39870@http://blog.tmcnet.com/contact-center-strategies/</guid>
<description><![CDATA[<span style="font-size: 11pt; font-family: Arial; mso-fareast-font-family: 'Times New Roman'; mso-ansi-language: EN-US; mso-fareast-language: EN-US; mso-bidi-language: AR-SA">Yesterday, while getting ready to fly back home from a meeting, I thought I would try a new auto-identification application the airline had installed some months back. &#160;I'm normally a first adopter of anything that can make my life easier (Tivo, Roomba, etc.), but I had to wait a number of months to see this new offering mature. &#160;So, I found myself with a few moments to register with the Web site and on the dial tool as well. &#160;I put in my cell number, confirmed it and went off to call them to arrange my seating preference for the flight. <br /><br />I phoned the 800 number and hit the first IVR prompt - asking for an agent immediately. &#160;It responded with: "Hi, welcome to the tool (we'll keep it anonymous), I can confirm your online preferences if you like". &#160;I'm instantly pleased! &#160;It told me my name, I confirmed that I was in fact that person and answered a few other personalization questions and now I'm ready to get to that agent I so badly wanted. &#160;I told it that I was in need of travel in the 50 states and I got routed off immediately. &#160;I'm really happy. &#160;<br /><br />Next I hear the agent come on the line, my expectations are high, exciting building, and then.... She asks for my frequent flyer number. &#160;I respond with a simple question of: "Didn't you get that on your screen when the call routed?" &#160;I'm then told that no, I'm sorry, I didn't get that information, but I can help you - which in fact she did without issue. &#160;But the fact of the matter was that I really wanted to see the technology work. &#160;I mean inbound calling, coupled with number recognition, CTI integration to my profile, and a screen pop - that's just a simplistic application, but for those of us who travel and have had to deal with the background noise issues on speech recognition systems - it's a huge upgrade!<br /><br />So, I decided to give it another try, after all, I know there's a ton of backend systems being deployed to get this all working. &#160;So I phone again, this time it recognizes me immediately and indicates that I'm flying from airport ABC -- GREAT, I think. &#160;I answer the question, that yes, that's correct and I want to speak to an agent. &#160;My call gets routed, and again -- the agent has no clue who I am or what flight I'm calling about! &#160;I'm deflated, disappointed. <br /><br />The lesson here is that this is a great example of the customer experience failing the expected performance, and something that this particular airline will need to address for sure. &#160;It's not enough to make me not travel with them, but still failed to hit the mark. <br /><br />What's true today is that many contact centers are struggling to manage their OPEX and CAPEX in these troubled markets. &#160;&#160;And moreover, many of them are using legacy voice systems from various vendors, ACD's from other vendors, CTI integration from yet, another -- you get the picture. &#160;Again, not completely a bad thing, but quite complicated to deploy. &#160;Why might you ask? &#160;Most all of these systems have evolved over time and are standalone for all the right reasons, but lack a common integration language. &#160;<br /><br />We must evolve the architecture of the classic contact center, as customers expect more and are driving alternate vehicles for interacting with contact centers from instant messaging, voice, the Web, and even video. &#160;Each of these can be seen as merely an application supporting the interaction type required, however, the various jigsaw pieces that are deployed in many contact centers today may not scale to support them. &#160;Front ending these deployments with various pre-route treatment systems is not the answer to scale for the future for sure. &#160;Contact center architectures must evolve and leverage a new set of technologies to support these changing interaction methods. &#160;This will be even more true as the population of Gen Y'ers move to become mainstream purchasers, banking clients, etc - since they've grown up thinking differently. &#160;This NET generation expects personalization to be ready for them, for systems to anticipate their needs. They're edgy, NET-ready. &#160;Many even come with an optional wireless card embedded, making networking a snap<img src="http://blog.tmcnet.com/images/smileys/smiley2.gif" alt="wink" border="0" /><br /><br />Over the coming weeks, we'll discuss how technology is evolving in the core of the communication systems and how that transformation is delivering on a new call center architecture possibility for consideration.&#160;&#160;</span>]]><![CDATA[<p>
Tags: <a href="http://blog.tmcnet.com/contact-center-strategies/tag/Avaya" rel="tag">Avaya</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/call%20center" rel="tag">call center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact%20center" rel="tag">contact center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/self%20service" rel="tag">self service</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/unified%20communications" rel="tag">unified communications</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/voip" rel="tag">voip</a>
Related tags: <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact centers" title="contact centers" rel="tag">contact centers</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact center" title="contact center" rel="tag">contact center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/customer expectations" title="customer expectations" rel="tag">customer expectations</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/customer experience" title="customer experience" rel="tag">customer experience</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/systems" title="systems" rel="tag">systems</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/number" title="number" rel="tag">number</a>
<br>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/Avaya" title="Avaya" rel="tag">Avaya</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/self service" title="self service" rel="tag">self service</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact center" title="contact center" rel="tag">contact center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/voip" title="voip" rel="tag">voip</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/ip telephony" title="ip telephony" rel="tag">ip telephony</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/unified communications" title="unified communications" rel="tag">unified communications</a><br>
<ul>

</ul>

<b>Related Entries</b>

 <a href="http://blog.tmcnet.com/contact-center-strategies/2009/02/when_self-service_applications_fail_to_deliver.html#trackback">TrackBacks</a>
 | <a href="http://blog.tmcnet.com/contact-center-strategies/2009/02/when_self-service_applications_fail_to_deliver.html#comments" title="Comment on: When Self-Service Applications Fail to Deliver">Comments</a> | <a href="http://del.icio.us/post?url=http://blog.tmcnet.com/contact-center-strategies/2009/02/when_self-service_applications_fail_to_deliver.html&title=When%20Self-Service%20Applications%20Fail%20to%20Deliver">Tag with del.icio.us</a> | <a href="http://blog.tmcnet.com/contact-center-strategies/">Contact Center Strategies Home</a> | Permalink: <a href="http://blog.tmcnet.com/contact-center-strategies/2009/02/when_self-service_applications_fail_to_deliver.html" title="When Self-Service Applications Fail to Deliver">When Self-Service Applications Fail to Deliver</a></p>
<!--end-->
Copyright <a href="http://blog.tmcnet.com/contact-center-strategies/">Contact Center Strategies</a>


<p><map name="google_ad_map_090220194213">
<area shape="rect" href="http://imageads.googleadservices.com/pagead/imgclick/090220194213?pos=0" coords="1,2,367,28"/>
<area shape="rect" href="http://services.google.com/feedback/abg" coords="384,10,453,23"/></map>
<img usemap="#google_ad_map_090220194213" border="0" src="http://imageads.googleadservices.com/pagead/ads?format=468x30_aff_img&client=ca-pub-8317963745003590&channel=0771188340Call with FONcall™0771188340Connecting...Connected!Error: could not place callbug?&output=png&cuid=090220194213&amp;url=http%3A%2F%2Fblog.tmcnet.com%2Fcontact-center-strategies%2F2009%2F02%2Fwhen_self-service_applications_fail_to_deliver.html"/></p>]]></description>
<dc:subject>Avaya</dc:subject>
<dc:subject>call center</dc:subject>
<dc:subject>contact center</dc:subject>
<dc:subject>self service</dc:subject>
<dc:subject>unified communications</dc:subject>
<dc:subject>voip</dc:subject>

<dc:subject>Avaya</dc:subject>
<dc:subject>self service</dc:subject>
<dc:subject>contact center</dc:subject>
<dc:subject>voip</dc:subject>
<dc:subject>ip telephony</dc:subject>
<dc:subject>unified communications</dc:subject>
<dc:subject>contact centers</dc:subject>
<dc:subject>contact center</dc:subject>
<dc:subject>customer expectations</dc:subject>
<dc:subject>customer experience</dc:subject>
<dc:subject>systems</dc:subject>
<dc:subject>number</dc:subject>

<pubDate>Fri, 20 Feb 2009 19:42:13 +0000</pubDate>
<dc:date>2009-02-20T19:42:13+00:00</dc:date>

</item>

<item>
<title>Realities of managing the customer experience in the contact center.</title>
<link>http://blog.tmcnet.com/contact-center-strategies/2009/02/realities_of_managing_the_customer_experience_in_the_contact_center.html</link>
<guid isPermaLink="false">39694@http://blog.tmcnet.com/contact-center-strategies/</guid>
<description><![CDATA[<div>Today, many contact centers are managing their resources and investments on a cost per contact basis. But while this is a core metric for managing those centers, I would argue that in the current economic climate, there may be more to the equation than just this. &#160;For contact center managers, understanding the customer experience, and moreover managing it more effectively, is rapidly becoming equally important. &#160;With the trend moving more towards a self-service model, managers are increasingly challenged to provide a positive experience, while keeping the overall cost to service their customers low. <br /><br />Today, the measured customer satisfaction rating for these self service interactions is relatively low, leaving room for improvement, and in some cases, room for innovation. &#160;This can come from a myriad of&#160;issues that many of us have faced in our own interactions with Web and phone support systems in use today. &#160;What's more is that when a failed self service interaction results in a phone call, the lack of connection between the two interactions only further frustrates the consumer.</div><div><br />Customers want and expect more. This calls for self service tools that go beyond basic inbound and outbound voice<b> -</b> and create a productive interaction that uses speech to its greatest capacity, while connecting to live agents only as needed.&#160;In addition, there should be a recognition that there have to be self service solutions tailored to specific company needs, based not only on a specific industry's requirements and practices, but also by helping serve the commonly accepted ways in which customers are comfortable sharing information.&#160;This, of course, introduces a new set of challenges, such as security and cost to serve, but companies can start with the goal of striving for and providing outstanding customer service. After this is established, companies can build upon this momentum as the company matures.</div>]]><![CDATA[<p>
Tags: 
Related tags: <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact center" title="contact center" rel="tag">contact center</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/customer experience" title="customer experience" rel="tag">customer experience</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/service" title="service" rel="tag">service</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/managing" title="managing" rel="tag">managing</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/customer" title="customer" rel="tag">customer</a>, <a href="http://blog.tmcnet.com/contact-center-strategies/tag/contact" title="contact" rel="tag">contact</a>
<br><br>
<ul>

</ul>

<b>Related Entries</b>

 <a href="http://blog.tmcnet.com/contact-center-strategies/2009/02/realities_of_managing_the_customer_experience_in_the_contact_center.html#trackback">TrackBacks</a>
 | <a href="http://blog.tmcnet.com/contact-center-strategies/2009/02/realities_of_managing_the_customer_experience_in_the_contact_center.html#comments" title="Comment on: Realities of managing the customer experience in the contact center.">Comments</a> | <a href="http://del.icio.us/post?url=http://blog.tmcnet.com/contact-center-strategies/2009/02/realities_of_managing_the_customer_experience_in_the_contact_center.html&title=Realities%20of%20managing%20the%20customer%20experience%20in%20the%20contact%20center.">Tag with del.icio.us</a> | <a href="http://blog.tmcnet.com/contact-center-strategies/">Contact Center Strategies Home</a> | Permalink: <a href="http://blog.tmcnet.com/contact-center-strategies/2009/02/realities_of_managing_the_customer_experience_in_the_contact_center.html" title="Realities of managing the customer experience in the contact center.">Realities of managing the customer experience in the contact center.</a></p>
<!--end-->
Copyright <a href="http://blog.tmcnet.com/contact-center-strategies/">Contact Center Strategies</a>


<p><map name="google_ad_map_090211172138">
<area shape="rect" href="http://imageads.googleadservices.com/pagead/imgclick/090211172138?pos=0" coords="1,2,367,28"/>
<area shape="rect" href="http://services.google.com/feedback/abg" coords="384,10,453,23"/></map>
<img usemap="#google_ad_map_090211172138" border="0" src="http://imageads.googleadservices.com/pagead/ads?format=468x30_aff_img&client=ca-pub-8317963745003590&channel=0771188340Call with FONcall™0771188340Connecting...Connected!Error: could not place callbug?&output=png&cuid=090211172138&amp;url=http%3A%2F%2Fblog.tmcnet.com%2Fcontact-center-strategies%2F2009%2F02%2Frealities_of_managing_the_customer_experience_in_the_contact_center.html"/></p>]]></description>
<dc:subject>contact center</dc:subject>
<dc:subject>customer experience</dc:subject>
<dc:subject>service</dc:subject>
<dc:subject>managing</dc:subject>
<dc:subject>customer</dc:subject>
<dc:subject>contact</dc:subject>

<pubDate>Wed, 11 Feb 2009 17:21:38 +0000</pubDate>
<dc:date>2009-02-11T17:21:38+00:00</dc:date>

</item>

</channel>
</rss>