What’s this thing with technical support mails? And why do most of us end up making such a great mess of them?
They’re always too long, boring or just downright confusing.
As someone in tech support, I’ve had my fair share of support conversations ranging from terrible to occasionally hilarious. And while I’m sure everyone has, at some point or the other, quibbled over phrasing so that they don’t sound too apologetic or aggressive, it still doesn’t account for some of the mind-boggling ways in which some people mess up.
So here is a curated list of things you should remember when you’re composing that great support response –
1. Examine the problem from every point of view
I know, I know, this is about as obvious as it gets. But you’d be surprised at the number of times customers call tech support and the guys at the other end just refuse to listen.
I’ve seen reps who just assume that customers know as much about their products/space as they do. And when they build on this assumption, all hell breaks loose. The easiest way to get it right is by reading over the complaint, over and over again. Three to four iterations later, you’ll get a clear picture of the situation. Try it and you’ll be able to see yourself how often your initial assumptions can end up being wrong.
2. Try the solution out yourself
The next time you are typing a particularly ambiguous reply, don’t validate the solution because you tried it out three months ago or someone on your developer team explained it to you. Do it yourself, see the result with your own eyes and confirm that it’s working before you hit that send button. Even the slightest missteps can, after all, turn a satisfied customer into an irate one.
3. Put yourself in their shoes
Every customer you speak to has a genuine problem. To them, the littlest of glitches could mean a critical issue that can cause bottlenecks. It is not okay for you to take them lightly just because the fix is already on the way.
So try to see the world from their eyes. Put your two-year-old canned responses to rest and get personal with them. Understand what they are going through and try to make your apologies as personal as possible. Make them a promise, that you are personally looking into the issue, and follow through until everything’s okay.
4. Check for grammatical errors
While it’s impossible for you to make sure that every email is perfect before you shoot ’em out, especially when you have dozens queuing up for your attention every other second, you need to at least try. Make it a point to go through every reply at least once before sending it. If you don’t trust yourself to spot all the errors, trust in a tool like MS Word (the Spellcheck in MS Word can be quite the Grammar Nazi) or Grammarly to spot them for you. And for your customers’ sake, stop switching between browser tabs when answering a ticket.
5. Think twice before saying no
There’s not a user in the world who, if asked what features they’d like to see added to their product, says that the product is absolutely perfect and there is nothing you can do to improve it. But as much as you’d like to oblige them all, you can’t put every request in your roadmap. All you can do is understand the client’s problem to the best of your ability and suggest workarounds based on what you know.
And even if you cannot give the feature to them, make sure you never say a hard “no”. Check with your project manager if something’s being planned, and keep them in the loop. In the meantime, they’ll appreciate the small hack.
If you feel like I’ve missed out on a very obvious tip, feel free to mention it in the comments down below.