<?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: Getting started with the Customer Portal</title>
	<atom:link href="http://blog.beetil.com/getting-started-with-the-customer-portal/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.beetil.com/getting-started-with-the-customer-portal/</link>
	<description>Professional service management without the pain</description>
	<lastBuildDate>Fri, 18 May 2012 05:00:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Dan</title>
		<link>http://blog.beetil.com/getting-started-with-the-customer-portal/#comment-88</link>
		<dc:creator>Dan</dc:creator>
		<pubDate>Thu, 24 Sep 2009 03:45:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.beetil.com/?p=197#comment-88</guid>
		<description>Thanks for the feedback Graham.

Improved knowledge management and email interfacing is coming soon.</description>
		<content:encoded><![CDATA[<p>Thanks for the feedback Graham.</p>
<p>Improved knowledge management and email interfacing is coming soon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Robson</title>
		<link>http://blog.beetil.com/getting-started-with-the-customer-portal/#comment-79</link>
		<dc:creator>Graham Robson</dc:creator>
		<pubDate>Tue, 22 Sep 2009 08:16:27 +0000</pubDate>
		<guid isPermaLink="false">http://blog.beetil.com/?p=197#comment-79</guid>
		<description>Blending together the ability to find knowledge (knowledge base), open discussion, and private reporting of incidents is certainly the way to go.

Also would like to see some idea management &amp; voting for feature requests. Since the Beetil back end will managing through to release it can report back on progress. 

Good to see a nice clean client interface, absolutely right with the design aim - needs to be intuitive and a pleasure to use. However, also need to have an email only interface - lots of folks still don&#039;t want to use a portal.</description>
		<content:encoded><![CDATA[<p>Blending together the ability to find knowledge (knowledge base), open discussion, and private reporting of incidents is certainly the way to go.</p>
<p>Also would like to see some idea management &amp; voting for feature requests. Since the Beetil back end will managing through to release it can report back on progress. </p>
<p>Good to see a nice clean client interface, absolutely right with the design aim &#8211; needs to be intuitive and a pleasure to use. However, also need to have an email only interface &#8211; lots of folks still don&#8217;t want to use a portal.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Beetil Blog &#187; Blog Archive &#187; Getting Started with Incident Management</title>
		<link>http://blog.beetil.com/getting-started-with-the-customer-portal/#comment-32</link>
		<dc:creator>Beetil Blog &#187; Blog Archive &#187; Getting Started with Incident Management</dc:creator>
		<pubDate>Mon, 14 Sep 2009 06:59:15 +0000</pubDate>
		<guid isPermaLink="false">http://blog.beetil.com/?p=197#comment-32</guid>
		<description>[...] Beetil and the Customer Portal [...]</description>
		<content:encoded><![CDATA[<p>[...] Beetil and the Customer Portal [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

