<?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: 10 Top Tips for Handholding</title>
	<atom:link href="http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/feed/" rel="self" type="application/rss+xml" />
	<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/</link>
	<description>Go Where Your VisionPoints</description>
	<lastBuildDate>Thu, 06 Oct 2011 13:16:45 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: Inspiration Points: 10 Sneaky Ways To Capture 10% of Your Market &#124; Maximum Customer Experience Blog</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-139081</link>
		<dc:creator>Inspiration Points: 10 Sneaky Ways To Capture 10% of Your Market &#124; Maximum Customer Experience Blog</dc:creator>
		<pubDate>Wed, 30 Jun 2010 07:20:16 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-139081</guid>
		<description>[...] know all about handholding. You know about writing your own story. You know about showing off your passion for what you do. But [...]</description>
		<content:encoded><![CDATA[<p>[...] know all about handholding. You know about writing your own story. You know about showing off your passion for what you do. But [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Erickson</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-131271</link>
		<dc:creator>Kelly Erickson</dc:creator>
		<pubDate>Thu, 03 Jun 2010 12:40:49 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-131271</guid>
		<description>Steven,

Hello and welcome to Maximum Customer Experience!

Be like the customer is an excellent addition. And I got a good laugh out of the last subset of that tip: &quot;If the customer is flakey, give them support.&quot; Sometimes those folks are the truest fans you can have because so few people take the time to understand their needs! Well-said!

Regards,

Kelly</description>
		<content:encoded><![CDATA[<p>Steven,</p>
<p>Hello and welcome to Maximum Customer Experience!</p>
<p>Be like the customer is an excellent addition. And I got a good laugh out of the last subset of that tip: &#8220;If the customer is flakey, give them support.&#8221; Sometimes those folks are the truest fans you can have because so few people take the time to understand their needs! Well-said!</p>
<p>Regards,</p>
<p>Kelly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Di Pietro</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-130958</link>
		<dc:creator>Steven Di Pietro</dc:creator>
		<pubDate>Wed, 02 Jun 2010 13:01:52 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-130958</guid>
		<description>Kelly,

Love the post. 

I would suggest also to Be like the customer.  We all change how we act in different situations, eg we act different at work, and different at home.  When we talk to a child we talk different to when we talk to a friend.  Likewise, when we talk to a customer we should be like the customer - I mean - be like that individual customer.

If the customer is impatient, talk fast.
If the customer is in for a chat, then chat.
If the customer wants process, give them process.
If the customer is flakey, give them support.

Go beyond empathy, be like the customer.</description>
		<content:encoded><![CDATA[<p>Kelly,</p>
<p>Love the post. </p>
<p>I would suggest also to Be like the customer.  We all change how we act in different situations, eg we act different at work, and different at home.  When we talk to a child we talk different to when we talk to a friend.  Likewise, when we talk to a customer we should be like the customer &#8211; I mean &#8211; be like that individual customer.</p>
<p>If the customer is impatient, talk fast.<br />
If the customer is in for a chat, then chat.<br />
If the customer wants process, give them process.<br />
If the customer is flakey, give them support.</p>
<p>Go beyond empathy, be like the customer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. A. Kobu</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-130439</link>
		<dc:creator>C. A. Kobu</dc:creator>
		<pubDate>Mon, 31 May 2010 18:48:07 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-130439</guid>
		<description>Graham, I agree with you that the information on a web site must be provided to the visitors as fast as possible. SAQ and RAQ can never take the place of a well-formulated FAQ. But they can compliment it. Yet, it all depends on the context and the customer profiling. By the way, I love your idea of keeping an &#039;alive and kicking&#039; FAQ document at hand and revising it whenever needed.</description>
		<content:encoded><![CDATA[<p>Graham, I agree with you that the information on a web site must be provided to the visitors as fast as possible. SAQ and RAQ can never take the place of a well-formulated FAQ. But they can compliment it. Yet, it all depends on the context and the customer profiling. By the way, I love your idea of keeping an &#8216;alive and kicking&#8217; FAQ document at hand and revising it whenever needed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Erickson</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-129741</link>
		<dc:creator>Kelly Erickson</dc:creator>
		<pubDate>Fri, 28 May 2010 22:08:09 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-129741</guid>
		<description>C.A.,

It&#039;s a cool idea. If you do it, do drop a link here so we can see it!

Graham,

Of course!! Not at all instead of! (Well, not in my mind....) I was imagining them alongside, or in the same dropdown with FAQs, or maybe as bonus-y links &lt;em&gt;from&lt;/em&gt; the FAQs, something like that. Don&#039;t Make Me Think is always the first rule. &quot;Give me a smile or a surprise&quot; is way down the list.

As always, you bring up great points.   :)

Until later,

Kelly</description>
		<content:encoded><![CDATA[<p>C.A.,</p>
<p>It&#8217;s a cool idea. If you do it, do drop a link here so we can see it!</p>
<p>Graham,</p>
<p>Of course!! Not at all instead of! (Well, not in my mind&#8230;.) I was imagining them alongside, or in the same dropdown with FAQs, or maybe as bonus-y links <em>from</em> the FAQs, something like that. Don&#8217;t Make Me Think is always the first rule. &#8220;Give me a smile or a surprise&#8221; is way down the list.</p>
<p>As always, you bring up great points.   <img src='http://maximumcustomerexperience.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Until later,</p>
<p>Kelly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Strong</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-129671</link>
		<dc:creator>Graham Strong</dc:creator>
		<pubDate>Fri, 28 May 2010 13:49:04 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-129671</guid>
		<description>P.S. - not to be a downer on your idea of changing the FAQ, C.A. I just re-read this and saw that it could be taken that way. I love the idea, and in a perfect world we should all be thinking up fresh new ways to say &quot;About Us&quot; (I know I always did). 

It&#039;s only that, bottom line, it doesn&#039;t always work. People aren&#039;t at a website to read lyrical words, they&#039;re there to get their information. Preferably as quickly as possible. If you have a captive audience or if it is a &quot;just for fun&quot; website, then great, come up with all the newest, freshest phrases you can. But if you are trying to sell something (products, services, whatever), it is usually best to make navigation as straightforward as possible.

I&#039;ll stop rambling now...

~Graham</description>
		<content:encoded><![CDATA[<p>P.S. &#8211; not to be a downer on your idea of changing the FAQ, C.A. I just re-read this and saw that it could be taken that way. I love the idea, and in a perfect world we should all be thinking up fresh new ways to say &#8220;About Us&#8221; (I know I always did). </p>
<p>It&#8217;s only that, bottom line, it doesn&#8217;t always work. People aren&#8217;t at a website to read lyrical words, they&#8217;re there to get their information. Preferably as quickly as possible. If you have a captive audience or if it is a &#8220;just for fun&#8221; website, then great, come up with all the newest, freshest phrases you can. But if you are trying to sell something (products, services, whatever), it is usually best to make navigation as straightforward as possible.</p>
<p>I&#8217;ll stop rambling now&#8230;</p>
<p>~Graham</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Graham Strong</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-129669</link>
		<dc:creator>Graham Strong</dc:creator>
		<pubDate>Fri, 28 May 2010 13:30:38 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-129669</guid>
		<description>The FAQ page is, in my opinion, definitely one of the most important pages for some websites. It&#039;s also the quintessential hand-holding page. Here&#039;s what we do, here&#039;s what you may not know, etc. etc. 

However as you point out Kelly, it is often not used properly. The best policy is to actually include questions you get from customers. Usually there is a large disconnect between the question at point-of-contact with the customer, and actually going to update the website. This seems to be especially if you rely on a web designer/Webmaster to do the updating for you.

Perhaps a solution is to keep a Word document (or a fancy MS Office Note) handy on your desktop so you can add questions as they come up. That way, when you do go to update your website, you have the list at your fingertips.

I&#039;m a little hesitant about changing the name &quot;FAQ&quot; though, I must say. Generally, it is not a good idea to make website visitors think (our good friend &lt;a href=&quot;http://www.sensible.com/&quot; rel=&quot;nofollow&quot;&gt;Steve Krug&lt;/a&gt; taught us that). However SAQ or RAQ might be close enough to FAQ to be a no-brainer. And, as always, it depends on the website -- if it is fun AND inherently sticky, changing up names could be intriguing to the website visitor. Definitely some sort of testing should be done before committing to the newer version.

IMHO,

~Graham</description>
		<content:encoded><![CDATA[<p>The FAQ page is, in my opinion, definitely one of the most important pages for some websites. It&#8217;s also the quintessential hand-holding page. Here&#8217;s what we do, here&#8217;s what you may not know, etc. etc. </p>
<p>However as you point out Kelly, it is often not used properly. The best policy is to actually include questions you get from customers. Usually there is a large disconnect between the question at point-of-contact with the customer, and actually going to update the website. This seems to be especially if you rely on a web designer/Webmaster to do the updating for you.</p>
<p>Perhaps a solution is to keep a Word document (or a fancy MS Office Note) handy on your desktop so you can add questions as they come up. That way, when you do go to update your website, you have the list at your fingertips.</p>
<p>I&#8217;m a little hesitant about changing the name &#8220;FAQ&#8221; though, I must say. Generally, it is not a good idea to make website visitors think (our good friend <a href="http://www.sensible.com/" rel="nofollow">Steve Krug</a> taught us that). However SAQ or RAQ might be close enough to FAQ to be a no-brainer. And, as always, it depends on the website &#8212; if it is fun AND inherently sticky, changing up names could be intriguing to the website visitor. Definitely some sort of testing should be done before committing to the newer version.</p>
<p>IMHO,</p>
<p>~Graham</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. A. Kobu</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-129664</link>
		<dc:creator>C. A. Kobu</dc:creator>
		<pubDate>Fri, 28 May 2010 12:08:51 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-129664</guid>
		<description>I&#039;m actually considering adding SAQ to one of my blogs (still building). I haven&#039;t come across a formal, separate section in the menu before except for one site. They had RAQ. Too bad I can&#039;t remember the name, but I do remember that the site had an overall fun approach to rather serious services (or the kind of services that are often &#039;bestowed upon&#039; the customer with a grim face and a raised eyebrow :)) That&#039;s how I made an evernote to myself: ADD SAQ (easier to pronounce than RAQ). More people must have used it. I&#039;m sure.

Cheers,
C. A.</description>
		<content:encoded><![CDATA[<p>I&#8217;m actually considering adding SAQ to one of my blogs (still building). I haven&#8217;t come across a formal, separate section in the menu before except for one site. They had RAQ. Too bad I can&#8217;t remember the name, but I do remember that the site had an overall fun approach to rather serious services (or the kind of services that are often &#8216;bestowed upon&#8217; the customer with a grim face and a raised eyebrow <img src='http://maximumcustomerexperience.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> ) That&#8217;s how I made an evernote to myself: ADD SAQ (easier to pronounce than RAQ). More people must have used it. I&#8217;m sure.</p>
<p>Cheers,<br />
C. A.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Erickson</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-129660</link>
		<dc:creator>Kelly Erickson</dc:creator>
		<pubDate>Fri, 28 May 2010 11:41:33 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-129660</guid>
		<description>C.A.,

Absolutely! I definitely incorporate both RAQs and SAQs when writing Frequently Asked Questions. Actually, now that you&#039;ve given them such clever names I&#039;m wondering whether that would be fun to see formally—right IN the menu, of a site with the right sort of humor going on. Wondering whether more people would click on the acronyms they don&#039;t know and learn something cool about the company. Hm, hm. That would be a neat thing to test out!

Regards,

Kelly</description>
		<content:encoded><![CDATA[<p>C.A.,</p>
<p>Absolutely! I definitely incorporate both RAQs and SAQs when writing Frequently Asked Questions. Actually, now that you&#8217;ve given them such clever names I&#8217;m wondering whether that would be fun to see formally—right IN the menu, of a site with the right sort of humor going on. Wondering whether more people would click on the acronyms they don&#8217;t know and learn something cool about the company. Hm, hm. That would be a neat thing to test out!</p>
<p>Regards,</p>
<p>Kelly</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: C. A. Kobu</title>
		<link>http://maximumcustomerexperience.com/2010/05/28/10-top-tips-for-handholding/comment-page-1/#comment-129647</link>
		<dc:creator>C. A. Kobu</dc:creator>
		<pubDate>Fri, 28 May 2010 09:38:58 +0000</pubDate>
		<guid isPermaLink="false">http://maximumcustomerexperience.com/?p=1387#comment-129647</guid>
		<description>Kelly, I also love the idea of a RAQ (rarely asked questions) or SAQ (seldomly asked questions). Being proactive in answering some anticipated questions before the customer formulates them saves a lot of time. And it helps the customer (or visitor, whatever) to have more clarity in a faster way. One more thing: I really hate the dry lifeless kind of FAQ. Simple language, zero wordiness, and some clever humor do the thing for me.</description>
		<content:encoded><![CDATA[<p>Kelly, I also love the idea of a RAQ (rarely asked questions) or SAQ (seldomly asked questions). Being proactive in answering some anticipated questions before the customer formulates them saves a lot of time. And it helps the customer (or visitor, whatever) to have more clarity in a faster way. One more thing: I really hate the dry lifeless kind of FAQ. Simple language, zero wordiness, and some clever humor do the thing for me.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

