Home > Murray Newlands, social media > Social Media Disaster, Trust and Winning Trust Back

Social Media Disaster, Trust and Winning Trust Back

by Murray on September 11, 2009

Social Media Disaster, Trust and Winning Trust Back

What would you do, ask the experts?


A few days ago I blogged about the Adrian Flux Insurance Group with whom I am having some challenges. Adrian Flux’s reaction was to comment on my blog using a FAKE name from a FAKE company they use within their social media out reach.

Unfortunately for Adrian Flux the “Whois” records go back to registration to their Marketing Manager David Wilson and the domain is registered to their company address.

whois Social Media Disaster, Trust and Winning Trust Back

I blogged it. This turned a customer dissatisfaction issue into a Social Media Disaster issue. It makes me more annoyed with their treatment. It shows up their shadowy practices. It reveals their un-trustworthy communication practices. The crazy thing is that I have already had direct contact with them and David Wilson, I am a customer. They know who I am. Now even if I was unjustified in my consumer complaint their shady method of response was disastrous.

Now my personal involvement aside, no really forget that. This is much more interesting. I am interested to know what you would do if this happened to you and how you would see to resolve it?

Do you, as a business, use social media monitoring tools to spot these things, such as Google Alerts, sm2, Radian6, Visible Technologies , Buzzlogic , TNS Cymfony, Nielsen , Trackur, Reputation Defender, Sentiment Metrics or PopularMedia?

Here are my suggestions for business owners:

1 Contact your customer with your real name as a real person, preferably on the phone.
2 Try to resolve the issue.
3 Try to turn the situation around to make the customer an advocate of your company.

What would you do to avoid a social media disaster such as this?

Popularity: 9%

Related Posts:

{ 16 trackbacks }

MurrayNewlands (Murray Newlands)
September 11, 2009 at 12:58 pm
MurrayNewlands (Murray Newlands)
September 11, 2009 at 12:59 pm
MurrayNewlands (Murray Newlands)
September 11, 2009 at 1:31 pm
Dunkndisorderly (Duncan Birch)
September 11, 2009 at 1:32 pm
killer_bunnie (claire stokoe)
September 11, 2009 at 1:33 pm
MLDina (MLDina)
September 11, 2009 at 2:33 pm
MurrayNewlands (Murray Newlands)
September 11, 2009 at 2:34 pm
MurrayNewlands (Murray Newlands)
September 11, 2009 at 3:18 pm
OysteinLund (Oystein Lund)
September 11, 2009 at 3:27 pm
MurrayNewlands (Murray Newlands)
September 11, 2009 at 3:31 pm
MurrayNewlands (Murray Newlands)
September 11, 2009 at 3:32 pm
HeatherinBC (HeatherinBC)
September 11, 2009 at 3:33 pm
pwebbiz (Michael)
September 11, 2009 at 3:34 pm
MurrayNewlands (Murray Newlands)
September 11, 2009 at 3:35 pm
sei_ryu (Ken Brucker)
September 11, 2009 at 5:25 pm
Great posts on Murray Newlands from 7th 7th September – 13th September Sep 2009 | Murray Newlands
September 19, 2009 at 5:56 pm

{ 3 comments… read them below or add one }

1 Lauren Vargas September 11, 2009 at 5:22 pm

Good example of how tools to identify conversations about brand do not always result in the best engagement. One can only automate response to a degree. The human element, especially in customer service, is essential. Thank you for including us in your list of social media monitoring tools.

Lauren Vargas
Community Manager at Radian6
@VargasL

Reply

2 admin September 11, 2009 at 5:28 pm

Lauren Thank you for your comment. I agree the human element, especially in customer service, is essential. This is precisely why you were in our list of social media monitoring tools. http://www.murraynewlands.com/index.php/2009/07/top-10-social-media-monitoring-tools-and-social-media-monitoring-tools-review/

Lauren what would you recommend a Radian6
to do in their place?

Reply

3 admin September 11, 2009 at 5:32 pm

Ken If you have already had correspondence why hide? Seems illegitimate, to me and others who have responded by RT ing.

Reply

Leave a Comment

CommentLuv Enabled

Previous post:

Next post: