I gave two customers full refunds this month and took them off our contact list, and I'd do it again.
I want to be clear about what that means before I explain why. I handle patient conflict personally at SOM Aesthetics. Most of the time I'm good at it. I can find what's underneath a complaint, address it, and keep the relationship. I like solving problems for people.
But twice this month I couldn't get there. The situation was past what problem-solving could reach. And I made a decision I want to talk about, because nobody teaches founders how to make it cleanly.
What Most Conflict Advice Gets Wrong
The standard advice is to save every customer. Find the win-win. I believe in that, up to a point. The point is this: some customers are not upset about a problem. They are upset as a state of being, and no resolution changes that state.
You can recognize them because the conversation moves but never lands. You address one concern and a new one appears. You offer a solution and it's not enough. You engage and they escalate. There is no landing spot.
Chasing that landing spot costs you time, team energy, and often money spent on service recoveries that don't recover anything. The refund you should have given in week one becomes three weeks of attempts and then a refund anyway, plus the team morale hit.
Most of the time I'm able to really tap into people's experience and problem-solve successfully. But twice lately people were just so upset that I gave full refunds and took them off our lists. That's the decision.
Solvable Problem or Unsolvable State
There is one question that cuts through it. Ask yourself: is this person describing a problem I can solve, or a state I cannot change?
A solvable problem looks like this. A patient is unhappy with a specific result. They can tell you what they expected and where the gap is. When you address the gap, the conversation has somewhere to go.
An unsolvable state looks like this. The complaint is global. Nothing has been right. The tone is accusatory from the first message. The person is not describing an experience. They are performing an emotion at you.
Solvable problems get my full attention, every time. Unsolvable states get a clean exit: full refund, clear communication, relationship closed.
Build the Policy Before You Need It
Most founders handle refunds badly because they're making the policy at the moment they need to apply it. That's the worst possible time. You're reactive, under pressure, and the situation pushes you toward half-measures that don't close anything out.
Write the policy now, in a shared document your whole team can see. Define three things: what triggers a full refund, what triggers a partial refund, and what behavior from a customer ends the relationship regardless of the financial outcome.
That last category matters. There are behaviors that warrant closing the door even when the underlying complaint is legitimate. Decide what those behaviors are in advance. Otherwise you'll apply the standard differently every time, and your team won't know what to expect.
For us, the trigger for ending the relationship is extended hostility directed at our staff. One difficult conversation is normal. A pattern of escalation that takes multiple team members off their work ends the relationship. The refund is not a reward for the behavior. It's the clean close on something that isn't working.
Protect the Team First
This is the piece I feel most strongly about. Your team members are not customer conflict absorbers. The longer a difficult customer interaction stays at the staff level without escalating to you, the more it costs the people who work for you.
Make the escalation path explicit and easy. Set it up in your practice management software or your team Slack so anyone can flag a situation to you in one message, without having to justify it or assess whether it's serious enough. You handle it, same day, and you make the call. They don't carry it home.
The cost of keeping a problematic customer is never just the refund. It's the staff member who's dreading coming in tomorrow because they know that person is calling again. That cost is real. It doesn't show up on the P&L.
One More Thing: Get Something in Return
If you're going to break your no-refund policy, get something back for it.
We use a release of liability when we issue refunds for non-standard situations. It's a short document the customer signs that confirms they received a full refund and release any claims against us or our staff related to their experience. It doesn't have to be complicated. Ours is one page.
This matters for two reasons. First, it closes the loop legally. You gave them something of value; they acknowledged it and agreed not to pursue further action. Second, it signals to the customer that the transaction is complete. There's no next move. The door is closed from both sides.
Most founders just issue the refund and hope the person goes away. Sometimes they do. Sometimes they leave a review, file a dispute, or send one more email six weeks later. A signed release eliminates that ambiguity.
If you're going to break your own policy, you deserve something for that decision. Make it count.
Three Things to Do This Week
First, write the policy. Open a shared document and define what triggers a full refund, what triggers a partial, and what behavior ends the relationship regardless of outcome. Keep it short. One page is enough. The point is that everyone on your team knows the standard before the next situation arrives.
Second, build the triage question into your process. When a complaint comes in, ask one question before you respond: is this a problem I can solve, or a state I cannot change? Solvable problems get full attention. Unsolvable states get a fast, clean exit.
Third, set up the escalation path in whatever tool your team uses today. One message, one flag, comes to you. They should never absorb more than one difficult exchange before it lands on your desk.
And if you do issue a refund outside your policy, have a one-page release ready. It takes five minutes to draft and one signature to close the chapter.
I don't love giving refunds. But I don't lose sleep over the two I gave this month. The door is closed from both sides. The team is fine. We're not spending another hour on customers who couldn't be satisfied no matter what we did.
Sometimes the right decision is the clean one.