Monitoring
Status Pages
Pricing
If you have an online business, eventually, it’s bound to happen – you get a bad online review. Sure, a bad online review can ruin your day, but it’s not the end of the world, or more specifically, it’s not the end of your business. If you treat a bad review as an opportunity to learn more about your customers and how they perceive your business, you can turn a negative experience into a positive one.
When dealing with a bad review, there are several things to keep in mind. First, the internet is a land of extremes, not moderation. There are very few three-star reviews. People usually write positive reviews or negative reviews, and they tend to use extreme language when doing so. Secondly, people are more likely to write a review if they are unhappy, so one negative review is not representative of how the majority of your customers feel about your company. Nevertheless, you must deal with a negative review promptly if you wish to maintain control of your online reputation. Here are the steps to take to respond to a bad review.
Even if you didn’t do what the customer said you did, apologies for the incident. Apologize sincerely and tell your customer that you are sorry that they feel the way they do. Empathize with the customer and indicate that you understand how they feel. Promise you’ll look into the problem and get back with them shortly. Don’t tell your customer you’ll “try” to resolve the problem – that’s not what your customer wants to hear. Your customer is unhappy and wants to resolve the problem, not just try to do so.
You’re probably angry because of the bad review, but don’t let anger cloud your judgement. Be honest with yourself as you investigate the incident and if your company’s actions caused the problem, take responsibility for it. Taking responsibility will help you craft a credible response to your unhappy customer and help you avoid causing the same problem in the future.
After you’ve investigated the problem, get back to the customer promptly to resolve it. If possible, develop a dialogue with your customer offline via email, as dealing with a problem offline can help diffuse anger and lead to a constructive resolution. Listen to what your customer is telling you. Ask your customer what you can do to make things right, Your customer will appreciate that you asked for their input, and accept their solution if it is reasonable. A frank dialogue can lead to a mutually agreeable solution and can turn an unhappy customer into a happy one.
Once you’ve resolved the problem with your customer, spend some time diagnosing what caused it. Your objective here is not to assign blame to someone but to understand why the problem occurred so you can take corrective action so that it won’t happen again.
If you handle it correctly, a bad review can help you improve user experience.
Share this
4 min read On 13th August 2026, a storm knocked out cooling at RadiusDC’s Phoenix data centre, which hosted essential Namecheap operations. To protect hardware from thermal damage, Namecheap took services offline while temporary chillers were brought in. The incident and recovery ran for roughly 30 hours, with Namecheap’s own site unreachable for about 11 hours 42 minutes
3 min read On Wednesday 19 August, Monzo had an outage. DownDetector logged more than 3,000 reports by midday. Monzo’s own statement was direct about what it did next: it activated Monzo Stand-in, its fully independent backup bank, while it investigated an issue affecting customers. By the end of the day, Monzo said the issue was resolved and
3 min read GitHub’s incident on 17 August 2026 ran from 13:28 to 21:15 UTC, seven hours and forty-seven minutes. At peak, web and API traffic saw error rates of around 20%, while archive and raw-content downloads reached roughly 50%. SAML and OIDC authentication, SCIM and Team Sync were affected alongside Git operations, Actions, Pages, Issues, Pull Requests
3 min read Adding a new website, launching a customer portal, or handing a service to a new team should be straightforward. Setting up monitoring is part of that job, but it is easy for a manual step to be missed when information is spread across several systems. StatusCake now integrates with viaSocket, giving teams a way to connect
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
Find out everything you need to know in our new uptime monitoring whitepaper 2021
