<?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: FACTS ABOUT FAQS</title>
	<atom:link href="http://webmarketingtalk.net/172/172/feed/" rel="self" type="application/rss+xml" />
	<link>http://webmarketingtalk.net/172/172/</link>
	<description>Web Marketing 24/7</description>
	<lastBuildDate>Thu, 26 Aug 2010 02:06:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Graham Price</title>
		<link>http://webmarketingtalk.net/172/172/comment-page-1/#comment-59</link>
		<dc:creator>Graham Price</dc:creator>
		<pubDate>Wed, 10 Mar 2010 03:37:30 +0000</pubDate>
		<guid isPermaLink="false">http://webmarketingtalk.net/172/172/#comment-59</guid>
		<description>Fascinating. Am new to blogging and never even thought about FAQs. I&#039;ll get onto it</description>
		<content:encoded><![CDATA[<p>Fascinating. Am new to blogging and never even thought about FAQs. I&#8217;ll get onto it</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jenny Sanders</title>
		<link>http://webmarketingtalk.net/172/172/comment-page-1/#comment-53</link>
		<dc:creator>Jenny Sanders</dc:creator>
		<pubDate>Tue, 09 Mar 2010 15:45:07 +0000</pubDate>
		<guid isPermaLink="false">http://webmarketingtalk.net/172/172/#comment-53</guid>
		<description>Good idea Dan. What we really need is a sort of FAQ application that manages both the front and back end of dealing with FAQs. Imagine visiting a site, and asking a question via the FAQ application&#039;s form.

The site owner logs into the FAQ program (e.g. gets an email from the application and clicks a link to log in automatically). The owner answers the question, and can check a box to indicate whether or not the question and its answer should be added to the FAQ page.

This would make the whole thing automatic. And could even include built-in functionality to search out similar questions. Somebody must have created this already.</description>
		<content:encoded><![CDATA[<p>Good idea Dan. What we really need is a sort of FAQ application that manages both the front and back end of dealing with FAQs. Imagine visiting a site, and asking a question via the FAQ application&#8217;s form.</p>
<p>The site owner logs into the FAQ program (e.g. gets an email from the application and clicks a link to log in automatically). The owner answers the question, and can check a box to indicate whether or not the question and its answer should be added to the FAQ page.</p>
<p>This would make the whole thing automatic. And could even include built-in functionality to search out similar questions. Somebody must have created this already.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan B</title>
		<link>http://webmarketingtalk.net/172/172/comment-page-1/#comment-51</link>
		<dc:creator>Dan B</dc:creator>
		<pubDate>Tue, 09 Mar 2010 14:59:22 +0000</pubDate>
		<guid isPermaLink="false">http://webmarketingtalk.net/172/172/#comment-51</guid>
		<description>Those are some great tips Ken, just wanted to add my two pence and remind everyone that the FAQs page doesn&#039;t have to be static, questions that a website owner maybe called about on the phone may change over time and at different times of the year. So keep a record of the questions that you might get in a phone call or in person and if they get asked repeatedly consider adding them to the FAQs page.</description>
		<content:encoded><![CDATA[<p>Those are some great tips Ken, just wanted to add my two pence and remind everyone that the FAQs page doesn&#8217;t have to be static, questions that a website owner maybe called about on the phone may change over time and at different times of the year. So keep a record of the questions that you might get in a phone call or in person and if they get asked repeatedly consider adding them to the FAQs page.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
