What to do when your manager doesn't accept your vendor's answer about a bug?

Question

Basically, my company uses Software A, which provides a developing framework and a lot of generic code templates. My company purchases this software and uses it as a platform, making customizations where needed. Recently, someone approached us with a defect wherein buttons weren't displaying correctly (relatively minor). The boss told me to contact the software company to submit a defect report, to which they essentially replied "We fixed it in the next release."

Of course, we can't just drop everything to update the software; it's a process that takes months. My boss wanted me to continue working with this customer service rep until a 'proper' solution was found, despite being told multiple times that there is no other workaround.

Essentially, my boss isn't happy with the answer, so he wants me to bully this customer service rep until the answer changes to something 'acceptable' (which it won't). I've been polite in my dealings with the rep, and my boss has now told me to use 'any means necessary' (AKA yelling/belittling the rep) to get a solution.

How can I stand up to my boss in this matter and tell him that the answer is not going to change, and that I outright refuse to be intentionally rude to a customer service rep?

Answer 1

So, you're stuck between a rock and a hard place. Your boss refuses to hear the word "no," and you can't get any sort of "yes" answer.

You need to remove yourself as the middleman from this situation.

The next time you speak with the service rep, take your boss with you to the meeting (or let him talk with the rep by himself), and let him do his own yelling to the rep. It's very likely that your boss will still not get what he wants, but at least he'll realize that you can't do anything about this (at least not immediately), and that he needs to probably focus more on upgrading the company's system or finding a new vendor for Software A.

Answer 2

This answer combines "escalate" and "stop being the middleman".

The customer service rep is unlikely to be able to do anything further. A decision has already been made to fix in the next release, so service managers are also unlikely to be able to help.

Your company purchases Software A. Someone in your company, possibly your immediate boss, possibly someone else, has a customer-seller relationship with a Software A sales person. That is a higher leverage relationship than your user-support relationship. Call that person "B".

If your boss is B, suggest he should use his contacts with Software A sales to escalate the issue.

If your boss is not B, suggest bringing the issue to B's attention. B will have to decide whether the issue is serious enough to justify further action. If it is, B should contact the Software A sales organization, and express dissatisfaction with the bug and the decision to fix it only in the next release. Your company may or may not be a sufficiently important customer for the Software A sales organization to decide to raise the issue with the development organization.

This path may even work. It it does not work, no amount of you yelling at a support person will work. Regardless of whether it works, it gets you and the first line support person out of the line of fire. It forces your manager to either get a reality check from B, or if he is B to think through the significance of the issue relative to the overall relationship.

Answer 3

The same way your company won't drop everything to install a new version, the Software A vendor won't take the time to issue a specific patch just to solve your problem in the current version, even more so if there is a fix on a new version. It is usually very costly for companies to support older versions and they try their best to stay away from it.

You can yell to this customer rep until you are blue in the face and this won't change anything. You may want to escalate to the rep's boss, and document everything that you did as CYA but this basically has no solution.

Answer 4

I've been at both sides of the phone line, so I may be of some use.

First of all, don't yell, insult, threat or abuse a customer support representative. I repeat: don't do it. First level customer support rarely employs developers or people with IT studies. The rep in question may not fully understand what you're talking about, and even if he/she does, it's out of his/her scope.

What you can do is document everything, to prove that both you and support people are doing all they can. How? Like this.

• Support usually manages customer calls with ticket systems, so ask for its number. If you call again, mention it, and ask to be updated. This way its easier to track the request history across the different support levels. If the software company lets you access to it via web or a proprietary app, you can show your manager.

• If there is no ticket system available to customers, make your own. Write down dates, names and a small summary of the conversation. In some places first level reps don't use their real name to avoid client harassment, but it shouldn't be a problem in this case. For example

  2015-04-21: Jane Doe. Explained problem. Opened ticket number 12346584. Promised to escalate to 2nd level.

  2015-04-30: John Smith. Asked for updated. He says 2nd lvl hasn't read it yet. Updated ticket to reflect my call.

  2015-05-05: Alice Jones, 2nd lvl. The bug is detected and fixed. Will show up in the next release.

  Independently of the way you used, show it to your manager when he requests the status.

Lastly, if your manager doesn't believe you, even after you show him either the ticket or what you wrote down, suggest him to call again and put the phone in speaker so that he can listen to the whole conversation. If you communicate through email, suggest to CC or CCO him.

If after all this he still does not believe you, or demands something impossible for you or the software company, its him who needs to understand that there are things that cannot be fixed in the blink of an eye. Do not harrass or be rude to the support reps, even if he orders to do it, because if it reaches upper management ears you could be the one who has to pay for it.

Hope this helps.

Answer 5

There are a few matters here that potentially intersect, and you don't necessarily understand all of them.

You need to understand why your boss insists on a different answer. Is there some larger pressure - such as a major customer threatening to take their business elsewhere - that makes waiting until a future release unacceptable?

Has your boss actually told you to bully the rep, or simply asked you to find a workable solution more quickly than you have found to date? If so, have you considered other options, such as whether your boss is willing to pay for a quicker solution, and or asked the sales rep to provide a quote to deliver a quicker fix than waiting for the next release?

Asking for a quote for quicker interim delivery is one way to get a supplier to seriously consider what it takes to deliver a usable fix or give information about a workaround before the next release. They might still refuse, but they might also surprise you. You won't know until you ask.

