<?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: Why we should care about students&#8217; email addresses and Twitter names</title>
	<atom:link href="http://lincoln.nickjackson.me/why-we-need-emails-and-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://lincoln.nickjackson.me/why-we-need-emails-and-twitter/</link>
	<description>A look into the exciting work of Nick.</description>
	<lastBuildDate>Mon, 13 Feb 2012 14:32:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Nick Jackson</title>
		<link>http://lincoln.nickjackson.me/why-we-need-emails-and-twitter/comment-page-1/#comment-958</link>
		<dc:creator>Nick Jackson</dc:creator>
		<pubDate>Tue, 31 Aug 2010 14:34:02 +0000</pubDate>
		<guid isPermaLink="false">http://lincoln.nickjackson.me/?p=326#comment-958</guid>
		<description>The blog post specifically refers to ZenDesk, although some other solutions such as Parature are also being looked at. I&#039;m a big fan of ZenDesk having used it in other places (the rules, targets and so-on make it so easy to keep on top of everything), but I agree it does look expensive.

The trouble with SAAS is that it seems pricey, but only when put against the raw cost of a package to do the same in-house. For example, 50 agents in ZenDesk is $14400 a year (about £9350), but remember that this includes the whole thing (servers, hosting space, bandwidth, new features, support, set-up, the works) versus a bit of software which you need to provide the infrastructure for. Ultimately it&#039;s down to the circumstances of your helpdesk, number of agents etc. as to whether it makes good sense. I know in big helpdesks it can get very expensive very quickly, but then again in those situations ZenDesk is more likely to cut you a deal.

My only real advice would be to get a trial of the services you&#039;re looking at, and see how they&#039;d work for your particular situation.</description>
		<content:encoded><![CDATA[<p>The blog post specifically refers to ZenDesk, although some other solutions such as Parature are also being looked at. I&#8217;m a big fan of ZenDesk having used it in other places (the rules, targets and so-on make it so easy to keep on top of everything), but I agree it does look expensive.</p>
<p>The trouble with SAAS is that it seems pricey, but only when put against the raw cost of a package to do the same in-house. For example, 50 agents in ZenDesk is $14400 a year (about £9350), but remember that this includes the whole thing (servers, hosting space, bandwidth, new features, support, set-up, the works) versus a bit of software which you need to provide the infrastructure for. Ultimately it&#8217;s down to the circumstances of your helpdesk, number of agents etc. as to whether it makes good sense. I know in big helpdesks it can get very expensive very quickly, but then again in those situations ZenDesk is more likely to cut you a deal.</p>
<p>My only real advice would be to get a trial of the services you&#8217;re looking at, and see how they&#8217;d work for your particular situation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Skelton</title>
		<link>http://lincoln.nickjackson.me/why-we-need-emails-and-twitter/comment-page-1/#comment-928</link>
		<dc:creator>Nick Skelton</dc:creator>
		<pubDate>Mon, 23 Aug 2010 21:13:32 +0000</pubDate>
		<guid isPermaLink="false">http://lincoln.nickjackson.me/?p=326#comment-928</guid>
		<description>Which SAAS help desk package are you looking at and keen on? A Bristol we&#039;re looking to replace our current system, and all the options look expensive.</description>
		<content:encoded><![CDATA[<p>Which SAAS help desk package are you looking at and keen on? A Bristol we&#8217;re looking to replace our current system, and all the options look expensive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex Bilbie</title>
		<link>http://lincoln.nickjackson.me/why-we-need-emails-and-twitter/comment-page-1/#comment-919</link>
		<dc:creator>Alex Bilbie</dc:creator>
		<pubDate>Sun, 22 Aug 2010 21:25:45 +0000</pubDate>
		<guid isPermaLink="false">http://lincoln.nickjackson.me/?p=326#comment-919</guid>
		<description>One solution is to add extra fields enrolment forms for Twitter/Facebook/Foursquare/whatever ID</description>
		<content:encoded><![CDATA[<p>One solution is to add extra fields enrolment forms for Twitter/Facebook/Foursquare/whatever ID</p>
]]></content:encoded>
	</item>
</channel>
</rss>

