Empathy statements for customer service that don't sound scripted
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.
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 themselvesThe customer has explained the same problem more than once
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 teamsThey've been transferred or redirected several times
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.
Waiting and delays
Swap "thank you for your patience" for what the wait actually cost them, and a firm next date.
- Delivery is lateAn order missed its delivery date
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 youThey waited a long time in chat or on the phone
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].
Mistakes we made
Own it in plain words, say sorry once, and put the fix in the same message.
- Wrong item sentYour packing or ordering error
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 amountA billing error on your side
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.
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 giveThe request is outside your policy
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 haveThey need something the product doesn't do
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].
Billing worries
Money worries need facts fast: the amount, the date, what it is, and when it resolves.
- An unexpected chargeThey don't know what a charge is for
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 twiceTwo charges for one purchase
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].
Technical problems
Acknowledge what the problem is stopping them from doing, not just the error.
- Locked out before a deadlineThey can't get in and time is short
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 workThey can't finish a task because of a fault
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.
Cancellations
Make leaving easy and respectful. The way someone leaves decides whether they come back.
- Leaving because of a problemThey cancel after a bad experience
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 costThey say it's too expensive
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].
Urgent or personal situations
Slow down, keep it short, and take the work off them. Never a cheerful template here.
- A death in the familyThey're closing or changing an account after a death
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 stayThey tell you they're unwell or caring for someone
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.
Positive moments
Empathy isn't only for problems. Match their good mood and be specific about what they did.
- A customer says thank youThey praise you or a colleague
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 milestoneThey share an achievement, a launch or an anniversary
Congratulations on [milestone]. That's a lot of work behind it. We're glad [product] played a small part.
Nothing matches. Try another word.
Your result appears here.
Written by AI. Read it before you send it.
Build a support agent from your site
Your own AI agent answers questions like this on your website, day and night, from your own pages and documents, and passes the hard ones to you. Paste your address to see it learn your site. No account needed.
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.
- Pick the situationChoose frustration, waiting, a mistake, bad news, billing, technical, cancellation, personal or positive, or search for a word such as "refund" or "late".
- Copy it, or personalize itCopy 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.
- Add the facts and the next stepAn empathy statement opens the reply. Follow it with the answer and one clear next step, with a time.
- Or add empathy to your own draftOpen 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.
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."
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."
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."
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 |
| 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
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 agentQuestions 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.
Related pages
- Canned responses libraryOver 70 copy-ready canned responses for customer service, by situation, with a tab that rewrites your own reply.
- De-escalation script generatorDescribe an upset customer's situation and get a step-by-step script for chat, email or phone.
- Support ticket response templates60 copy-ready ticket replies sorted by ticket type, from the first response to closing, with slots to fill.
- AI reply generatorPaste a message and get three replies to send, for email, chat, DMs, comments, reviews or texts.
- AI customer service agentAnswers from your help pages and live order data, says when it does not know, and hands the chat to a person.
Build it with your AI agent
Give an agent your site and it can create the chatbot, read your pages and test it through LuckPanda's API and MCP. It prepares the work; going live stays with you.
Use LuckPanda's MCP server (https://luckpanda.app/mcp) to build a website chatbot for me. Ask for my website address, call chatbot_create_from_website with it, wait until the pages are learned (chatbot_source_list), then run a few test questions with chatbot_test_message and show me the answers. Do not put it live: I will do that myself.
Instructions for AI agents
Needs a LuckPanda agent key (Settings › Developers) with the chatbot.manage grant. MCP endpoint: https://luckpanda.app/mcp (Streamable HTTP, bearer key).
chatbot_create_from_website{ url }: creates a draft chatbot named after the site and starts reading it.chatbot_source_list: pages learned, failed or skipped, with a reason for each.chatbot_test_message: asks the bot a question as the owner. Test chats never email anyone.- Going live (
chatbot_updatewith status live) is a person's action; an agent gets APPROVAL_REQUIRED.
Try it on your website
Paste your address and watch the chatbot learn your pages. No account and no card.
This page in other languages