Slashdot Mirror
Dealing w/ Unsatisfied Customers?
MoOsEb0y wonders: "At the company I work at, we have set up a series of SLAs giving a list of things they expect our products to do, that we promise we will deliver. In my particular situation, I have a customer who claims that the product we delivered them was slow and unresponsive. However, when we tested it to try and determine what was wrong, we didn't find anything wrong with it. How do you deal with a customer who is bent on assuming that you are incompetent, and that he or she could never have unreasonable expectations?"
Some customers just aren't worth having. It's a tough choice to make sometimes, but every now and then you've got to drop a customer.
You Can't. You Just Can't. Let a higher-up manager deal with them. That's what they get paid for.
- You're not paranoid, they really are after you.
You can't always assume the customer is always right... sometimes they're just wrong and you just have to let them know. It's all you can do. :/
-uso.
What you hear in the ear, preach from the rooftop Matthew 10.27b
Due diligence is important though so make sure you actually do try to find their problems. If nothing's found, humor them and say you've looked into the problem. Try to get their system specs, environment settings, etc, etc, ad nauseum and they'll learn they better be able to provide a lot of detials next time they decide to report a complaint on a whim if that's the case.
why run from Vincenzo?
I've been in that situation, and it's not fun.
If you can't track down a cause for the problem, the best you can do is explain to them the limitations of the product and product development, etc. If they are saying the product is unresponsive when it's just being a little slow, then that's not going to work. If it really becomes a big problem, you may need to refer them to the engineering team.
Just hope the engineer doesn't say "I'm a people person, damnit!"
Ask them to give you a demonstration of the product and show you what's wrong with it, then work with them.
echo YOUR_OPINION >
Let me guess, is this the customer at work testing your so-called "incompetent" product?
'Tell them to fuck off'
Also, refer to:
http://www.somethingawful.com/index.php?a=3853
and
http://www.somethingawful.com/index.php?a=3885
If the customer is important enough then try to see the problems from their perspective; give them the benefit of the doubt. Assign a customer-oriented, technical person to be onsite to see the "problem" first-hand. See if it really is a problem (bug or implementation) or just an expectation problem. The absolute worst thing to do is dismiss it outright.
If it is too much trouble for your organization, give your customer the names of some competing product or another product that will fit the task and send them on their way.
Hey
I don't mean to flame, but I have been in the opposite position. I have had a laptop where it will fail something like Memtest, I will send it in and the technicians will say I am not a tech and that there is nothing wrong according to their certified tools. I have had hard drive failuers that techs could not detect and I have had broken keyboard where the one letter (q I believe) only worked if you pushed really hard on it and the technician has said it was normal.
Since all of that I have moved into a tech job. I have had computers come to me after they have brought them to other dealers and I have found things wrong. Though I am sure you are good at what you do I recommend you check everything. Sometimes the check list does not cover everything. I know that everytime I sent my laptop into Toshiba Tech with a broken DVD drive it was certainly never tested as it always came back broken until I gave up and replaced it myself.
Having said that I have had one occurence where I could not find something wrong. The customer was saying that the computer was to slow. In that instance I called them up with some timings I had made. E.g. Word takes 10 sec to start etc. Asked them if this was the problem. I would send it back to them and have them time it. I eventually found out that thought everything was suppose to be instantnious.
So after all that my advice, phone them up. Have them walk you over the phone what is wrong with it. Then you can tell them either you cannot reduplicate the issue, or that you don't support that.
FYYFF
(EOM)
It's possible that you're wrong, and the product really is performing poorly for them, and not because of a legitimate reason like "the server is slow because so many people are using it simultaneously."
I have been on both sides in situations like this where the service provider or vendor was wrong. I've made the mistake of jumping to conclusions when I couldn't replicate the problem, or when I thought the customer was being unreasonable. I've also had to deal with people who were clearly making the same mistake, and it cost them any future business from me.
My advice would be that if they're still convinced it's a problem, either go see it in person (if this is an expensive product), or offer them a full refund.
"...always new atoms but always doing the same dance, remembering what the dance was yesterday." -Richard Feynman
Perhaps it has intermitant issues that need to be tested more thoroughly? Perhaps there's an outside variable causing the product not to work (I guess the "user" has already been mentioned here, but there are others). I don't know enough about the product to know if this is possible. People will believe what they want to believe as consumers, so you either need to reason with them or just bite the bullet and take the product back.
Only to idiots, are orders laws.
-- Henning von Tresckow
You do everything you can to try to find the true problem, then you work with the client to find an acceptable solution. If your client is similar to this computer store customer [Video], then you take the appropriate action. Watch the video to the very end to see how to handle the situation properly.
It must be Windows. It needs half a gig of RAM and a hardware-accelerated graphics card just to run Solitaire.
I try to please them as much as I can without giving them oral. If that doesn't work, then I point them to a piece I did just recently, explicating how they make me feel.
Seriously though, sometimes you just have to guage how much you value that customer. I work in the newspaper industry (art, advertising, and new media), and when a print product doesn't come out like they wanted, we'll determine if it's our fault or theirs. Usually, we'll give them a free run in the paper, sometimes even if it is their fault (for instance, not catching something in the proof we sent them). If the customer becomes belligerent, or refuses to pay their bill, we cut them off and tell them to find another place to advertise until they grow up. Mistakes happen in any industry - while it does suck, we can only compensate a customer so much.
"Better to be vulgar than non-existent" -Bev Henson
I hold both the copyright and trademark on telling a customer to "fuck off"!
Perhaps too plain and simple an answer.
DT
Is this thing on? Hello?
I am probably on the opposite side of this kind of situation. We even had the vendor come in and do a complete analysis during one of our busiest times. They gave us a report that told us nothing new. Thier excuse? The next version, due any day now, is supposed to be faster then the old one and they only give us 7 months to upgrade to it(no,, not really, but in our case, we're a college....you DON'T launch new products during the Fall quarter! Which means we launch in April for summer registration, our lowest time of year). Anyway, we have had third parties VERIFY the issue is with the software, yet the VP's running the company have never heard of the issue. Oh and this is running on what is some of the fastest stuff available....16 processors and 100 gig of ram....tons of hardware....we could write a system that would be EASILY 3-4 times as fast as this crap we're running now....and NOT upgrade for another 4 years.....Yeah our version would nto be as complex, but it would do what WE want and not all of the extra junk. So when you THINK the customer is wrong, make sure you are really sure about that.
Gorkman
While I'm sure this is a simplified summary of what occurred, there needs to be more investigation into the problem than, "It looks fine to me." What exactly is slow, how slow is it, when is it slow? What is unresponsive, how unresponsive is it, when is it unresponsive?
It could very well be that the customer has found some part that is slow and unresponsive, or it could just as easily be that the customer has unrealistic expectations and you need to show them a competitor's product and say, "see, it is just as slow and unresponsive as you think ours is."
Ask for more information. Ask for more details.
Of course the customer could be unrealistic, and no amount of effort is going to make them happy. In that case tell them not to let the door hit them on the way out.
Look at the discussions around here. Every time any software has a story, there are always a number of people complaining about how "slow and unresponsive" that software is. "OMG, I've had it running for three months straight and it is taking up 80mb of my 2gig of ram. What a piece of crap!"
http://www.popularculturegaming.com -- my blog about the culture of videogame players
I have had many issues where a customer's overzealous internal network security slowed EVERYTHING they did down. But they wouldn't talk about their apps, only ours.
Does the app run in an environment that doesn't have as much connection to anything they might have broken internally?
Do the guy's co-workers think it's slow as well, or is this person insane?
My mom says I'm cool.
The number of people out there who will complain just for the sake of complaining...for entertainment purposes...is shockingly high.
It's best to keep your distance from these people, as they are selfish and unpredictable.
"If it is too much trouble for your organization, give your customer the names of some competing product or another product that will fit the task and send them on their way."
And on their way out they will tell everybody and the world what a bunch of whankers you are. Some of us actually
survive or go under by mouth propaganda.
I worked on a plugin that's being sold today. One of the things I pushed for early on is that we can offer refunds for people that cannot get it working, even if the fault's on their end instead of ours. As a result, we're pretty quick to say "If we cannot get this working, don't worry, we'll give you your money back." It has been my experience that most customers that hear this early on are happier to work with us troubleshooting the problem. It puts them into a position of feeling like we're truely trying to help them, plus it relieves them of the burden of trying to prove it's our fault. We've had a few hundred sales, and we've only issued a couple of refunds. To the best of my knowledge, we don't have any unhappy customers, and that includes the two we gave refunds to. (Heck, they may even come back when they have some time to put into troubleshooting.)
I don't know if you can offer a refund or not, but I thought I'd suggest it. I can tell you from personal experience that inability to get your money back is one of the biggest frustrations with support problems. If you can get the money element off the table, you may enjoy a better support experience.
"I like to lick butts!" by MobileTatsu-NJG (#32700246) (Score:5, Informative)
(1) Their perception is completely based on their inability to properly understand how the system works... or worse, they don't want to know. If what they feel is stirred by their ignorance, you can't beat that until you demonstrate (with a LOT of patience) that it does work.
This technique is more valuable than most people consider, because when you work with the customer as directly as possible (or explain as simply as you can what the readouts of the Task Manager Processes window actually represents), it actually helps to create the relationship that businesses really want with service providers.
(2) Another thing guiding their perception is spawned by the possibility that other systems may interfere with your systems. Your benchmarks and your test environment are not the same as theirs in production... what you see as a working, functioning model does not mean the outcome will be the same where they are.
Easiest example is like a network throughput test. You may see 100mbit full duplex, but they may work in a hubbed environment with a jabbering NIC somewhere on the network. Or a quiet network such as yours may not make multiple requests to the machine in question, but when they put it back online, it may be getting DoSsed out the yang.
(3) Last thing is to demonstrate the importance of your SLA, and what it does not cover. You must be firm about this, and explain that while your benchmarks indicate proper function, for a reasonable fee you can watch over their shoulder after it's reimplemented.
This becomes a cost/benefit exercise, but in one fell swoop, if you have the opportunity to visit his site, you might charge an hour's service wage to investigate on your own. Most often when I'm having to look at the impossible possibility, I have to open my mind as wide as possible, and consider as many variables as I reasonably can.
Keep your perspective as wide as possible. People don't always intend to insist things are your fault, but you better be aware of the fact that this customer will not be the first to bitch. If you succeed at solving the problem, you have both satisfied the customer, and demonstrated your ability to agreeably end hostile customer problems.
Some customers are unskilled and unaware of it (PDF link, 254kB). There is nothing you can do. In these people the level of incompetence is high enough that they cannot recognize their own inability. The only thing you can do is stay away from them. Don't explain, don't try to make it right. You cannot. Limit your losses and get rid of them. If nothing else helps, take the device back and give them a full refound.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
> In my particular situation, I have a customer who claims that the product we delivered them was slow and unresponsive. However, when we tested it to try and determine what was wrong, we didn't find anything wrong with it.
Sorry, you'll have to be more specific.
This is a situation where you should have a warrantability document that they must read before you do business with them. It doesn't have to be incredibly complex. You can google for thousands of examples of disclaimers of warrantability. I've been in the hospitality/restaurant business, and the IT sector as a small businessman for quite a while.
In the hospitality industry, usually, they just want someone to listen to them whine for a while because they are lonely. I find the ones that have a *legitimate* complaint in a hotel setting are very understanding of mitigating circumstances; They don't expect the sun to blink out *just* for them. The ones who seem unreasonable almost ALWAYS are looking for a free room, or a discount.
In the IT arena, it's not quite the same. Some of them want their money back because they dropped more money than they could afford, and some of them want you to fix a product that was designed in their own fantasy world (i.e., you didn't have a disclaimer of warrantability), so they expect it to do things that it wasn't designed to do.
Thusly, do yourself a favor, and create a disclaimer of warrantability.
Cheers.
Forget this. In memorial.
There's nothing wrong with firing a customer and/or client if they cost you more than you will ever make from them. Bad customers must be shown the door, then they become your competitions problem. Let the bad customer suck the life out of your competition instead of you.
Steve's Computer Service, Hobbs, NM
I have found that the most effective way to handle any client is to fully adress the situation at hand, and not just the technical issues (or percieved issues). All aspects of the situation must be examined with care. Be calm. Listen to everything the client tells you (and do not interrupt him/her) then repeat the situation back to the customer to make sure that you both have the same understanding of the situation. Also document everything. Be thorough. Record all indications of trouble, either stated by the customer or your own conjecture. Record all actions taken by you and your customer. Then you can start to get to the root of the problem.
If the client believes that you understand the situation and are really trying to resolve the situation (or find an acceptable workaroud) then he/she is much more likely to be happy with your company and more willing to pay your fees. If, however, the client is simply unwielding, beligerent, rude, or unacommodating then it may be time to end your business relationship and focus on other clients.
- James
... is that you?
We had a POS (point of sale) / inventory system that would occasionally freeze for everyone for exactly 3 minutes. There were also times where it'd slow to about 1/20th of it's normal speed (3 second report might take a minute) until the database server (just the service) was restarted. I never could find any network problems to explain it, and the server was pretty idle almost all the time. Maybe the author believed us, but it was never resolved. Eventually we just made the costly switch to something else.
Though I'm sure you encounter many customers who expect the software to be infinitely intelligent and psychic. If they're sincere, there's not much you can do about them, except sever your relationship with them and feel secure in the knowledge that their life will be full of disappointment. But I suspect a number of customers will just exaggerate the problems of the software in an attempt to end their service agreement with a refund, like this person.
Challenge them to find a better product.
Some dumb and sort-of-unrelated observations: It isn't how it looks to you, it is how it feels to him. I was walking out of the courthouse with a client after the judge ruled against us. My client told me not to worry about it. He said I had clearly presented his case. He knew there was a chance of losing, and he had lost the gamble. He thought he had received justice because he had his side clearly and eloquently presented, and he felt the judge had ruled against him on one of the marginal points. Southwest Airlines employees like to re-tell the story of the lady that wrote numerous complaint letters, objecting to many of Southwest's unique policies. The staff finally kicked one of her letters up to CEO Herb Kelleher. It took Kelleher sixty seconds to compose his response: Dear Mrs. Crabapple: We will miss you. Love, Herb. It isn't how it looks to him, it is how it looks to everyone else. That one sale will neither make nor break your business. If the rest of the general public is convinced that you treated him fairly and respectfully, listened to his problems, and made a serious effort to find and eliminate any possible problems, then you are ahead of the game. With those kinds of folks, I find it best to go a little overboard. When they complain to friends and neighbors that you didn't do what they wanted, they will be quizzed about what you did do. When the complainers describe the above-and-beyond things you did to fix their problem, first, the audience will disbelieve the complainer, and second, it might just generate some business. It often worked that way for me.
All is paradox. Retired lawyer, so this is just one more layman's opinion.
Usually I come in late in the game when the customer is already unsatisfied, and most of the time for very good reasons. I don't know who you're dealing with or at what stage in the game you enter, but none of my customers are in any position to judge my competence in my expertise, otherwise they wouldn't require my help. I do know people who can judge my competence in my expertise, but they are not my customers
.2K/s for dynamic pages should fall under unresponsive, unresponsive should fall under "something" wrong, and something wrong especially for a commercial website leads to a very unsatisfied customer.
"I have a customer who claims that the product we delivered them was slow and unresponsive. However, when we tested it to try and determine what was wrong, we didn't find anything wrong with it."
I had a similar experience last year. Two months of debating and hair pulling with a major hosting company over the meaning of slow, and "anything wrong". In the end we did agree that a 2K/s for static pages, and
http://en.wikipedia.org/wiki/Quantitative
You will never understand their problems until you step in their shoes.
The software you will always work very well in your own computer.
However, when it is install in your customer's computer. Your application will be fighting for resources
with the customer's 101 applications.
The matter will be worst if their computers are a few years older than yours.
You must work for Blizzard on that WoW thing.
Once upon a time, a soon to be mommy and daddy loved each other very much (the lust was strong as well as the drinks)
Rat Sound Message Board
General
Doing the Gig (Moderator: Forum Admin)
when singers throw your mics around!
While the issues may be different, the idea of taking a PROBLEM and rendering it into an opportunity is the same.
Technology -- No Place For Wimps! Grateful Dead and Jerry Garcia Chatroom -- http://www.wemissjerry.org
I have a customer who claims that the product we delivered them was slow and unresponsive. However, when we tested it to try and determine what was wrong, we didn't find anything wrong with it.
Steve Ballmer is MoOsEb0y?
mcgrew's razor: Never attribute to stupidity that which can be explained by greedy self-interest
I'm not working in technology (I'm in university and working a summer job in dealing with conferences on campus) but I have a ton of interaction with customers. Specifically, we have a huge group (~1200) of elderly schoolteachers here. These people expect hotel level care and convenience from a fairly spread out dormitory campus, which we just aren't prepared to provide.
We do as much as we can (a 24 hour help desk, for instance; I'm working 16 hour days with generous OT), but eventually you need to tell people that you cannot help them. Some tricks to this:
1. As other people have said, for the love of god stay calm. More reasonable people will cool off when they realize they're the only ones yelling, but many won't, so...
2. Also be firm. Let them know that you can't help them until they leave (even if it's not strictly true). If they get out of your hair, they may cool off.
3. Pawning them off on a supervisor is always effective, or even someone imposing who might appear to be a supervisor.
4. My boss told me this on the first day, and even if I can't always follow it, it's a good ideal: "Never say 'no,' always present an alternative.
"Just because you're eloquent doesn't mean you aren't a fucking crackpot." -Wavebreak
If you aren't solving their problems, then you appear incompetent. Appearances go a long way. Which means, you need to figure out how to solve their problems, rather than do a few tests and throw up your hands in defeat. If it were me, I'd look at this as an opportunity to actually use my problem-solving skills, rather than just grind out code.
This post expresses my opinion, not that of my employer. And yes, IAAL.
You need to find out what is really happening. Often, the users are experiencing problems. I deal with industrial applications. Generally, I assume the users are having problems, and I am not getting accurate enough descriptions to debug with.
Often, the problems are real. It is just the cause that is not obvious.
I've been on both ends. Sometimes, as a customer calling tech support, I've tried to explain the situation and had the other guy just assume I couldn't possibly be right and hang up on me. Calling back, I'd get a different person and then them work out for themselves what I'd tried telling the first guy. 40 minutes later the fact that the cable modem wasn't working because the entire neighborhood was out would eventually come to their attention, as I'd tried telling them at first.
Most comments here seem to be (unjustly) bagging the customer for their own ineptitude. Without more information about your product it's difficult to say, but it's possible that the customer is correct and is actually experiencing slow operation due to link latency between their site and yours. If you're testing the product's correct operation from your local network (instead of connecting from a remote ISP's dial-up or DSL link) of course it will seem fine.
Remote users of MS Outlook's MAPI client, for example, can attest to how painful that product can be - same goes for international users of World of Warcraft on Blizzard's "Oceanic" servers.
All this SLA, technical support, loser/user interaction reminds me of... /.ers were exposed to him. The BOFH.
Well, I don't know if the younger
Excerpt:
So, to relieve the boredom, I get some iron filings and pour them into the back of my Terminal until it fizzes out (Which doesn't take all that long, surprisingly enough), then call our maintenance contractors and log a fault on the device. Sometimes they'll send someone who knows what they're doing, but it's a lot more fun when they don't - which is about 98% of the time.
So their maintenance guy comes in, and I can tell he's NEW because the photo on his ID actually LOOKS like him, not like the head engineer, whose photo's a black and white tin-type (he's that old).
Maintenance Contractors always dress up nice, with a tie and everything because they believe that a customer will trust a nicely dressed guy with their million dollar equipment *just* because he's got a nice tie..
Because he's NEW and ALONE, he's what you call an appeasement engineer, the new guy they send so they respond within the 4 hour guaranteed response period. (Things are getting better and better) Your average appeasement engineer is about as clued-up on computers as the average computer "hacker" is about B.O, and their main job is to make sure the power plug is in and switched on, then call back to the office for "PARTS". The really keen ones will sometimes even take a cover off the equipment and pretend that they see this stuff all the time. I wonder what sort today's is...
Complete story here.
All about BOFH@Wiki: http://en.wikipedia.org/wiki/PFY
Quem a paca cara compra, paca cara pagará.
I get this all the time. I've been troubleshooting systems since the mid-60's, and now I get a lot of calls to fix systems that other techs and engineers failed to fix. One thing I've learned over all those years, is that 90% of problems on most projects (including my own) are due to inadequate design and specifications in the beginning.
A problem is a discrepancy between the way things are and the way you want and expect them to be. All problems have a specific description, and elements of timing, location and scope. In order to resolve a customer's problem you must have agreement UP FRONT about what the resolved problem looks like in description, timing, location and scope. Without that agreement about "how you know when the problem is solved" you will just keep tracking unspecified problems. Precision is ultimately important.
Now, if one of my projects fails to perform within the environment, time and extent that I promised, I fix it. Occasionally the customer has an additional requirement (change orders, anyone?). If I can profitably meet the customer's requirements, I will. Some projects are not worth fixing. In less than one percent of my projects have I had to give a refund or a discount, but I'm willing to do so if that will get some projects out of my hair. As has already been said, some customers are not worth having. I usually find this out when I try to get proper agreement on the specs and prices.
Occasionally I find there are conditions outside my control that keep the project from performing like the customer expects. I will work with just about anyone to help alleviate these problems, but if it works correctly in my test environment, and if the test environment is spec'd at the design phase, and if the customer agreed to the test environment, then it's not my problem. (The last problem I had like that, about 4 years ago, the customer changed telephone systems just before I installed the project, and the new system had some incompatible idiosyncracies. The customer paid extra for me to resolve the problem.)
If you are not trained in a formal problem resolution process, I recommend starting with "The New Rational Manager" by Kepner and Tregoe. Good luck
"The mind works quicker than you think!"
No, really.
*shudder*
Funny Captcha word: Extract. Oh, the irony.
I see the solution in placing enough numerical thresholds, which can be precisely tested. Once the performance can be precisely evaluated using scientific method (and not subjective "feel"), customer can either proove fault using scientific method, or be satisfied with the product.
there is no issue with my network
..."fixing" situations like this by having the customer *show* me how the product is not working. This has the dual benefit of showing you whether it's the product or the customer that is malfunctioning, as well as giving you a chance to educate the customer if needed.
I can say that I have been on the customer side of this crappy equation, and it pisses me off. If their expectations were too high, then you need to reign in your sales-weasel that promised them the moon and the stars. If they aren't getting the functionality that can reasonably be expected, then you need to fix your software. In my case, the company told us that "We don't know why our software keeps crashing on your systems, but it had to be your fault because it works fine for us here. Let us know what you find out." For 70k per year we expected better. Two years later it doesn't work any better and we have to spend hours on workarounds to prevent crashes. Unfortunately they are the only ones that make software that does what it does.
People who think they know everything really piss off those of us that actually do.
What are you people thinking? How do you stay in business with all these refunds you're giving out? The ONLY time you give a refund is when you do not deliever as promised. That means selling your product for what it is. Don't ever tell someone that your system will turn lead into gold, and if it does, then it does it at its own pace. Level of proformance should not be implied, as you cannot guarantee that. Only infomercials promise to do something at break-neck speeds. ATi doesn't tell you that you'll get 60fps in Farcry, just that it does 4x AA...
Got a difficult customer? Tell them trouble-shooting is $35/hour
I'm fighting The War on Drugs!
Funny you should mention "The customer is always right" phrase.
Not many people know or remember that this phrase was originally created by Sears, Roebuck, and Co. as a marketing motto about 100 years ago, around a decade after the Sears Catalog came into existence.
If one were to quantify how horrific that quote's effect on world (and more significantly, US) culture has been, one may venture to remark that it would be similar to Ebola or AIDS -- compared to the "free gas for a year if you buy a new Hummer or Expedition" advertizing that seems to be going around nowadays that would roughly equate to a common Cold or a light case of Influenza.
The customer is not always right. In most cases, the customer is dead wrong and is too ignorant to realize they are broadcasting that fact to everyone they meet.
In my particular situation, I have a customer who claims that the product we delivered them was slow and unresponsive.
Customer: "Hey, Funkmaster Fresh Fly , those girls you sent over took two hours to get here, and they were nodding off on heroin when they arrived. They just lay there drooling!"
However, when we tested it to try and determine what was wrong, we didn't find anything wrong with it.
Funkmaster Fresh Fly: "Yeah, we fucked those bitches hard and they was squirmin' around and yellin' and shit. Maybe you just got a little dick?"
- None can love freedom heartily, but good men; the rest love not freedom, but license. -- John Milton
Either you're dealing with a customer who isn't worth the effort, or you really aren't trying hard enough to solve the customer's problem.
I've called many tech support desks where the help treated me as if I was being unreasonable, but the tech was being incompetent. Here are some examples:
Again, perhaps you really haven't tried hard enough to understand the customer's problem.
No, I will not work for your startup
Wouldn't a solution also be to sue him for defamation? It's overused, but that particular charge exists for a reason.
Phrases like ..claims that the product we delivered them was slow and unresponsive.. really means
Time for Hookers and Booze.
-- www.globaltics.net
Political discussion for a new world
Thanks for the license, but I believe I have prior art
whoa.... Let's recap
That guy's going to be spending a long time in the Sunday confession.