<?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: Chronological order or reverse order?</title>
	<atom:link href="http://www.serviceuntitled.com/chronological-order-or-reverse-order/2009/01/09/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.serviceuntitled.com/chronological-order-or-reverse-order/2009/01/09/</link>
	<description>The blog about customer service and the customer service experience.</description>
	<lastBuildDate>Tue, 16 Mar 2010 19:31:02 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Julia</title>
		<link>http://www.serviceuntitled.com/chronological-order-or-reverse-order/2009/01/09/comment-page-1/#comment-881166</link>
		<dc:creator>Julia</dc:creator>
		<pubDate>Thu, 15 Jan 2009 13:46:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/?p=934#comment-881166</guid>
		<description>I agree with Gary. In our ticketing system, the most recent messages are normally shown on top and you can change it with one click. 

Showing the oldest items on top is important if different agents handle the same ticket. Otherwise, if the same agent takes care of the whole conversation, he/she will probably remember what was going on before and won&#039;t need to re-read all the time. Some tickets can be pretty lenghthy.</description>
		<content:encoded><![CDATA[<p>I agree with Gary. In our ticketing system, the most recent messages are normally shown on top and you can change it with one click. </p>
<p>Showing the oldest items on top is important if different agents handle the same ticket. Otherwise, if the same agent takes care of the whole conversation, he/she will probably remember what was going on before and won&#8217;t need to re-read all the time. Some tickets can be pretty lenghthy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gary Sherman</title>
		<link>http://www.serviceuntitled.com/chronological-order-or-reverse-order/2009/01/09/comment-page-1/#comment-878668</link>
		<dc:creator>Gary Sherman</dc:creator>
		<pubDate>Mon, 12 Jan 2009 21:40:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.serviceuntitled.com/?p=934#comment-878668</guid>
		<description>I prefer most recent at the top, with the ability to easily flip it on the fly.
For most case (ticket, incident) histories, I typically only care about the most recent stuff. But occasionally, I want to be able to easily start from the beginning.</description>
		<content:encoded><![CDATA[<p>I prefer most recent at the top, with the ability to easily flip it on the fly.<br />
For most case (ticket, incident) histories, I typically only care about the most recent stuff. But occasionally, I want to be able to easily start from the beginning.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
