What’s the standard practice to prevent users from having unreasonable expectations?

There’s some subscription-based data processing web service – users pay via PayPal for the right to use the service. The “terms of service” document prepared by lawyers explicitly says that there’re no guarantees so customers can’t possibly file a lawsuit.

Now the service doesn’t always work trouble-free. Sometimes there’re network problems and so it’s unreachable to some clients. Sometimes there’s a problem with third-party services the service depends upon. So something like twelve hours per year total it doesn’t work. This is not perfect, but IMO very good.

Yet clients feel that since they’ve paid for it – it must just work, period, at all times and they even write claims for compensation to the service support.

I’d guess they just don’t read the “terms of service” but I can’t be sure.

What’s the standard practice (besides having “terms of service”) to prevent users from having unreasonable expectations?

I think the only real answer here in helping your customers with unreasonable expectations is to be proactive with positive customer service.

What I mean is take every opportunity to reach out to your customers in a positive way when things are going well and go above and beyond to satisfy them when things are bad and most will overlook the small issues and negative experiences.

Overwhelming positive customer service will quell much in the way of negative experiences.

As a side, most users do not adequately read the ToS but stating it when they have a problem is not perceived as a positive experience. Sometimes even when you are right and they are wrong, you just have to make it right for the subscriber. What that is for your particular business I don’t know. A free month maybe?

Make some promises, make them prominent, and keep them. If you fail, extend your user’s subscriptions appropriately to cover the down time. Don’t promise anything you don’t think you can deliver, but if you start making (and keeping) promises, then you’ll take care of a lot of the customer issues.

Now, your lawyers may try to weasel-word you (in the TOS) out of making these promises real. Don’t let them do it.

Don’t promise you’ll give away the store if it all goes pear-shaped on you one day (because it will), but don’t treat these promises like marketing-speak. Mean them. Own them. Live up to them.

Do realize that you’ll always have some annoying customer who thinks that having sent you $5 entitles them to everything in the universe, and compensation in the form of jeweled goblets filled with caviar whenever you have 5 minutes of downtime. Just be firm and tell them no. They might walk, but don’t give into irrational demands – give them what you’d give everyone else, and get on with your day.

One other thing: A “terms of service document prepared by lawyers” is not good enough. Write plain language and state your service (and limitations of it) clearly in advance and in no more than 5 lines.

Plain and clear language come first. Legalese is totally unimportant in developing good customer relations.

Otherwise:

Don’t promise what you can’t provide

This is good both legally and for customer satisfaction. If you’re advertising better service than you’re providing (100% Uptime!) on your main page, even if the Terms of Service are more laid back there’s going to be trouble. This also applies to comparing yourself to services that you can’t match/etc. Focus on what you do well and sell it for all its worth, but do make sure you can actually live up to it.
Try to show the customer that you feel their pain when things don’t go well

Things break, services go down. When they do, make sure the customer knows you care. Don’t let them bully you into feeling like you have to provide more than you said, but if you have the opportunity to go above and beyond, do so. And certainly if you DO drop below the terms of service, make sure you compensate them properly.

What you can do:

Be willing to weedout bad clients.The customer is always right, but in my interpretation, if they don’t want to pay for services or they believe they’ve paid for services at a price I’m not willing to provide, you’re no longer my customer. This could be a mutual agreement, maybe not. There is another old saying about getting what you paid for. If you stay at a cheap hotel expect cheap service. If I stay at a five star hotel and want a peanut butter sandwich at 4 O’clock in the morning and they run out, someone better run down to the corner store and pick up a jar and it’s not going to be me. That’s the expectation and the fact you paid a lot of money supports that agreement and justifies their rating.
Manage Expectations with warnings. Website outages never happen at a good time. Most people would prefer scheduled maintenance, so they can plan around it. If you’re not doing that, you should. Send an email. Post it on your site when they log in. Keep people informed. Taking the site down because you’re trying to manage the added growth could be interpreted as a positive sign that you’ll be around.

The success of Facebook wasn’t the idea for a social networking site (It wasn’t the first.) it was the ability to manage the technical requirements of adding millions of users and keeping up with the volume without crashing like all the other sites. It is nearly impossible to do, but they’ve separated themselves very successfully.

I work for a company that also provides data as a service. So I feel your pain. We have decided that keeping customers for the long term is more important and thus we decided to give refunds (so in the long term we keep them paying a monthly fee).

The only way to stop the complaints is to start providing refunds.

Do it such a way that you detail exactly how much you will refund (explicitly how it is calculated) and under what conditions the refunds kick in. Differentiate planned vs unplanned outages. This can be very strict just document it. Make the calculations done in such a way that it will be unlikely that you refund much (this is not unreasonable either) and the max you refund is one payment (assuming customers pay monthly).

Customers will vote with their feet and stop paying if the don’t like the service.

Put on the home page down-time in the last 12 months and expected down time in the future (given past experiences). On the front page put a link to a page that details all down times and explain why the service was down. just be open and honest.

You have to remind people that downtime for a service is expected and document the conditions under which you expect to fail.

This really isn’t your question, but that a system works all the time isn’t “unreasonable”. With that being said, it would depend on how your system reacts to failure by third party systems and providing a good user experience when those occur.

As for your question. I would say that the best way to handle user’s expectations is to provide them with a good experience in working with your system. This will help reset your user’s expectations of the system. As pointed out in the comments, “No one reads the terms of service anyway”.

Filed under: softwareengineering - @ 17:58

Thẻ: users, web-services

Thiết kế website giá rẻ

Danh mục

What’s the standard practice to prevent users from having unreasonable expectations?