<?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>47 Project &#187; liliana dumitru-steffens</title>
	<atom:link href="http://www.47project.com/tag/liliana-dumitru-steffens/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.47project.com</link>
	<description>Rich Harris &#62; Father of 3, Marketing Guy, Musician, Artist, Photographer, Web Ninja, Sarcasm Expert</description>
	<lastBuildDate>Wed, 14 Jul 2010 17:50:18 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
		<item>
		<title>Social Media: Stand By Your PR Crisis</title>
		<link>http://www.47project.com/2010/02/01/social-media-stand-by-your-pr-crisis/</link>
		<comments>http://www.47project.com/2010/02/01/social-media-stand-by-your-pr-crisis/#comments</comments>
		<pubDate>Mon, 01 Feb 2010 18:25:53 +0000</pubDate>
		<dc:creator>Rich Harris</dc:creator>
				<category><![CDATA[Business]]></category>
		<category><![CDATA[Commentary]]></category>
		<category><![CDATA[Social Media]]></category>
		<category><![CDATA[47]]></category>
		<category><![CDATA[b of a]]></category>
		<category><![CDATA[bank of america]]></category>
		<category><![CDATA[everythingPR]]></category>
		<category><![CDATA[facebook]]></category>
		<category><![CDATA[huffington post]]></category>
		<category><![CDATA[liliana dumitru-steffens]]></category>
		<category><![CDATA[pr crisis]]></category>
		<category><![CDATA[rich harris]]></category>
		<category><![CDATA[support]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[website down]]></category>

		<guid isPermaLink="false">http://www.47project.com/?p=888</guid>
		<description><![CDATA[Bank of America is in the trenches right now. Like most B of A customers last week, I could not access my account info while attempting to login from www or via mobile device. Of course I jumped on Twitter to follow them for status. As I watched the stream on Twitter unravel, watching everyone&#8217;s [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.47project.com/wp-content/uploads/2010/02/bank_of_america.jpg"><img class="alignright size-medium wp-image-895" style="border: 0pt none; margin: 10px;" title="bank_of_america" src="http://www.47project.com/wp-content/uploads/2010/02/bank_of_america-300x140.jpg" alt="" width="300" height="140" /></a>Bank of America is in the trenches right now. Like most B of A customers last week, I could not access my account info while attempting to login from <strong><em>www</em></strong> or via mobile device. Of course I jumped on Twitter to follow them for status. As I watched the stream on Twitter unravel, watching everyone&#8217;s opinions and complaints about B of A fly by on TweetDeck, I was checking out what <a title="Posts by Liliana Dumitru-Steffens" href="http://www.pamil-visions.net/author/liliana/">Liliana Dumitru-Steffens</a> saw before writing her article &#8220;<a href="http://www.pamil-visions.net/bank-of-america-website-down/211255/" target="_blank">Online PR Crisis: Bank of America Website Down, no Explanation from the Owner</a>&#8220;. At first my thoughts were, &#8220;cool, they&#8217;re on Twitter, they&#8217;re gonna let us know what&#8217;s up.&#8221; Instead what I saw was the online bludgeoning of the folks who were running the Twitter accounts on behalf of B of A by all the customers, but Bank of America was not effectively backing them process-wise. While the customers were snapping at them right and left, shooting first and asking questions later, I realized a couple things. First, I could tell that their Twitter reps were genuinely wanting to help. The problem was the second issue -  they were probably to some extent not getting the info they needed from their own employer to respond accordingly with some details that would&#8217;ve at least given the B of A customers a little more patience during the crisis.</p>
<h3>A Couple Tips for a PR Crisis</h3>
<ol>
<li>Before choosing Twitter as an official and legitimate support channel for your company, make sure your PR/Communications team are ready to support your Twitter reps with a process for delivering details/status on issues expeditiously so that you don&#8217;t hang your social media reps out to dry for your customers to devour and lambaste them when there is a crisis. Sending your soldiers out to battle with no weapons or gear is bad.</li>
<li>Always stay in front of the PR crisis publicly, with a sense of urgency, and mean it. When a bad PR hit goes down for your company or client on Twitter/Facebook, especially when there are customers being effected (and in this case, they&#8217;re hooked in financially which makes them extra edgy), this is your moment to shine and wave the flag of corporate transparency to put them at ease. Customers know that websites have issues, that they get hacked, that they crash or become unavailable. Welcome to technology! However, if they can&#8217;t clearly see that you are coordinated with your internal teams with the latest updates, rolling out practical sets of expectations every half hour or so with the latest news, they will hate you quickly and easily. Let them know you are fighting for their right to have a good customer experience.</li>
</ol>
<p>Also check out the Huffington Post article: &#8220;<a href="http://www.huffingtonpost.com/2010/01/29/bank-of-america-website-d_n_442486.html" target="_blank">Bank Of America Website DOWN: 2010 Outage Affects Online Banking</a>&#8220;. There are some good nuggets in there as well.</p>
<p>Onward.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.47project.com/2010/02/01/social-media-stand-by-your-pr-crisis/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>
