Service Can and Should be Proactive – Social or Not
If there is data available, or simple process improvement that could easily elevate my service experience, as a consumer, why are companies not doing it? Telecommunications carriers are such easy targets that I hesitated to write this post. I can offer offer simple advice, as a practitioner, from both a process and technical perspective, so maybe, just may they will listen – and readers can learn as well. It is not that hard, it is just about putting the right information in front of the right person at the right time. Interestingly, this is about two of the biggest providers in the US and both happened during a one week period.
The Response to an Issue can be more Important than the Issue Itself
I am a technologist, often an early adopter and also a pragmatist; Shtuff happens, I get it. It could be weather, it could be solar flares, it might even be a software glitch. What I have little patience for is what I believe to be ultimately quite simple process fixes, which can easily be implemented but for some reason, have not.
- AT&T had an outage in Vermont last week. It was early in the day, 7:30 am to around 9:30am. Local technical and socially connected posted on Twitter and tried to get AT&Ts attention. The response from AT&T was slow, almost non-existent on the social channels. No recognition of the problem, until after it was fixed. The customer service team on Twitter did work through their queue from the night before (easy to spot), and did not send any broadcast messages. Some discovered that if you switched off 3G, Edge provided service for phone only. AT&T did not make that statement, a user did. AT&T did not even RT that post. Response grade C-
- My 16yo had an issue with his HTC phone, so we did a warranty replacement. Many steps completed without any issue – including a whole 10 minutes in a Verizon store, well done. New phone arrived, activation easy, still good. The front of the little instruction packet had a number (long 10 or 15 digit number) and a note under it with a URL to FedEx for tracking. So, my 16yo took the old phone to FedEx with the enclosed label; only to find out it was a USPS label – odd, but not a huge problem. Brings the box to USPS and off it goes. One week later, Verizon calls and wants to bill us $500 for the “yet-to-be” returned phone. We find the little packet with the tracking number, take a look at the website and tell the agent (who also checks). We also remind the agent that we have insurance on the phone and if it dropped in a lake, we would still get a new phone, no questions. Why was the call ever made (there are two reasons why the call should not have been made)? Response grade B, but the last impression is what sticks.
My simple advice:
- Customer Service can be Proactive – It is possible, it can show you care and save inbound calls
- Engage when it counts, walk the walk – Recognize an issue, help customers through an incident and be human, the Social part of Service is not just about PR
- Put data where it can be most useful, turn data into information – If you have information which can prevent a call from happening, use it.
I suppose it is possible that because I live and breath this sort of thing and know what our software can do I have a different take on things, but really is it that hard?
- There is a Big Difference Between Can’t and Won’t
- Stop Thinking in Two Dimensions
- No Beginning, No Middle and No End
- Rethinking the Customer Journey
- The Simplest Thing I Ever Had to Write
- Context Integration, the Future of System to System Interactions
- The Evolution of Customer Community
- The Fine Line Between Personalization and Creepy
- Experience Innovation
- Maybe We are Using the Wrong Words to Describe Collaboration
- It is awesome having friends in the many corners of the World! @prem_k @PaulSweeney @wimrampen @MarkTamis @mikeboysen #insomnia :-) 7 hours ago
- @prem_k Let's just call it a bot and go back to circa 2001 :-) 8 hours ago
- .@Uber_Support The unskilled driver and danger caused angst and a lost 45 minutes of time. #custserv 8 hours ago
- .@Uber_Support I did and it took 3 interactions to convince @Uber to go back to the original quote when the whole ride should be comped 8 hours ago
- @prem_k Funny how a Chatbot can be run by pure boolean logic 8 hours ago
- An error has occurred; the feed is probably down. Try again later.