<?xml version='1.0' encoding='utf-8' ?>

<rss version='2.0' xmlns:lj='http://www.livejournal.org/rss/lj/1.0/'>
<channel>
  <title>removercomplain</title>
  <link>http://www.iziblog.net/users/removercomplain/</link>
  <description>removercomplain - IziBlog</description>
  <managingEditor>rmvr_complaint@yahoo.com</managingEditor>
  <lastBuildDate>Fri, 20 Jul 2007 05:28:10 GMT</lastBuildDate>
  <generator>LiveJournal / IziBlog</generator>
  <lj:journal>removercomplain</lj:journal>
  <lj:journaltype>personal</lj:journaltype>
<item>
  <guid isPermaLink='true'>http://www.iziblog.net/users/removercomplain/321.html</guid>
  <pubDate>Fri, 20 Jul 2007 05:28:10 GMT</pubDate>
  <title>Branding Guru - Brand Identity Guru - complaintremover</title>
  <author>rmvr_complaint@yahoo.com</author>  <link>http://www.iziblog.net/users/removercomplain/321.html</link>
  <description>Branding Today&lt;br /&gt;&lt;br /&gt;Have you ever had a good brand experience? How about a bad brand experience? Is there a difference in your mind? How many people do you tell about a positive brand experience? How about for a poor brand experience?&lt;br /&gt;&lt;br /&gt;One poor brand experience will not destroy a firm. One poor brand experience per day, however, can ruin a company in the long run for sure. It&apos;s really easy math. If one person receives a poor experience with a brand, they might tell 10 people. At 365 days a year that&apos;s over 4000 people per year. Yikes! Not good at all.&lt;br /&gt;&lt;br /&gt;So, how can your employees protect your brand everyday?&lt;br /&gt;&lt;br /&gt;It all depends on delivering your internal brand and training. Not only do you have to train employees on customer service issues but also they must know how to deal with a customer that is upset or has a problem.&lt;br /&gt;&lt;br /&gt;Let me give you an example. I purchased some artwork on a Carnival Cruise. Upon purchase from the vendor (not from Carnival Cruise itself) I requested custom frames. The vendor, Park West took my order and informed me that it would be 6-8 weeks for delivery.&lt;br /&gt;&lt;br /&gt;10 weeks later I called Park West. They told me it shipped. I received my artwork 3 weeks late. I was so excited and I ripped the packaging away only to find they did not put on the custom frames. I waited 10 weeks for nothing.&lt;br /&gt;&lt;br /&gt;I called Park West immediately. Guess what? I was going to have to wait another 6-8 weeks for the correct replacement. I asked for a refund and a pick up of the incorrect artwork. They denied me and said it was a final sale.&lt;br /&gt;&lt;br /&gt;I called my credit card company. Guess what? The charge went through my Carnival Cruise account. I called them. Guess what? They would not help me, as it&apos;s a third party vendor. This is a third party vendor that Carnival Cruise has partnered with.&lt;br /&gt;&lt;br /&gt;Did I mention that this was my 19th Carnival Cruise?&lt;br /&gt;&lt;br /&gt;Long story short I had to pay to ship my artwork back and my credit card company took care of me.&lt;br /&gt;&lt;br /&gt;I will never take another Carnival Cruise again.&lt;br /&gt;&lt;br /&gt;How could Carnival save itself from losing me as a customer? It&apos;s really quite simple. Ultimately because the charge went through Carnival they needed to take responsibility. They should have said you&apos;re a valued guest and we will credit you immediately. At that point I&apos;m thinking wow, Carnival is even better than I thought. But instead I&apos;m writing this article and never ever going on another cruise with them.&lt;br /&gt;&lt;br /&gt;Carnival could have saved the brand. If they had gone the extra mile to put themselves in my shoes, I would have had a positive brand experience. I would have used Carnival again, and I would have probably told everyone I know how great there service was. Developing a proper internal brand strategy and training is the key to delivering a positive brand experience. Don&apos;t make stupid mistakes with your brand.</description>
  <category>complaintremover</category>
  <lj:security>public</lj:security>
</item>
</channel>
</rss>
