<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Service Desk Center &#187; Technology</title>
	<atom:link href="http://www.servicedeskcenter.com/category/technology/feed" rel="self" type="application/rss+xml" />
	<link>http://www.servicedeskcenter.com</link>
	<description>How I Am Keeping My Service Desk Alive</description>
	<lastBuildDate>Thu, 28 Feb 2008 09:09:09 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Future Service Desk Characteristics</title>
		<link>http://www.servicedeskcenter.com/future-service-desk-characteristics.html</link>
		<comments>http://www.servicedeskcenter.com/future-service-desk-characteristics.html#comments</comments>
		<pubDate>Thu, 28 Feb 2008 09:09:09 +0000</pubDate>
		<dc:creator>Amos W</dc:creator>
				<category><![CDATA[People]]></category>
		<category><![CDATA[Process]]></category>
		<category><![CDATA[Technology]]></category>

		<guid isPermaLink="false">http://www.servicedeskcenter.com/future-service-desk-characteristics.html</guid>
		<description><![CDATA[If you have worked in a Service Desk environment long enough, you will bound to notice some trends as to the directions people, processes and technologies are taking to.  Below are some of the points that I picked up while attending a seminar and I&#8217;ve added my comments for each item pointed out.

The characteristics that [...]]]></description>
			<content:encoded><![CDATA[<p>If you have worked in a Service Desk environment long enough, you will bound to notice some trends as to the directions people, processes and technologies are taking to.  Below are some of the points that I picked up while attending a seminar and I&#8217;ve added my comments for each item pointed out.</p>
<p style="text-align: center"><img src="http://farm4.static.flickr.com/3250/2297947586_08bd9b7887.jpg" alt="Future" /></p>
<p>The characteristics that Service Desk is moving towards are:</p>
<ol>
<li><strong>Increased use of self help</strong> &#8211; As customers and users become more technologically savvy, they are getting braver nowadays to execute remedial efforts.  Compared to a few years back, these group of customers have become bolder and have embraced technology quicker than ever before. It is therefore a good time for Service Desk manager to re-look into their FAQs and knowledge bases so that their customers can help themselves. <span id="more-13"></span></li>
<li><strong>Improved knowledge bases with contextual searching</strong> &#8211; the tools I work with today have appalling knowledge base design.  The categorization of knowledge leaves much to be desired as is with the search function.  Even a simple wizard-based kind of troubleshooting steps is non-existent.  I&#8217;m using a very famous and probably the world&#8217;s best helpdesk system but yet, the knowledge base module is not quite to my standard. In time to come, you will find better knowledge base designs with better search engines.  I will also expect vendors to adopt wizard based diagnostic/troubleshooting process; much like the current Microsoft&#8217;s Troubleshooter.</li>
<li><strong>Reduction or elimination of deskside support</strong> &#8211; With customers becoming bolder and technology-savvier, this characteristic is bound to follow suit. Now that customers are able to perform remedial actions on their own, deskside support will be reduced.  Furthermore, with technologies such as remote access becoming a common tool in all organizations, IT no longer need to be on-site to assist the customer.</li>
<li><strong>Provision of services through a fully integrated service catalog</strong> &#8211; a service catalog lists down your organization&#8217;s service provision along with the description of such services, the service level for service fulfilment, service entitlement, associated cost and procedures to obtain such services.  Comparing analogically, you can imagine the service catalog like a menu in a restaurant.  In time to come, your customers and users can order services right from their desktop where the system will only display the services that they are entitled to.  The request will then be automatically subjected to an automated approval workflow and service providers are constantly reminded of unfillled services so as to meet the service level.</li>
<li><strong>Remote rebuild &amp; self healing workstations</strong> &#8211; these are technologies that are available today.  For example, Microsoft Vista has an inbuilt self healing system where computers are kept running reliably by automatically detecting and resolving many known problems—requiring little or no effort from the user.  It&#8217;s here in the operating system and before long, it&#8217;s moving to specific applications.  Even software developers are improving their software with such technologies so as to minimize support.</li>
<li><strong>Tight integration with IP Telephony</strong> &#8211; Voice Over IP is cheap; Caller ID makes it personal; Service Desk professional can be mobile and yet reachable through a single number; audio conferencing can be made on the fly; video conversation is available; instant messaging communications is available &#8211; no wonder organizations are embracing IP Telephony.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.servicedeskcenter.com/future-service-desk-characteristics.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
