<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>IvyCat Website Services &#187; Articles</title>
	<atom:link href="http://www.ivycat.com/category/articles/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ivycat.com</link>
	<description>Web Hosting, Design &#38; Development</description>
	<lastBuildDate>Fri, 14 May 2010 22:49:57 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>Use Business E-mail for Business</title>
		<link>http://www.ivycat.com/2009/07/use-business-e-mail-for-business/</link>
		<comments>http://www.ivycat.com/2009/07/use-business-e-mail-for-business/#comments</comments>
		<pubDate>Thu, 16 Jul 2009 20:41:38 +0000</pubDate>
		<dc:creator>Eric</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[email]]></category>

		<guid isPermaLink="false">http://www.ivycat.com/cms/?p=50</guid>
		<description><![CDATA[If you're in business and have a website, it's in your best interest to use an email address with your domain in it.]]></description>
			<content:encoded><![CDATA[<p><strong>If you&#8217;re in business and have a website, it&#8217;s in your best interest to use an email address with your domain in it.</strong></p>
<p>I&#8217;m often surprised at the number of business people who conduct business regularly using free email accounts from Google, Yahoo, or MSN/Hotmail.  If you have a website, it just makes sense to conduct business using the domain of your website.</p>
<p>So, if your domain is <em>mydomain.com</em>, make sure to setup email addresses for each member of your organization, <em>jane@mydomain.com</em>, <em>john@mydomain.com</em>.</p>
<p><strong>There are several good reasons for this:</strong></p>
<ol>
<li><strong>Branding</strong> &#8211; when people see your domain name, they associate it with a web site.  Using an email address from your own domain reinforces your company&#8217;s branding</li>
<li><strong>Usability</strong> &#8211; it&#8217;s much easier to remember an email address tied to a company&#8217;s domain.  My email address is eric@ivycat.com.  If people can remember my name and this domain, it easier</li>
<li><strong>Control</strong> &#8211; call me greedy, but I like having control over the email domain.  This way, I can add add new accounts, forwarders, setup filters, etc.</li>
</ol>
<p>Most hosting accounts come with a certain number of email accounts and forwarders and they&#8217;re not hard to setup.  If you need help, your web host or IT person should be able to help.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ivycat.com/2009/07/use-business-e-mail-for-business/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Using Email Forwarders</title>
		<link>http://www.ivycat.com/2008/06/using-email-forwarders/</link>
		<comments>http://www.ivycat.com/2008/06/using-email-forwarders/#comments</comments>
		<pubDate>Tue, 03 Jun 2008 22:25:27 +0000</pubDate>
		<dc:creator>Eric</dc:creator>
				<category><![CDATA[Articles]]></category>
		<category><![CDATA[email]]></category>
		<category><![CDATA[website]]></category>

		<guid isPermaLink="false">http://www.ivycat.com/cms/?p=1</guid>
		<description><![CDATA[Creative ways to use e-mail forwarders to provide more personalized customer service, increase flexibility, and track incoming messages.]]></description>
			<content:encoded><![CDATA[<p><strong>Email forwarders offer some great opportunities for better serving your customers.</strong></p>
<p>Email forwarders (aka. <em>aliases</em>) are not actual email accounts, rather they&#8217;re email addresses that simply redirect email to another account.  No mail is stored in the forwarder/alias itself; the mail is stored in the account(s) to which the mail is forwarded.</p>
<p>Small businesses often want to appear larger than they are, while keeping very personalized customer contact.  One strategy is to setup forwarders that you use on your site or marketing materials that are redirected to an individual or a group.</p>
<p>Your hosting account should allow you to setup generic email addresses like info@ and sales@ and have them redirected to the individual(s) within the company responsible for these communications.</p>
<h2>Here are a few ways email forwarders can benefit you:</h2>
<ol>
<li><strong>Personal Service</strong> &#8211; Since the messages are forwarded to actual email accounts, responses will come from the individual, rather than the forwarder.  For example, if you email sales@ivycat.com, the email is forwarded to my account, so when I reply, you get an email from Eric, an individual, rather than a faceless generic company address.</li>
<li><strong>Flexibility</strong> &#8211; if an employee leaves, you can easily redirect the forwarder to a different address, so you don&#8217;t have to check another account.</li>
<li><strong>Marketing</strong> &#8211; since forwarders are cheap (usually free) you can setup different email address for individual marketing campaigns so you can better track return on investment.</li>
<li><strong>Appear Larger</strong> &#8211; while we all want to provide personal service, sometimes its helpful to appear larger than you actually are</li>
<li><strong>Individual anonymity</strong> &#8211; Using forwarders allows you to keep your individual employee email addresses hidden.</li>
</ol>
<p>So, consider your organization&#8217;s email setup and see if email forwarders might help you deal with mail more efficiently.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ivycat.com/2008/06/using-email-forwarders/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
