---
title: "Empathy Statements for Customer Service: 60+ Free"
description: "Over 60 free empathy statements for customer service, by situation, with phrases to avoid and before-and-after rewrites. Add empathy to your own reply."
canonical: https://luckpanda.app/chatbot/tools/empathy-statements-library
updated: 2026-10-14
---

# Empathy statements for customer service that don't sound scripted

Canonical URL: https://luckpanda.app/chatbot/tools/empathy-statements-library
Language: en
Updated October 14, 2026

Copy a statement for the situation you're in, or paste your draft and add empathy to it. Every statement names what happened and leads to an action.

Free tool: https://luckpanda.app/chatbot/tools/empathy-statements-library (widget, customer-service)

Agents: run it over MCP (https://luckpanda.app/mcp) with chatbot_public_tool_run { "tool": "empathy-statements-library", "lang": "en", "inputs": { … } }; chatbot_public_tool_list gives the inputs.

## Frustration and anger

Name the specific thing that went wrong for them. A general "I understand" makes an angry customer angrier.

### They've had to repeat themselves

_The customer has explained the same problem more than once_

```text
You've now explained this [number] times, and you shouldn't have had to. I've read the whole thread, so you won't need to tell it again. Here's where things stand: [status].
```

### Passed between teams

_They've been transferred or redirected several times_

```text
You've been sent from [team] to [team] and nobody has fixed it. I'm staying with this until it's sorted, and I'll be the one who writes back to you.
```

### They lost time because of us

_Your problem cost them hours or a day_

```text
You spent [time] on something that should have been quick. That's time you won't get back, so I'll keep the rest of this short: [next step].
```

### An angry message

_The message is in capitals or full of exclamation marks_

```text
I can see this has gone badly wrong for you. I've read every part of your message, and I'll answer each point, starting with [the most urgent point].
```

### They've already tried the fixes

_They list the steps they've taken_

```text
You've already [restarted / reinstalled / cleared the cache], so I won't ask you to do that again. Let's look at what's different about your [account / setup].
```

### Their complaint is fair

_They are right and you want to say so_

```text
You're right to be annoyed about [issue]. If I'd [paid for next-day delivery / booked a table for a birthday] and this happened, I'd feel the same.
```

### They feel ignored

_Their earlier messages went unanswered_

```text
You wrote to us on [date] and heard nothing back until now. That silence is on us, not you. Here's the answer you should have had then: [answer].
```

## Waiting and delays

Swap "thank you for your patience" for what the wait actually cost them, and a firm next date.

### Delivery is late

_An order missed its delivery date_

```text
Your order was due on [date], and you planned around that. It's now expected on [new date]. I'll [check it every day / tell you the moment it moves] until it reaches you.
```

### A long queue to reach you

_They waited a long time in chat or on the phone_

```text
You've waited [duration] to talk to someone. I'm here now and I've read your message, so let's start with [first action].
```

### Waiting for a refund

_Money is out of their account and not back yet_

```text
Waiting for money to come back is stressful, especially when it's [amount]. The refund left us on [date], reference [reference]; your bank usually shows it within [number] business days.
```

### A callback that didn't happen

_You promised to call or write back and didn't_

```text
We said we'd call you on [date], and we didn't. I'm sorry. I'd like to fix that now: [what you can do now].
```

### An event or deadline at risk

_The delay threatens a date that matters to them_

```text
You need this by [date] for [event], so a vague estimate won't help. Here's what I know for certain: [fact]. And here's the backup if it doesn't arrive in time: [option].
```

### A ticket that's been open too long

_Progress has been slow_

```text
This has been open for [number] days, and that's longer than it should take. Today I [what you did]. The next step is [step], and you'll hear from me by [date] either way.
```

### You can't give a date yet

_You genuinely don't know when it will be fixed_

```text
Not knowing when this will be fixed makes it hard to plan around. I don't have a date yet, and I won't guess one. I'll write to you by [date] with an update, even if the update is "still working on it".
```

## Mistakes we made

Own it in plain words, say sorry once, and put the fix in the same message.

### Wrong item sent

_Your packing or ordering error_

```text
You ordered [item] and we sent [wrong item]. That's our mistake. The right one ships [today / on date], and [here's a free return label for the other / you can keep the other one].
```

### Charged the wrong amount

_A billing error on your side_

```text
We charged you [amount] instead of [amount]. That's our error, and I've refunded the difference of [amount] today. You'll see it within [number] business days.
```

### We gave them wrong information

_They acted on an answer from your team that was wrong_

```text
The answer you got from us on [date] was wrong, and you acted on it. I'm sorry. Here's the correct information: [correct answer]. If it cost you [time / money], tell me how, and I'll see what we can do.
```

### A missed appointment

_Your team didn't turn up or didn't call_

```text
You were booked for [time], and nobody turned up. You set aside part of your day for that. I've [rebooked you for the first slot you choose / refunded the booking], and [what else you will do].
```

### Their data or work was lost

_Something they made or saved is gone_

```text
Losing [work / data] after the time you put into it is awful. Here's what we can recover: [what can be recovered]. And here's what we can't, so you know where you stand: [what can't].
```

### The same mistake twice

_It has happened before_

```text
This is the second time we've [mistake]. Once is a slip; twice means something in how we work is wrong. I've [process fix], and I'll check your next [order / invoice] myself.
```

### A bad experience with our staff

_They describe rude or unhelpful treatment_

```text
Nobody should be spoken to the way you describe. I've passed your message to [manager or role], who will follow up with you directly by [date]. Thank you for telling us rather than just leaving.
```

## Bad news and saying no

Say no clearly, give the reason in one line, and lead straight to what you can do.

### A refund you can't give

_The request is outside your policy_

```text
I know this isn't the answer you were hoping for. Under our [policy name], I can't refund [item] after [period]. What I can do is [alternative], and I can set that up today.
```

### A feature you don't have

_They need something the product doesn't do_

```text
You've clearly thought about how you'd use [feature], and I wish I had a better answer: [product] doesn't do that today. The closest way to get there is [workaround].
```

### A product that's discontinued

_Something they rely on won't be sold again_

```text
It's disappointing when something you rely on is discontinued. [Item] won't be made again. The nearest match is [item], which differs in [how].
```

### An exception that was refused

_You asked for an exception and the answer is no_

```text
I asked [manager or team] whether we could make an exception, and the answer is no. I'd rather tell you straight than keep you waiting on a maybe. Here's what is still possible: [option].
```

### A price increase

_Their plan or service will cost more_

```text
A higher bill is unwelcome news, so here are the facts. From [date], [plan] will cost [new price]. You can [switch to another plan / pay yearly], or cancel before [date] and you won't be charged the new price.
```

### Information you can't share

_They ask about another person's account or details_

```text
I can see why you'd want to know [information]. I can't share it, because [it belongs to another account / of privacy rules], but I can [what you can do instead].
```

### You don't serve their area

_They're outside your delivery or service area_

```text
I'm sorry to say we don't [deliver / work] in [place] yet, and I know that's frustrating after you've found what you wanted. [Option, such as a pickup point or a sign-up to hear when we expand].
```

## Billing worries

Money worries need facts fast: the amount, the date, what it is, and when it resolves.

### An unexpected charge

_They don't know what a charge is for_

```text
An unexpected charge is alarming, so let's pin it down. The [amount] on [date] is [explanation]. If that doesn't match anything you ordered, tell me and I'll look into it today.
```

### Charged twice

_Two charges for one purchase_

```text
Seeing two charges for one order is worrying. The second is [a pending hold your bank will release / a duplicate I've refunded today]. It should be gone from your statement by [date].
```

### Money is tight

_They tell you they're struggling to pay_

```text
Thank you for telling me; that can't have been easy to write. Here's what I can offer: [payment plan / pause / smaller plan]. Take your time and tell me which works.
```

### Card declined

_Their payment failed and they're embarrassed or confused_

```text
A declined card is frustrating, and it's rarely anything you did. The bank gave the reason as [reason]. You can try another card here: [link], and your [order / account] stays [reserved / active] until [date].
```

### They fear fraud

_They think someone used their card or account_

```text
If you don't recognize this, you're right to check before anything else. Let's secure your account first: [steps]. Then I'll go through the charge with you.
```

### An invoice with the wrong details

_Their accounts team can't use the invoice_

```text
An invoice with the wrong [company name / tax ID] is no use to your accounts team. I've reissued it with [correction], and it's attached. Future invoices will use the new details.
```

## Technical problems

Acknowledge what the problem is stopping them from doing, not just the error.

### Locked out before a deadline

_They can't get in and time is short_

```text
Being locked out right before [deadline] is the worst timing. Let's get you in first and find the cause after: [first step].
```

### A bug is blocking their work

_They can't finish a task because of a fault_

```text
So [task] is stuck because of this, and your team is waiting on it. I've reproduced the error and sent it to our engineers as urgent. Meanwhile, [workaround] will get [task] done today.
```

### A problem that's hard to describe

_They struggle to explain what's wrong_

```text
Thanks for the screenshots; they show exactly what you mean. Problems like this are hard to put into words, and you've given me enough to start: [next step].
```

### Not a technical person

_They say they're not good with technology_

```text
You shouldn't need to know what [technical term] means to use [product]. Let's go one step at a time, and tell me where you get stuck. First: [step].
```

### A problem that comes and goes

_The fault is intermittent_

```text
Problems that come and go are maddening, because they never happen when you show someone. Next time it does, could you [capture the time / take a screenshot]? That gives us something solid to work with.
```

### Our update broke something

_It worked before your change_

```text
You didn't change anything, and [feature] stopped working after our update on [date]. That's on our side. Until the fix is out on [date], here's how to [work around it]: [steps].
```

### The cause is on their side

_Their settings or device cause the problem_

```text
Good news: nothing is broken on your account, so this should be quick to fix. The cause is [setting or device]. Here's the change to make: [steps]. If it's still wrong after that, I'll stay on it with you.
```

## Cancellations

Make leaving easy and respectful. The way someone leaves decides whether they come back.

### Leaving because of a problem

_They cancel after a bad experience_

```text
I'm sorry [problem] is why you're leaving. Your cancellation is done, and you won't be charged again. If you're willing to tell me one thing we should fix, I'll pass it to the team.
```

### Leaving because of cost

_They say it's too expensive_

```text
Cost is a fair reason. Your [plan] ends on [date]. If a smaller plan would cover what you need, [plan] is [price]. If not, no hard feelings, and your data stays [for period / until you delete it].
```

### Canceling was too hard

_They struggled to find how to cancel_

```text
You should have been able to cancel in one step. I've canceled it now, and I've [refunded the charge from after you first tried / confirmed nothing more will be charged].
```

### Their business is closing

_They cancel because the business is shutting_

```text
Closing [business] is a big step, and I'm sorry it came to that. I've canceled your account from [date]. Here's how to download your records first: [link].
```

### Thinking about leaving

_They haven't decided yet_

```text
Before you decide, can I ask what isn't working? If it's [common reason], there may be a fix. If not, I'll help you cancel without a sales pitch.
```

### Leaving on good terms

_They leave for reasons unrelated to you_

```text
Thanks for telling me, and for the time you spent with us. Everything is canceled from [date]. If you ever need [product] again, your [settings / history] will be here until [date].
```

## Urgent or personal situations

Slow down, keep it short, and take the work off them. Never a cheerful template here.

### A death in the family

_They're closing or changing an account after a death_

```text
I'm very sorry for your loss. I'll take care of [account / order] for you, and you won't need to explain any of this again. The one thing I need, whenever you're ready, is [document or detail].
```

### Illness or a hospital stay

_They tell you they're unwell or caring for someone_

```text
I'm sorry you're dealing with this. I've [paused / extended / moved] [service] until [date], and there's nothing you need to do now.
```

### Time-critical travel

_They're about to travel and something is wrong_

```text
You fly in [hours], so let's sort the urgent part first: [action]. The rest can wait until you've landed, and I'll have it ready for you.
```

### Their business is losing money

_Your outage is costing them sales_

```text
Every hour [system] is down costs you sales, and I'm treating it that way. [Name or team] is working on it now, and I'll update you every [interval] until it's fixed.
```

### A safety concern

_They report something that may be unsafe_

```text
Thank you for telling us straight away. Please stop using [product] now. If anyone is hurt, contact your local emergency services first. Then I'll arrange [replacement / refund / collection] and pass your report to [team].
```

### A hard change in their life

_They mention a job loss, a move or a family change_

```text
That sounds like a lot to deal with at once. Let's make this part simple: [option]. If it helps, I can [pause / change / move] it so it's one less thing to think about.
```

### An accessibility need

_They tell you what works best for them_

```text
Thanks for telling me what works best for you. I'll [write by email / call / send plain text] from now on, and I've noted it on your account so the rest of the team does the same.
```

## Positive moments

Empathy isn't only for problems. Match their good mood and be specific about what they did.

### A customer says thank you

_They praise you or a colleague_

```text
Thank you, that's good to hear. I'll pass it on to [colleague], who [what they did]. It means a lot to the team.
```

### A milestone

_They share an achievement, a launch or an anniversary_

```text
Congratulations on [milestone]. That's a lot of work behind it. We're glad [product] played a small part.
```

### A long-time customer

_Someone who has been with you for years writes in_

```text
You've been with us since [year], so you've seen [business] change a lot. Thank you for sticking with us. Here's the answer to your question: [answer].
```

### A first order

_Someone buys from you for the first time_

```text
Thank you for your first order, [customer name]. If anything about it isn't right when it arrives, reply to this email and you'll reach a person.
```

### They fixed it themselves

_They found the answer before you replied_

```text
Nice work finding that. Thanks for letting me know, so I don't send you on a hunt for something you've already solved. I'll [add your fix to our help page / pass it to the team].
```

### Good news after a problem

_The fix they waited for is done_

```text
Good news: [what is fixed]. Thanks for staying with us while we sorted it. If anything still looks off, reply here and I'll pick it straight back up.
```

### Helpful feedback

_They suggest an improvement_

```text
That's a useful idea, and the example of [their example] makes it easy to see why. I've passed it to the [team] with your words. I can't promise it will happen, but it will be read.
```

## What an empathy statement is

> An empathy statement is a sentence in a customer service reply that shows you understand what happened to the customer and how it affected them. A good one is specific: it names the problem, the time or money it cost them, or the plan it upset, and then moves straight to what you will do. "I understand your frustration" is not one. "You've explained this three times now" is.

Empathy statements are not a script to read in place of an answer. They are the one or two lines that make the rest of the reply land: the customer feels heard, so they read the facts that follow instead of skimming for the next thing to be angry about.

1. **Pick the situation.** Choose frustration, waiting, a mistake, bad news, billing, technical, cancellation, personal or positive, or search for a word such as "refund" or "late".
2. **Copy it, or personalize it.** Copy the statement, or press Personalize and add the customer's name, your business and what happened. The AI fills the slots it can and keeps the rest in brackets.
3. **Add the facts and the next step.** An empathy statement opens the reply. Follow it with the answer and one clear next step, with a time.
4. **Or add empathy to your own draft.** Open the Add empathy to my reply tab, paste a reply you wrote, and get a version that acknowledges the problem once and keeps every fact you wrote.

## What makes empathy sound real

Customers can tell a phrase from a script from a sentence written about them. These are the differences.

- Be specific. Name the order, the date, the number of times they wrote. "You've waited since Tuesday" beats "I know waiting is hard".
- Name the impact, not just the event. The late parcel is the event; the missed birthday is the impact.
- Match their intensity. A calm question needs a light touch; a ruined event needs a serious one. Cheerful language next to bad news reads as not listening.
- Say it once, near the start. Empathy repeated in every paragraph starts to sound like padding.
- Follow it with action in the same message. Empathy without a next step sounds like a stall.
- Don't follow it with "but". "I see why that's annoying, but our policy says…" cancels the first half. Use a full stop and start a new sentence.
- Don't claim feelings you can't know. "I know exactly how you feel" invites "No, you don't".
- Use their words. If they said "the app keeps logging me out", say that, not "you're experiencing an authentication issue".

| Part | What it does | Example |
| --- | --- | --- |
| What happened | Shows you read the message | Your order arrived two days after the party. |
| What it cost them | Shows you see the impact | So the gift wasn't there when it mattered. |
| What you'll do | Turns empathy into help | I've refunded the delivery charge and the gift wrap today. |

## Phrases to avoid, and what to say instead

Most of these phrases started out kind. They have been used so often, and so often without any action after them, that many customers now read them as a sign nobody is really listening.

| Avoid | Why it falls flat | Say instead |
| --- | --- | --- |
| I understand your frustration. | Generic; it could be pasted into any reply | You've now been charged twice and waited a week for an answer. |
| We apologize for any inconvenience. | "Any" suggests you don't know what went wrong | Sorry we sent the wrong size. The right one ships today. |
| Thank you for your patience. | They didn't choose to wait | You've waited four days for this, which is too long. Here's the answer. |
| I'm sorry you feel that way. | Blames their feelings, not the problem | I'm sorry the repair didn't fix it. |
| As I said before… | Sounds like a reprimand | To put it another way: … |
| Unfortunately, that's our policy. | Hides behind a rule with no reason or option | We can't refund after 30 days because [reason]. What I can do is [option]. |
| Calm down. | Has never calmed anyone down | Let's sort this out. First, [action]. |
| Rest assured… | A promise with nothing behind it | I'll check again on Friday and write to you either way. |
| I know exactly how you feel. | You don't, and they know it | If that happened to me, I'd be annoyed too. |

## Before and after: empathy added to real replies

Each "after" keeps every fact from the "before". Only the opening and the close change.

**After: a refund that hasn't arrived**

```text
Hi Daniel, I know it's worrying when money leaves your account and doesn't come back on time. We sent your refund on 3 October, reference RF-20931. Banks usually take 5 to 10 business days to show it, so it should appear by 17 October. If it isn't there by then, reply here and I'll chase it with our payment provider the same day.
```

Before: "Your refund was processed on 3 October. It takes 5 to 10 business days. Please contact your bank if you don't see it."

**After: a feature that doesn't exist**

```text
Hi Mei, being able to export straight to your accounting software would save you a lot of copying, and I wish I could say yes. It isn't possible today. The closest option is the CSV export under Reports, which your accounting software can import. I've passed your request to the product team with your example.
```

Before: "This feature is not available at this time. We will consider it for future releases."

**After: a third message about the same outage**

```text
Hi Tomasz, this is the third time you've had to write about the connection dropping, and you shouldn't have had to chase us. I've booked an engineer for Friday between 9 and 12, and I've credited one month to your account for the days it wasn't working. I'll call you on Friday afternoon to check it's fixed.
```

Before: "An engineer visit has been scheduled for Friday 9-12. A credit has been applied to your account."

**After: saying no to a late return**

```text
Hi Grace, I can see you were hoping to return the jacket, and I'm sorry this isn't the answer you wanted. It was delivered 45 days ago, and our return window for a change of mind is 30 days, so I can't refund it. If something is wrong with it, tell me what, because a faulty item is handled differently.
```

Before: "Your return request has been declined as it is outside the 30-day return window."

## The "Add empathy to my reply" tab

Sometimes you've already written the reply, and it reads cold. Paste it into the Add empathy to my reply tab, add the customer's name and your business if you like, and the AI rewrites it. You get a draft to read and adjust, not a reply to send unread.

**What the rewrite does**
- Names the customer's problem or feeling once, in plain words
- Apologizes only for what actually went wrong, at most once
- Uses the customer's name once if you give it
- Ends with one clear next step

**What it never does**
- Change or drop a fact, a number or a date from your draft
- Add a promise, a refund or a discount you didn't write
- Make the reply much longer
- Use stock lines such as "I completely understand your frustration"

Each statement in the library also has a Personalize button. Add the customer's name, your business and what happened, and the statement is filled in for that one conversation. Slots you give no fact for stay in brackets, so check for any brackets before you send.

## Empathy by channel

| Channel | How empathy shows | Watch for |
| --- | --- | --- |
| Live chat | One short line, then the answer. Speed is part of the empathy. | A long paragraph of feelings while they wait for the fact |
| Email | One or two sentences at the start, and a next step with a date at the end | Burying the answer under the apology |
| Phone | Let them finish, say back what you heard, then speak more slowly | Interrupting with the fix before they feel heard |
| Public reviews and comments | Acknowledge the problem in one line, then offer to continue privately | Arguing the facts in public or sharing order details |
| Text and WhatsApp | Short and plain; one acknowledgment is enough | Several messages of apology before the answer arrives |

## Common mistakes

- Empathy instead of an answer. Three sentences of understanding and no fix make people angrier, not calmer.
- The same statement every time. Regular customers notice when every reply opens with an identical line.
- Apologizing for things that weren't wrong. Save the apology for real mistakes, so it means something when you use it.
- Making it about you. "I've had a long day too" moves the attention away from their problem.
- The wrong tone for the moment. An upbeat line next to a bereavement or a safety report reads as careless.
- Promising what you can't deliver to make someone feel better now. They feel worse when it doesn't happen.
- Assuming feelings. "You must be furious" can be wrong; describing what happened is always right.

## How an AI agent handles upset customers on your website

An AI customer service agent answers from your own website pages and documents, in the tone you choose. When a visitor is upset, the useful empathy is the same as for a person: say what happened in their words, give the fact, and move to the next step. The agent doesn't invent policies or promises, and you choose topics that always go to a person, such as complaints or refunds, so a human picks those up with the whole conversation in front of them.

*A visitor on a home internet provider's site, on a Sunday evening*

Visitor: third time this week my internet has cut out. i work from home, this is ridiculous

Chatbot: Three drop-outs in a week is a real problem when you work from home. Our service status page shows no outage in your area right now, so it may be your line or your router. The troubleshooting page suggests restarting the router first. Would you like me to pass this to the team to book a line check? _(Searched knowledge: connection dropping)_ _(From the page: Service status and troubleshooting)_

Visitor: yes. and i want something back for the days it was down

Chatbot: I've passed both to the team: the line check and your request for a credit. They're back at 8 am Monday and will reply here and by email. _(Handed to a person: complaint)_

**Calm, specific answers on your website, day and night** Build a support agent from your own pages. It answers what your site covers and hands complaints to your team. [See the AI customer service agent](https://luckpanda.app/chatbot/ai-customer-service-agent)

## Questions people ask

### What are empathy statements in customer service?

They are short sentences that show the customer you understand what happened to them and how it affected them, before you give the answer. Good ones are specific to the situation and are followed by an action in the same message.

### What are some examples of empathy statements?

"You've now explained this three times, and you shouldn't have had to." "Waiting for money to come back is stressful." "You need this by Friday, so a vague estimate won't help." Each one names the customer's actual situation rather than a general feeling.

### What should you not say to an upset customer?

Avoid "Calm down", "I'm sorry you feel that way", "As I said before" and "That's our policy" with no reason or option. Generic lines such as "I understand your frustration" and "We apologize for any inconvenience" also tend to sound scripted.

### What is the difference between empathy and sympathy in customer service?

Sympathy says you feel sorry for the customer. Empathy shows you understand their situation from their side, and in service it usually comes with action: you name what happened, what it cost them and what you will do about it.

### Should you apologize in every empathy statement?

No. Apologize once, and only when something actually went wrong on your side. You can acknowledge a problem you didn't cause, such as a carrier delay, without apologizing for it.

### Can a chatbot show empathy?

An AI agent can acknowledge what the visitor said in plain words, keep the tone you set and move quickly to an answer or a person. It should not pretend to have feelings. For complaints and sensitive topics, the better design is to hand the chat to a person.

Try it on your website: https://luckpanda.app/chatbot/try
