How To Deliver Bad News In A Positive Way To Customers

Delivering bad news always ends up with a bad customer experience. Or is it? If you can be a bit tricky here, you can turn this into a good CX. We all need to know how to deliver bad news in a positive way.

There are a few strategic approaches to turning the situation into a positive one. We will get into that step-by-step. Let’s start with delivering the bad news to the customer.

How to deliver bad news to customers 

This is the tricky part of a support agent’s job. It’s never easy to deliver bad news to anyone. If that person is a paying customer, then it becomes more difficult. Because you don’t know what the customer is going through or how they will react.

So, here are three tips that can help you manage and control the situation like a pro.

Step #1: “The reason…”

Instead of directly saying the bad news, start the sentence with “the reason…”. That means, start with the reason for the bad news that you are delivering. That way, the customer will understand the situation instead of getting angry about it.

Let’s say you have to tell a customer that you are going to terminate an online account. If you say this without any context, the customer may get understandably mad about it.

But if you start like this,

As you can see in this fake scenario, after adding context to the “bad news,” it doesn’t look like bad news anymore.

Step #2: “So that you…”

In the previous stage, we prevented the anger of the customet. Now comes the next step. Now let’s bring context to the benefits. At this step, we will provide some benefits to the customer as they get out of this “bad news.”

So, continue your conversation with the customer by adding, “So that you…”. Here’s how it can go:

See what we did here. We showed the benefit of the action. In addition, we opened an opportunity for our next and last step.

Step #3: “Would you like that?”

Up until now, we dodged the bullet. The customer is now calm and well informed about the situation. In the final step, we will provide a possible solution to compensate for the situation.

So, we will continue our conversation and provide a solid solution or remedy to prevent the harm from the “bad news.”. You have to end the conversation by saying, Would you like that? That way, you are handing over full control of the situation to your customer.

The conversation goes on.

Now that you have made a decision, customers will be more engaged and collaborative instead of getting angry.

How to deliver bad news in a positive way sample scripts

Reading the three steps is one thing. Seeing them used on a real ticket is another. Here are nine samples you can borrow for situations your team runs into.

Sample #1: Refund denied, no exception

Let’s say a customer wants a refund, but it’s way past your 30-day window. There’s no secret exception waiting to be found here. The only thing you control is how you say no.

Conversation: I’ve looked into this. I’m not able to process a refund, the purchase is 94 days past our 30-day window and that’s not something I have the ability to override. I know that’s not what you wanted to hear, especially after using the product for a while.

I don’t have a workaround for the refund itself, but if anything else is going on with your account, I’m glad to look into it.

As you can see, there’s no manufactured exception here. Just the reason, said once, and then it stops. That’s the respectful part. Dragging out a no, or hiding behind vague policy language, is what actually damages trust. Not the no itself.

Sample #2: Shipping delay

The package is late and the customer just wants to know why. Guessing, or apologizing without any details, only makes it worse.

Conversation: The reason your order is delayed is a carrier backlog in your region, not anything on our end. It’s three days behind schedule right now. So that you’re not left guessing, I’ll email you the updated tracking number the moment it moves. Would that help?

This one leans on the same “the reason” and “so that you” pattern from earlier in this piece. Once a customer understands why, a delay stops feeling personal.

Sample #3: Feature request declined

Let’s say someone asks for a feature that’s not on your roadmap. Saying “we don’t do that” just shuts the door. Saying why keeps it open.

Conversation: The reason we haven’t built that yet is it would slow down the core workflow for most of our users. So that you still get close to what you need, here’s a workaround using [existing feature]. Want me to walk you through it?

This works because you’re not brushing off the request. You’re explaining the tradeoff and handing over a path forward in the same breath.

Sample #4: A price increase with no exception

A price increase is bad news for almost everyone who hears it. There’s rarely a discount that makes it not bad news. So sometimes the respectful move is just telling people early, and telling them straight.

Conversation: Starting next month, your plan price is going up by 10%. I don’t have a way to keep your account on the old rate, so I want to tell you now instead of letting you find out on your renewal invoice. If the new price doesn’t work for your budget, I understand completely. I can walk you through downgrade options, or help you cancel, no hassle either way.

No silver lining added here. The professionalism is in the early notice, and in respecting that the customer might leave. Not in pretending the increase is somehow good news.

Sample #5: Service outage or data issue

Something broke, and the customer’s data or access is affected. It’s the highest-stakes version of a routine ticket. But usually it’s fixable.

Conversation: The reason your dashboard was down for two hours today is a server issue on our end, not anything you did. So that this doesn’t happen again, we’ve added a backup system that kicks in automatically next time. I’ve also credited your account for the downtime. Want me to walk you through what changed?

Own it plainly. No dancing around it, no blaming the customer’s setup. The credit and the fix matter more than the apology.

Sample #6: Security breach disclosure

This one stays serious even after you’ve done everything right. You’re not just apologizing. You’re asking the customer to take action for something that wasn’t their fault.

Conversation: The reason we’re reaching out is we detected unauthorized access to a portion of our database earlier today. Your password may have been affected. We’ve already reset it and sent you a link to set a new one. We’re also offering free credit monitoring for anyone affected, no questions asked.

