··· Chatra All books
§§ Table of Contents − − − − − − − − −
Ultimate Guide to Difficult
Conversations
1. Introduction 2. When you don’t know the answer 3. When you have to transfer a customer to someone else 4. When a customer requests a feature or product 5. When a customer asks you for a favor that you cannot do 6. When there’s something wrong with the delivered product 7. When you close the conversation 8. When a customer is angry 9. When a customer is unwilling to pay 10. When a crisis occurs 11. When you have a frequently complaining customer 12. When customers complain on social media 13. When you have legal issues 14. When you have to deliver bad news 15. When you have an abusive customer 16. When customers cross boundaries 17. When the customer speaks a different language 18. When a customer asks a vague question 19. When customers ask when something is going to be available 20. When you or your fellow agents made a mistake 21. When a customer wants to speak with a manager 22. When you can’t resolve the issue right away 23. When you need to let a customer know that it was their mistake 24. When a customer reaches you by mistake 25. When a customer asks how your product is different from others 26. When a customer is worried about how secure your service is 27. When a customer says that they forgot their password 28. When you want to point a customer to your documentation 29. When a customer violated your terms of service 30. When a customer is not tech-savvy 31. When a customer is right, but your policy is not 32. When a customer sounds like a bigot 33. You’ve got this!
5.

When a customer asks you
for a favor that you
cannot do

If you’ve worked in support for a while, maybe you’ve heard something like this: “Can’t you do it just this once?” Usually, it’s around a product feature that you don’t have or something that the customer perceives as being straightforward an easy to do. Usually, these things are not straightforward and easy to do, but even if they were, doing something for a customer that they can’t do for themselves is a surefire way to get more emails or chats back from that same customer in the future asking for your team to do it again.

While it can be difficult to say “no,” sometimes it’s important for the good of the whole. Take, for example, this story from Gregory at Help Scout:

I can give you a very candid story of when this really mattered to me: I was checking in to a very tiny beach hotel with a few of my friends, one of whom had a severe allergy to cats. I vividly remember watching this older couple at the desk while we were checking in, pleading with the employee to let their cat stay (the policy was “No Pets”).

[...]

If the front desk employee had given way to their request, he would have (unknowingly) made our group upset, trading one potentially unhappy customer for an even bigger problem.

I remember being really impressed with how he handled the situation:

Mr. and Mrs. ______, as much as I like fulfilling our customers’ requests, I’m afraid that the ‘No Pets’ policy we have in place is too important, as it deals with the safety and comfort of other customers. Can I perhaps call around for locations where your cat might be able to stay?

A stellar response to a pretty wacky request.

Greg’s example and the front desk employee’s response is so good because it really emphasizes the why behind the policy, rather than the no that is being given to the customer. Here’s how you can do that for yourself:

Hey there,

Thanks so much for emailing about this and for your great question. I can totally see how you would want me to make an exception here, as it seems like this is really important to your workflow. While I do see the value in it, we don’t currently have anything like that built into our system. I’m going to talk to our engineering team to see if this is something that we can offer in the future, but in the meantime, can I recommend [workaround xyz].

Let me know if that works for you, or if I might have missed the mark.

This can be used both for chat and for email. If sending via chat, this would likely be broken up into a few separate messages. If sending via email, it can be sent as-is with the workarounds specific to your company typed in.