<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Bloodhound FAQ</title>
	<link>http://www.ben300.com/TENPLAN/archives/74</link>
	<description>Charting a course for our tenth voyage of discovery to the New World of Education and Technology</description>
	<pubDate>Tue,  6 Jan 2009 10:26:42 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0</generator>

	<item>
		<title>by: David Seto</title>
		<link>http://www.ben300.com/TENPLAN/archives/74#comment-152</link>
		<pubDate>Mon, 16 Oct 2006 18:26:30 +0000</pubDate>
		<guid>http://www.ben300.com/TENPLAN/archives/74#comment-152</guid>
					<description>If I am to understand correctly, you are looking for commentary on a FAQ page for Bloodhound?  This would be a lot easier if there was something to demo in order to pre-empt Qs and As.  FAQ pages will have generic questisions (What is it?, How much does it cost?, Where do I get it?, What about privacy?, Who can help me?, How do I get started?), but many of the questions will be specific to the use of the product (What do I do now that...., How do I.....).  I would recommend an user guide section, that clearly deomstrates how a user would acquire, implement, and deploy their Bloodhound service with screenshots.  That is the first step to take.</description>
		<content:encoded><![CDATA[<p>If I am to understand correctly, you are looking for commentary on a FAQ page for Bloodhound?  This would be a lot easier if there was something to demo in order to pre-empt Qs and As.  FAQ pages will have generic questisions (What is it?, How much does it cost?, Where do I get it?, What about privacy?, Who can help me?, How do I get started?), but many of the questions will be specific to the use of the product (What do I do now that&#8230;., How do I&#8230;..).  I would recommend an user guide section, that clearly deomstrates how a user would acquire, implement, and deploy their Bloodhound service with screenshots.  That is the first step to take.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: skipper</title>
		<link>http://www.ben300.com/TENPLAN/archives/74#comment-151</link>
		<pubDate>Mon, 16 Oct 2006 18:05:06 +0000</pubDate>
		<guid>http://www.ben300.com/TENPLAN/archives/74#comment-151</guid>
					<description>More on Reddit -- for a good model of an FAQ -- more on this very interesting site, visit
http://reddit.com/help/faq

(also, note the URL address and pathway)</description>
		<content:encoded><![CDATA[<p>More on Reddit &#8212; for a good model of an FAQ &#8212; more on this very interesting site, visit<br />
<a href='http://reddit.com/help/faq' rel='nofollow'>http://reddit.com/help/faq</a></p>
<p>(also, note the URL address and pathway)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: skipper</title>
		<link>http://www.ben300.com/TENPLAN/archives/74#comment-150</link>
		<pubDate>Mon, 16 Oct 2006 18:03:15 +0000</pubDate>
		<guid>http://www.ben300.com/TENPLAN/archives/74#comment-150</guid>
					<description>Viewers to this page should visit
http://reddit.com/help/

and crawl all over reddit....one of the fastest growing &quot;social network&quot; sites on the Web -- and in it's own way a source for Bloodhound...and, maybe?, a model for how to acquire and train your Hound?</description>
		<content:encoded><![CDATA[<p>Viewers to this page should visit<br />
<a href='http://reddit.com/help/' rel='nofollow'>http://reddit.com/help/</a></p>
<p>and crawl all over reddit&#8230;.one of the fastest growing &#8220;social network&#8221; sites on the Web &#8212; and in it&#8217;s own way a source for Bloodhound&#8230;and, maybe?, a model for how to acquire and train your Hound?
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: skipper</title>
		<link>http://www.ben300.com/TENPLAN/archives/74#comment-149</link>
		<pubDate>Mon, 16 Oct 2006 16:25:10 +0000</pubDate>
		<guid>http://www.ben300.com/TENPLAN/archives/74#comment-149</guid>
					<description>USE OF THE ADDRESS LINE IN THE URL TO IDENTIFY AND NARROW THE TOPIC OF THE PAGE AND HELP WITH IDENTIFICATION

Ultimately, I would like to see a direct linkage between the url address and the text on the page.  Hopefully, these two examples illustrate what I am talking about.

1.  NOW WE HAVE on the icon TECHNOLOGY
&lt;http://www.bloodhoundsearch.com/technology.htm&gt;


Under my &quot;theory&quot; the Icon would change to ABOUT, with this url:
http://www.bloodhoundsearch.com/about.htm

The ABOUT page then becomes an &quot;index page&quot; which would lead to &quot;drill down pages relevant to &quot;about&quot; issues, each one of these examples as identified in the url address.

Examples reached from
http://www.bloodhoundsearch.com/about/

Each of the below would have a two sentence description followed by a &lt;LEARN MORE&gt; hyperlink leading to these pages

http://www.bloodhoundsearch.com/about/concept.htm
http://www.bloodhoundsearch.com/about/google.htm
http://www.bloodhoundsearch.com/about/technology.htm
http://www.bloodhoundsearch.com/about/business.htm
http://www.bloodhoundsearch.com/about/people.htm
http://www.bloodhoundsearch.com/about/contact.htm
http://www.bloodhoundsearch.com/about/investors.htm
http://www.bloodhoundsearch.com/about/oursite.htm
http://www.bloodhoundsearch.com/about/faq


2. ANOTHER EXAMPLE (FUTURE PLANS)
&lt;http://www.bloodhoundsearch.com/future.htm&gt;


I believe this could change to an icon reading HOUNDS

http://www.bloodhoundsearch.com/Hounds.htm

the HOUNDS &quot;Index&quot; (Directory) would serve as an Index Page leading to those particular page about how to acquire a Hound and how to train him... )

http://www.bloodhoundsearch.com/Hounds/acquirepuppy.htm

http://www.bloodhoundsearch.com/Hounds/trainingpuppy.htm

http://www.bloodhoundsearch.com/Hounds.help/htm

http://www.bloodhoundsearch.com/Hounds/faq.htm

FAQ's would be designed to briefly answer the question with the LEARN MORE hyper link leading &quot;back&quot; to a precise page where the entire issue would be detailed. (Each page would have a link back to both the relevant Index Page and to the Home Page)</description>
		<content:encoded><![CDATA[<p>USE OF THE ADDRESS LINE IN THE URL TO IDENTIFY AND NARROW THE TOPIC OF THE PAGE AND HELP WITH IDENTIFICATION</p>
<p>Ultimately, I would like to see a direct linkage between the url address and the text on the page.  Hopefully, these two examples illustrate what I am talking about.</p>
<p>1.  NOW WE HAVE on the icon TECHNOLOGY<br />
<http://www.bloodhoundsearch.com/technology.htm></p>
<p>Under my &#8220;theory&#8221; the Icon would change to ABOUT, with this url:<br />
<a href='http://www.bloodhoundsearch.com/about.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about.htm</a></p>
<p>The ABOUT page then becomes an &#8220;index page&#8221; which would lead to &#8220;drill down pages relevant to &#8220;about&#8221; issues, each one of these examples as identified in the url address.</p>
<p>Examples reached from<br />
<a href='http://www.bloodhoundsearch.com/about/' rel='nofollow'>http://www.bloodhoundsearch.com/about/</a></p>
<p>Each of the below would have a two sentence description followed by a <LEARN MORE> hyperlink leading to these pages</p>
<p><a href='http://www.bloodhoundsearch.com/about/concept.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/concept.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/google.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/google.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/technology.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/technology.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/business.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/business.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/people.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/people.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/contact.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/contact.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/investors.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/investors.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/oursite.htm' rel='nofollow'>http://www.bloodhoundsearch.com/about/oursite.htm</a><br />
<a href='http://www.bloodhoundsearch.com/about/faq' rel='nofollow'>http://www.bloodhoundsearch.com/about/faq</a></p>
<p>2. ANOTHER EXAMPLE (FUTURE PLANS)<br />
<http://www.bloodhoundsearch.com/future.htm></p>
<p>I believe this could change to an icon reading HOUNDS</p>
<p><a href='http://www.bloodhoundsearch.com/Hounds.htm' rel='nofollow'>http://www.bloodhoundsearch.com/Hounds.htm</a></p>
<p>the HOUNDS &#8220;Index&#8221; (Directory) would serve as an Index Page leading to those particular page about how to acquire a Hound and how to train him&#8230; )</p>
<p><a href='http://www.bloodhoundsearch.com/Hounds/acquirepuppy.htm' rel='nofollow'>http://www.bloodhoundsearch.com/Hounds/acquirepuppy.htm</a></p>
<p><a href='http://www.bloodhoundsearch.com/Hounds/trainingpuppy.htm' rel='nofollow'>http://www.bloodhoundsearch.com/Hounds/trainingpuppy.htm</a></p>
<p><a href='http://www.bloodhoundsearch.com/Hounds.help/htm' rel='nofollow'>http://www.bloodhoundsearch.com/Hounds.help/htm</a></p>
<p><a href='http://www.bloodhoundsearch.com/Hounds/faq.htm' rel='nofollow'>http://www.bloodhoundsearch.com/Hounds/faq.htm</a></p>
<p>FAQ&#8217;s would be designed to briefly answer the question with the LEARN MORE hyper link leading &#8220;back&#8221; to a precise page where the entire issue would be detailed. (Each page would have a link back to both the relevant Index Page and to the Home Page)
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: skipper</title>
		<link>http://www.ben300.com/TENPLAN/archives/74#comment-148</link>
		<pubDate>Mon, 16 Oct 2006 16:13:46 +0000</pubDate>
		<guid>http://www.ben300.com/TENPLAN/archives/74#comment-148</guid>
					<description>ABOUT USE OF AUTORESPONDERS AND PRECISE EMAIL ADDRESS
An easy example of the &quot;problem&quot; of listing FAQ's is that, I say, that each time a viewer was &quot;more information&quot;, they should be able to click on an email address, which opens their email client. The Bloodhound email address is ALWAYS an autoresponder address  --- so a generic answer is returned, but more detailed than is provided on the FAQ &quot;answer&quot;. That response instantly generates an alert that goes to one or more individuals responsible for appropriate follow up. All of this should go into a data bank for review by the leadership -- for obvious reasons.

It may be that the great bulk of the individual responses come from a single person. But the address for &quot;help&quot; would be tailored to the kind of &quot;help&quot; requested.

For example, in the FAQ's I created, I propose address' with &quot;warm&quot; connotation --
----
Who do I contact for more information?

For information about how to work for Bloodhound: &lt;job@bloodhoundsearch.com&gt;

For information about how to better train your Hound: &lt;houndtraining@bloodhoundsearch.com&gt;

For investor/financial information: &lt;equity@bloodhoundsearch.com&gt;

For advertising information write &lt;revenues@bloodhoundsearch.com&gt;

For partnering with us, please write &lt;partner@bloodhound.com&gt;</description>
		<content:encoded><![CDATA[<p>ABOUT USE OF AUTORESPONDERS AND PRECISE EMAIL ADDRESS<br />
An easy example of the &#8220;problem&#8221; of listing FAQ&#8217;s is that, I say, that each time a viewer was &#8220;more information&#8221;, they should be able to click on an email address, which opens their email client. The Bloodhound email address is ALWAYS an autoresponder address  &#8212; so a generic answer is returned, but more detailed than is provided on the FAQ &#8220;answer&#8221;. That response instantly generates an alert that goes to one or more individuals responsible for appropriate follow up. All of this should go into a data bank for review by the leadership &#8212; for obvious reasons.</p>
<p>It may be that the great bulk of the individual responses come from a single person. But the address for &#8220;help&#8221; would be tailored to the kind of &#8220;help&#8221; requested.</p>
<p>For example, in the FAQ&#8217;s I created, I propose address&#8217; with &#8220;warm&#8221; connotation &#8211;<br />
&#8212;-<br />
Who do I contact for more information?</p>
<p>For information about how to work for Bloodhound: <job@bloodhoundsearch.com></p>
<p>For information about how to better train your Hound: <houndtraining@bloodhoundsearch.com></p>
<p>For investor/financial information: <equity@bloodhoundsearch.com></p>
<p>For advertising information write <revenues@bloodhoundsearch.com></p>
<p>For partnering with us, please write<br />
<partner@bloodhound.com>
]]></content:encoded>
				</item>
</channel>
</rss>