The credit monitoring isn’t a gift to make up for it. It’s just a standard protective step. The breach is still bad news, and pretending the monitoring cancels that out would be dishonest. Say what happened. Say what you’re doing about it. Let it stay serious.

Sample #7: Killing a feature people love

Let’s say you have to retire a feature people genuinely love. This one is different from a refund denial. It moves slower, and it hurts more, because you’re taking away something people already built their workflow around.

Conversation: The reason we’re retiring [feature] next month is fewer than 2% of users are still on it, and keeping it slows down updates for everyone else. I want to be honest, [replacement] covers most of what it did, but not everything, especially [specific gap].

That might mean this genuinely doesn’t work for your setup anymore, and I’m not going to pretend otherwise. If you want, I can connect you with someone who’s helped a few people through this exact migration.

The honesty about the gap matters more than the migration offer. A customer who hears “this might not work for you anymore” trusts the next thing you say a lot more than one who just gets a cheerful pivot to a feature that doesn’t quite do the job.

Sample #8: Responding to a public complaint

A customer posts about you on social media before ever opening a ticket. Now there’s an audience watching how you respond.

Conversation: Hey [name], really sorry this happened, that’s not the experience we want for you. I’ve sent you a DM so we can sort this out properly, since a couple details are best handled privately. Hoping to have this fixed for you today.

Short, on brand, and out of the public thread fast. The real conversation happens in the DM, where the actual bad news, if there is any, gets delivered without an audience watching.

Sample #9: The phone call nobody wants to make

Sometimes the bad news is a phone call, not an email, and there’s no fix waiting on the other end. A customer checked out, but a coupon glitch let their order go through for a fraction of the real price. Not their fault. But the balance is real, and someone has to say so out loud.

Conversation: Hi [name], I’m calling about your account, nothing to worry about, just want to walk you through something on our end. When you checked out last week, a coupon stacked with a sale it wasn’t supposed to combine with, so your order processed at $12 instead of the $299 annual price. That’s on us, not you.

I do need to let you know we’ll be charging the remaining $287 to the card on file. I wanted you to hear that from a person first, instead of seeing it as a surprise charge later. I can split that into two payments if that’s easier on your end.

Notice what’s missing here. No apology on the customer’s behalf for something they didn’t cause. No dressing up an unwanted charge as some kind of win. Just the number, the reason, and one small piece of control handed back through the split-payment offer. That’s really the whole point of this list.

Positive doesn’t always mean the outcome gets better. Sometimes it just means the person delivering hard news treated you like an adult the whole way through.

The most effective way of delivering bad news

While delivering the news, there are a few things you have to keep in mind. Otherwise, things can escalate very quickly and very badly.

Be honest. Do not give any wrong information to your customer. Not even try to musk up or hide any kind of information from your customer. Just be honest.

Be quick. Delivering bad news slowly is a bad idea. You are thinking you are easing it down. But in contrast, for the customer, it’s building tension and frustration. Just say it immediately, without rambling around.

Be clear. Do not use confusing words. If you are not clear about what you are delivering, be clear about it first. Be precise about what you are saying. And if there are any technicalities to it, try to break it down for the customer.

Be empathetic. Try to be considerate and understanding. Be apologetic, and acknowledge what your customer is feeling. Not all situations are the same. Sometimes the bad news can be devastating for the customer

Be calm. Finally, no matter what, you have to be calm. From time to time situation can be heat up, and customer can be very upset. But by being calm can handle the heated situation professionally.

How to deal with difficult customer

Here is the thing: no matter what we do, there will be one or two backfires. There are a few customers who might not be as understanding as they can be. It can be for a variety of reasons. You cannot predict customers’ situations; only assume.

So, from time to time, customers can be difficult. Let’s know how we can handle the situation.

Acknowledge the comment

Let’s say the customer didn’t take the news well. Generally, the first reaction would be anger. The customer might shout and start to say what damage they have to face because of the bad news.

We should never retract the situation. Address the situation politely. At some point, the customer might start making the same random suggestion. Instead of being defensive, say, “That’s interesting. Tell us more”.

That way, you are redirecting the anger and making the customer talk it out.

Be positive

No matter how angry your customer is, you have to be calm and positive. You have already diverted the customer to a healthy conversation. Now you value the customer’s advice and opinion in a positive way.

That way, you have a break-break pattern, from anger to casual chat.

Ask question

Now, to carry on the conversation, you can ask the customer questions. That way, you can get a proactive suggestion from the customer. Sometimes, customers have their own expectations. Asking questions is the best way to learn about that.

Check out this video to learn more about how you can handle difficult people.

There are very few cases where nothing works. And customers become abusive. In that case, you have to handle abusive customers with a strict strategy.

Final thoughts

No one likes to be that person who tells the bad news. But keeping your customers well informed is also part of good service. So, if it’s good news or bad news, you have to disclose it.

To keep your customers happy all the way, agents also need to know how to deliver bad news in a positive way. That’s how you can turn a bad situation into a good one, and you may make a loyal customer in the process.