Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021
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.
Apologize
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.
Be honest with yourself
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.
Resolve the problem quickly
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.
Diagnose the cause of the problem
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.
StatusCake Team
Share this
More from StatusCake
In the Age of AI, Operational Memory Matters Most During Incidents
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
James Barnes
April 10, 2026
AI Didn’t Kill the SDLC. It Made It Harder to See
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
James Barnes
April 2, 2026
When Code Becomes Cheap: The New Reliability Constraint in Software Engineering
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
James Barnes
March 25, 2026
Buy vs Build in the Age of AI (Part 3)
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
James Barnes
March 18, 2026
Buy vs Build in the Age of AI (Part 2)
6 min read The Real Cost of Owning Monitoring Isn’t Code — It’s Everything Else In Part 1, we explored how AI has dramatically reduced the cost of building monitoring tooling. That much is clear. You can scaffold uptime checks quickly, generate alert logic in minutes, and set-up dashboards faster than most teams used to schedule the kickoff
James Barnes
March 11, 2026
Buy vs Build in the Age of AI (Part 1)
5 min read AI Has Made Building Monitoring Easy. It Hasn’t Made Owning It Any Easier. A few months ago, I spoke to an engineering manager who proudly told me they had rebuilt their monitoring stack over a long weekend. They’d used AI to scaffold synthetic checks. They’d generated alert logic with dynamic thresholds. They’d then wired everything
James Barnes
March 4, 2026