<?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: SugarCRM &#8220;sorts out Customer Service&#8221; for parade.com</title>
	<atom:link href="http://developers.sugarcrm.com/wordpress/2008/06/17/sugarcrm-sorts-out-customer-service/feed/" rel="self" type="application/rss+xml" />
	<link>http://developers.sugarcrm.com/wordpress/2008/06/17/sugarcrm-sorts-out-customer-service/</link>
	<description>Weblog for the Sugar Developer community</description>
	<lastBuildDate>Mon, 15 Mar 2010 17:55:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: smcnally</title>
		<link>http://developers.sugarcrm.com/wordpress/2008/06/17/sugarcrm-sorts-out-customer-service/comment-page-1/#comment-122</link>
		<dc:creator>smcnally</dc:creator>
		<pubDate>Wed, 18 Jun 2008 03:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://developers.sugarcrm.com/wordpress/?p=137#comment-122</guid>
		<description>Thanks, Clint.

I&#039;ve worked with SugarOS for a few years. We went with SugarPro for this project at Parade.

We&#039;re using a Lead Capture form, pre-defined Lead Sources, a bunch of workflows, several templates, and some logic to confirm submissions appropriately. 

The Lead Capture form is extended to grab additional information like email address, referer (so we know which page the reader selected &quot;Help&quot; or &quot;Contact Us&quot; from), user agent (to get their browser and OS info for tech troubleshooting) and other helpful bits. 

For the initial setup, we had some &quot;help,&quot; but that&#039;s &lt;a href=&quot;http://meanbusiness.com/2008/06/01/good-vendors-and-the-other-kind/&quot; rel=&quot;nofollow&quot;&gt;another, and not particularly positive, story&lt;/a&gt;; we worked it out in the end.

Since launch, we&#039;ve extended Sugar to help us collect, organize and report on Parade&#039;s &lt;a href=&quot;http://www.parade.com/contests/cartoons/061508&quot; rel=&quot;nofollow&quot;&gt;Cartoon Caption Contest&lt;/a&gt;. From Sunday (June 16, 2008) til Tuesday, we&#039;ve collected several thousand entries and can track them all with precision.

We&#039;ll keep on extending Sugar&#039;s use because we can. 

Thanks to you, the Sugar team and the community for a great platform.</description>
		<content:encoded><![CDATA[<p>Thanks, Clint.</p>
<p>I&#8217;ve worked with SugarOS for a few years. We went with SugarPro for this project at Parade.</p>
<p>We&#8217;re using a Lead Capture form, pre-defined Lead Sources, a bunch of workflows, several templates, and some logic to confirm submissions appropriately. </p>
<p>The Lead Capture form is extended to grab additional information like email address, referer (so we know which page the reader selected &#8220;Help&#8221; or &#8220;Contact Us&#8221; from), user agent (to get their browser and OS info for tech troubleshooting) and other helpful bits. </p>
<p>For the initial setup, we had some &#8220;help,&#8221; but that&#8217;s <a href="http://meanbusiness.com/2008/06/01/good-vendors-and-the-other-kind/" rel="nofollow">another, and not particularly positive, story</a>; we worked it out in the end.</p>
<p>Since launch, we&#8217;ve extended Sugar to help us collect, organize and report on Parade&#8217;s <a href="http://www.parade.com/contests/cartoons/061508" rel="nofollow">Cartoon Caption Contest</a>. From Sunday (June 16, 2008) til Tuesday, we&#8217;ve collected several thousand entries and can track them all with precision.</p>
<p>We&#8217;ll keep on extending Sugar&#8217;s use because we can. </p>
<p>Thanks to you, the Sugar team and the community for a great platform.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
