··· 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!
29.

When a customer violated
your terms of service

There are all types of people in the world, and so it should stand to reason that you can’t expect every single one of them to use your service or product in the “right” or “proper” way all the time. Sometimes people will violate your terms of service in obvious or egregious ways. Other times, it will be an accident and they won’t even know they are doing it. Either way, though, if it comes to the attention of your company, someone will have to handle it, and normally that someone will be the support team. So, what’s the best way to do it?

Being bureaucratic and explaining your terms of service, rather than accusing a customer of knowing and making the choice to break them is always going to be a better route. Rather than assigning blame to anyone, instead try to find out what the customer was looking to accomplish and how you can help them do that in a way that falls within your terms. Here’s an example: at one company where I worked, we would occasionally have people that would use the API to create hundreds of items within our product all at once.

This kind of hammering at the API would actually slow the whole infrastructure down as it tried to handle the bandwidth. There were, basically, only two things that could be happening when this occurred: first, someone could have made an incorrect API call and not  realize what they were doing or, second, someone is trying to spam someone by completely incapacitating their account. One of our tenets of good support was “assume positive intent,” and that was no different with things like this. Here’s how we’d answer, so maybe you can take it and run with it:

Hey there,

My name’s [blank] and I do [blank] here at [company]. I wanted to reach out because I noticed that you had some unusually high activity via the API which actually exceeds our usage guidelines. Could you share a bit more information with me about what you’re trying to accomplish? I’m wondering if I might be able to help you find a way to do what you’re looking to do while still staying within the boundaries of our terms of service.

If I don’t hear back from you or the activity doesn’t stop within the next 24 hours, I will, unfortunately, have to take action on your account by creating a temporary freeze on your API keys. That will mean that you will not be able to do anything via the API or programmatically (including using Zapier) until I remove the freeze.

Hopefully we can chat soon! Thanks!

While it might be slightly different for you and whatever the main issues with your product are, the important pieces are:

  • Ask for the intention behind why they are doing it.
  • Ask them why they are doing it so that you can offer a workaround
  • Let them know what action you will take in the event that they don’t respond.

While it may seem like bullying when receiving an email that tells them bad news or that they’ve done something wrong many people won’t respond. That gives them an incentive to explain things so that you can get a dialogue started.