Is your boss willing to escalate the matter with his counterparts in the supplier? If so, can you work with the sales rep to help that happen effectively?

You see, it strikes me that the only option you have pursued is asking the sales rep when they can deliver, and accepted the first answer provided. Unless you dig further, you won't know whether other options are available - particularly if your boss is willing to permit you to PAY for a quicker solution or to support you in escalating the problem. And a sales rep who is seriously asked for a quote for a quicker solution may well elect to escalate the matter internally within his organisation.

Addressing questions like the above mean you get an opportunity to test how committed your boss is to a quick solution and an opportunity to find what your supplier is capable of, or willing to do, in the right circumstances.

If you have exhausted these sorts of possibilities, and your boss is actually insisting that you bully the sales rep without any reasonable explanation (i.e. why?) or support (e.g. being willing to pay more for the faster fix) then other replies about "get out from being the middleman" apply.

Answer 6

If your boss wants "something" done and it's obvious the customer service rep is completely unable to do anything ask the person on the other end of the phone to escalate to their manager. I've had at least a dozen times where my supervisor gave the same answer as me but because it came from somebody in a position of power it held more weight. Your boss may accept reason from another manager.

Don't yell at or belittle the CSR, this does not move towards the goal of the bug fix or the goal of placating your boss.

Answer 7

So we have a situation where the customer wants an update but the vendor doesn't want to do it, and asking politely hasn't worked.

Yelling at tier 1 won't accomplish anything. You need to convince the company that they want to do it. How you do that depends on how much contract muscle you have with them.

If your service contract entitles you to this kind of service, then wave it at them. Begin with "This call is being recorded." Yes, they are likely recording their end but this puts the agent on notice that you have a copy too. Get someone to formally decline to make the change, then tell them your company's lawyers will be in touch and they might want to get the going-to-court suit cleaned. I once made a government agency go away, permanently, with this technique. Send recordings of the calls to your boss.

If you do not have any contract leverage, you have to make them want to push out an update. Since your boss said "any means necessary", get everyone else in the company to call the vendor's support desk and complain about the bug. Then call again. This will involve a lot of waiting on hold but that's what speaker phones are for. And don't worry about putting their agent on hold while you take your own calls. Remember who's paying whom here, and remind the vendor of that as well. Frequently, as they have apparently forgotten. The winner here will be the one with the greater phone resources and/or patience. Make sure everyone tracks their time and send a frequent report to your boss.

I have generally found that being rather firm with T1 support, followed by "I would be happy to take this up with your supervisor / T2" results in a quick transfer to the next level up, but I do not accept voicemail. Their boss is paid more to handle these things, so they can handle it.

If the vendor's office is in the same city, pay them a visit (remember, Boss said "any means necessary").

The next step, open warfare, depends heavily on which country you and the vendor are in. Get your boss to approve a budget and schedule in advance.

Answer 8

You boss is not accepting "It can not be done now," because you can not explain why it can not be done now. Partly because you have stated that they already have a fix for the issue out in the next release. So your boss knows it can be fixed.

So your next step is try to get your vendor to connect their developer who fixed the bug on their end to explain what it would take to fix the bug in the current system. It could be a simple fix that they can send you the details of. Or it could require complex changes in the system. It is funny how sometimes seemingly simple things in a system can be incredibly complicated to change.

The best way to get this information is not to bully but to convince the rep that you are on the same side. Acknowledge that the problem is small but you have an executive that has decided that this problem is a priority for you. Then tell the rep that you really want to work together with them to come to a resolution on this issue. It may take some time but you should be able to come to an understanding as to what it will take to solve the issue.

If you feel the effort is still much greater than than the reward explain what it will take to your boss and see if he still wants it completed. If he does then you implement those changes. If the fixes are easy just fix them and report the success back to your boss, you will want to avoid telling your boss that in the end the solution was simple, it will not look good for you.

Another option would be to explain the problem to your Dev team and offer a team lunch to figure out a short term fix for the issue and the dev who figures it out gets to be king of the devs for a day. Small rewards like these are the real world version of quests. It bumps up moral and gets the problem solved. "What ever it takes"

Answer 9

I've been on the other side of the fence often enough, as the software developer.

What works is to get your boss (it helps if he's the owner of your company and if your contract with the company is a big enough fish in the bucket) to go straight to the owner of the software development company.

And I mean owner not, some mid-level manager.

This is a way that minor things can get solved pretty fast.....if you don't do it too often.

Answer 10

It is a relative minor defect where the buttons just don't display properly. That would be characterized as a non critical bug. I seriously doubt any software company would go back and patch a prior release for a non critical bug.

Who says you need to deal with an unreasonable boss in a reasonable manner?

Putting the boss in the middle is not going to fix anything. Yelling at a rep is not going to get them to patch. It will only serve to damage the relation ship with the vendor.

Use 'any means necessary' (AKA yelling/belittling the rep). In a slightly elevated voice to the support person say "Really so you have no authority to fix my problem". Technically you have yelled and belittled but have done no real harm.

Boss I did everything I can. "I yelled and I belittled. I thought he/she was going to cry. I personally don't have the clout to get them to patch a prior release. They have stated it is fixed in the current release. At this point we may need to legal involved and review the contact to see if we can force them to patch a prior release."