32 Empathy Statements for Customer Service in Text

TL;DR: empathy statements for customer service are usually written as phone lines, and they break when you type them. In writing there is no tone of voice to carry them, so a line that sounds warm out loud reads as stalling on a screen. The 32 statements below are grouped by channel — live chat, email, text and WhatsApp — plus the lines an AI should send in a first reply and at a handoff, and the lines an AI should never send at all. Every one follows the same four-part shape: name the specific thing, say what happens next, say who, and give one next step.

This page is about wording — what to type, in which channel, and where an automated responder has to stop typing and fetch a person. It is written from cove1, a message-based AI support system for chat, email and messaging apps; it does not answer phone calls, so every line here is one somebody types. It is not an after-hours process document. If the open question is which contacts wake somebody at 2am and which wait until morning, our guide to writing an after-hours support SOP does that job, and this page supplies the sentences that SOP sends.

The four parts of an empathy statement that works in writing

Empathetic statements survive out loud because tone carries them. Typed empathy has no tone, so it has to be carried by specifics. Every line below is built from four parts, and a line that drops a part is usually the line that gets the angry reply.

• Name the specific thing, not the emotion. "A leak over your bed" beats "your frustration." Naming the thing proves you read the message; naming the emotion only proves you have a template.
• Say what happens next. A sentence of sympathy with no next action reads as a delay tactic in text, because the reader cannot see you doing anything.
• Say who. "Someone will look at this" is worse than "Dana is looking at this." Text readers assume an unnamed someone is nobody.
• Give exactly one next step, or none. If there is nothing for them to do, say so explicitly. Two asks in one message is how a thread turns into five.

The order matters less than the completeness. What does not work in writing is part one alone, which is what most empathy statement lists are: a stack of sympathetic openers with nothing behind them.

Why empathy statements for customer service read differently in text

On a call, an agent can pause, soften, and repair a clumsy sentence in real time. In a typed thread none of that exists, and three things change.

Time becomes the whole message. A caller hears you working. A reader sees a silent thread, so an empathy line without a named time — "by Thursday", "in ten minutes", "tonight between 7 and 9" — is read as nothing happening.

Everything is on the record. Chat transcripts and emails get forwarded, screenshotted and attached to complaints. A line that overpromises in speech is forgotten; the same line typed becomes evidence. This is why the statements below avoid admitting fault for anything you have not verified.

Repetition is visible. A reader can scroll up. Saying "I understand your frustration" twice in one thread is obvious on screen in a way it never is on a call, and it is the single fastest way to look automated.

Most published lists of empathy statements for customer service are written for voice. The AnswerConnect list that held position 2 for this query in a Semrush US export dated 8 September 2026 is a good example: across its full page text, the words chat, email, phone and SMS each appear zero times (answerconnect.com, accessed 11 September 2026). Chat-specific lists do exist — Freshworks publishes one with six ways to express empathy and twenty statements (freshworks.com, accessed 11 September 2026). The four pages we opened on 11 September 2026, those two plus Call Centre Helper and Qualtrics, are the published wording we worked from. This page is written for a different job. What an automated responder should say in its first message, what it should say when it hands over, and what it must never send each gets its own section below, alongside chat, email and text versions of every line.

Empathy statements for live chat

Live chat is watched in real time. The reader is looking at a typing indicator, so length costs you more here than anywhere else. Keep each message to one idea and send the next one rather than writing a paragraph.

1. "That is a frustrating thing to hit on a Friday. Give me a moment to pull up the account and I will tell you exactly where it stands."

2. "You should not have had to ask twice. Both of your earlier messages are here, so you do not need to repeat anything."

3. "I can see why that looks like a charge you never agreed to. Let me read the note on your file before I say anything else."

4. "That is a fair question and I do not want to guess at it. I am checking the policy now rather than giving you a maybe."

5. "This has taken up your whole morning already. Here is what I can do in the next five minutes, and here is what will take until tomorrow."

6. "I am sorry — that one is on us. I am going to fix the part that affects you first and explain the cause afterwards."

7. "Thanks for staying with me while I checked. The short answer is below, and I will put it in writing so you have it."

8. "I would rather tell you now that I cannot fix this myself than keep you here another ten minutes. I am bringing in Dana, who can."

Empathy statements for email

Email is read hours later, often on a phone, often by someone who has cooled down or boiled over since writing. The reply has to survive being read cold, so it carries the context the chat lines can leave out.

9. "I read your message twice before replying, because you raised two separate problems and I did not want to answer only the easy one."

10. "You wrote on Saturday and this is the first reply you have had. That delay is ours. Here is where things stand now."

11. "I am sorry about the disruption to your week. Below is what has already changed, and below that is the one thing I still need from you."

12. "I do not have a full answer yet. I am sending this anyway so you are not waiting in silence, and I expect the full answer by Thursday."

13. "You are right that our own documentation says something different. I have flagged that page for correction and I am honoring what it said."

14. "This should be the last email you need to send about this. If it is not, reply here and it comes straight back to me."

Empathy statements for text and WhatsApp

Text arrives as a notification, often at a bad moment, and is read on a small screen. Long messages get skimmed to the last line, so put the outcome there. Note one platform constraint worth designing around: on the WhatsApp Business Platform, a message or call from a customer starts a 24-hour timer that Meta calls a customer service window, and each new customer message restarts it. Inside it you can reply without a template; once it lapses, only pre-approved template messages go out (Meta developer documentation, accessed 11 September 2026). An empathy line that promises a follow-up "tomorrow" may have to arrive as a template.

15. "Got it, and that does sound urgent. I am getting someone to you now — stay on this thread."

16. "Sorry you are dealing with this in the rain. A visit is booked for between 7 and 9 tonight."

17. "That is a rough way to start a Monday. Nothing more is needed from you; I will message when it is done."

18. "I know this is your third message today. All three have been read. Give me ten minutes."

19. "You do not have to explain it again. The photos you sent are enough."

20. "I cannot promise tonight, and I would rather say that than leave you waiting for a knock."

What an AI should say in its first reply and at the handoff

This is the part missing from every one of the four lists we opened. If an automated responder answers first, the empathy problem changes shape: the reader's first question is not "do you care", it is "am I talking to a machine, and will a person ever show up".

Say so in the first sentence. There is also a legal reason in at least one state, though a narrower one than it is usually quoted as. California's B.O.T. Act makes it unlawful to use a bot to communicate with someone in California online, with the intent to mislead them about its artificial identity for the purpose of knowingly deceiving them about the content of the communication, in order to incentivize a sale or influence a vote — and it removes that liability outright for anyone who discloses that it is a bot. Where a disclosure is made, the statute says it must be "clear, conspicuous, and reasonably designed to inform" (Cal. Bus. & Prof. Code § 17941, accessed 14 September 2026). The narrow rule is not the point. The practical one is that disclosure is the cheapest way to make the question moot, so treat it as the default everywhere rather than a jurisdiction-by-jurisdiction decision. This page is operational guidance, not legal advice — run your own disclosure and escalation wording past whoever handles compliance for your business.

21. First reply: "You are messaging our automated assistant. I can answer most questions right now, and if I cannot, I will bring in a person."

22. Emergency detected: "That is a hard thing to come home to. This is logged as an emergency and the on-call manager has been paged. They will reply in this same thread."

23. Low confidence: "I am not confident enough to answer that one, and a wrong answer here would cost you money. I am passing it to Dana with everything you have told me."

24. Customer asked for a person: "Asking for a person is a fair thing to want. Dana is picking this up and already has the whole conversation."

25. Person taking over: "Hi, this is Dana. I have read the whole thread, so carry on from where you left off rather than starting again."

26. Handing back: "Dana has settled the billing part. I am taking the thread back for routine updates and will fetch her again if anything changes."

Two of those depend on the system underneath, not the wording. The handover only reads as continuous if the person receives the full history, not just a summary, and the escalation triggers have to be written down in advance — an explicit request for a human, a question outside scope, a sensitive topic, or low confidence. Our post on how an AI decides when to hand off covers the mechanics behind lines 23 to 26.

Empathy statements an AI should never send

An automated responder that produces the right sympathetic words in the wrong situation does more damage than silence. These categories are not "handle carefully". They are "stop and fetch a person", and the fetch should happen on the first signal rather than after a few exchanges.

The general rule behind the table: an automated responder may express regret, and may never express commitment. Apology is free; a promise is a liability.

Property management and HOA examples

Generic retail examples do not transfer to a tenant with water coming through a ceiling, so here are the six that actually come in overnight for residential and community-association teams.

27. Leak: "Water coming through a ceiling counts as an emergency under our rules. If you can reach the stop tap safely, turn it off. The on-call maintenance contact has been paged."

28. Noise: "Being kept awake at 1am is not something you should have to absorb. This is logged with the time and the unit so the pattern is on record, and the manager reads it first thing."

29. Violation notice: "A violation notice arriving without warning is upsetting. I can tell you what it refers to and what the appeal window is. I cannot decide the outcome, and I will not pretend otherwise."

30. Dues dispute: "I understand why that balance looks wrong to you. I am not going to argue the figure over chat. It has gone to the community manager with your ledger attached."

31. No heat: "No heat with a young child in the unit sits at the top of the list. This is escalated, and I am staying on this thread until someone confirms a time with you."

32. Access for a repair: "Letting a stranger into your home is an intrusion, and it is fine to say so. Here is exactly who is coming, when, and what they will do. If that time does not work, say so and it moves."

The pattern to copy is line 29. It says the sympathetic thing, then draws a boundary in the same breath. Empathy statements that promise beyond the responder's authority are the ones that produce the second, angrier message. Community-association wording lives closest to that line, which is why our HOA answering service page answers dues, ARC and rules questions straight from each association's governing documents with the source cited, and routes anything that needs interpretation, board discretion or legal judgment to a person instead.

Spanish and English pairs

If part of your resident or customer base writes in Spanish, the empathy line has to be written in Spanish rather than translated word for word at send time, because the register drifts. These are five of the lines above, trimmed to one sentence each and paired.

Two practical notes. Keep a glossary of terms that must not be loosely translated — unit names, plan names, defined terms from governing documents — because that is where machine translation quietly changes meaning. And when a Spanish thread escalates, the person picking it up should receive the sender's original words alongside an English rendering, not a translation that replaces the original. Our bilingual answering service page describes how that handoff is put together; it is written around the Spanish and English pair, and any language we have not tuned for a deployment we describe as untested rather than supported.

Empathy mistakes that make the thread worse

If you want a fast diagnostic, read your last twenty outbound messages and mark every one where the reader would still not know what happens next. That percentage, rather than the sympathy vocabulary, is what your empathy statements are actually worth. Reducing the follow-up messages those gaps generate is the same problem covered in our post on cutting ticket volume without stonewalling customers.

Where cove1 fits, and where it does not

cove1 is a message-based AI support system: web chat, email, WhatsApp and the other messaging channels a deployment connects, all landing in one console. It answers from your own documents with the source cited, and escalates to your on-call people when the customer asks for a person, when retrieval finds nothing relevant, when the topic is sensitive, or when its confidence is low. The person who picks up gets the full history alongside the structured summary, not a summary on its own, which is what makes lines 25 and 26 above readable rather than jarring. If you want the shape of the escalation rules themselves before you write the wording, our escalation matrix generator runs entirely in the browser and uploads nothing.

Where it does not fit: cove1 does not answer phone calls. There is no voice agent and no live receptionist on our side, so none of the spoken versions of these lines are ours to deliver, and the human in every handoff above is someone on your team, not ours. US SMS is a channel we connect rather than a switch we flip — the A2P 10DLC registration stays with you. Spanish and English is the pair we have productized; every language we tune for a deployment is named in writing, and anything not on that list we describe as untested. The disclosure line in statement 21 is wording we recommend, not a switch you flip in our product: cove1 ships no automatic "you are talking to an assistant" opener today, so that sentence has to be written into your agent's own first message. And the never-send table is a policy we hold rather than a setting you toggle: crisis, death notification and discrimination complaints go to a person by design.

If your after-hours threads look like the property and HOA examples above, the specifics are on the property management answering service page, and a demo is where the escalation rules get scoped against your own message history rather than a generic script. Bring your last thirty days of overnight messages; the wording follows the rules, not the other way around.

Frequently asked questions

What are empathy statements in customer service?

Empathy statements are short sentences that acknowledge what a customer is dealing with before, or alongside, the practical answer. In a typed channel they need more than acknowledgement to work: a usable statement names the specific problem rather than the emotion, states what happens next, names who is doing it, and gives at most one next step for the customer. The version that survives being screenshotted and forwarded is the one with a time in it. Sympathy without a time reads as delay, and readers respond to it by sending another message. So when you borrow empathy examples for customer service from a script written for the phone, supply the part a live pause used to cover: a named time, a named owner, or an explicit "I do not know yet, and I will tell you by Thursday."

How many empathy statements should an agent actually memorize?

Far fewer than any list suggests, including this one. The four-part structure at the top of this page matters more than the inventory, because a memorized line applied to the wrong situation is worse than an improvised one. Lists of empathetic statements for customer service are inventories, and an inventory is not a skill. A practical approach is to pick two per channel that fit how your team already writes, put them in your canned-response tool, and let everything else be assembled from the structure. Teams that paste thirty statements into a macro library usually end up with three in rotation and twenty-seven that make the thread sound stitched together from different people.

Should an AI chatbot say that it is an AI?

Yes, in the first sentence, and for two reasons. Practically, a reader who works out mid-thread that they were talking to software rereads every earlier sympathetic line as manipulation, and the repair costs more than disclosure would have. Legally, California's B.O.T. Act gives anyone who discloses a complete defense to its bot-deception provision, and Utah's S.B. 226 (2025) requires a supplier using generative AI in a consumer transaction to confirm it is not a human when the customer asks (Utah S.B. 226 enrolled text, accessed 14 September 2026). Rules differ by state, and this is operational guidance rather than legal advice: run your wording past whoever handles compliance. The better pattern is to disclose and immediately say what happens next: what the assistant can answer, and that a person is available. Disclosure paired with a route to a human reads as competence; disclosure alone reads as a warning label.

How do you show empathy without saying sorry?

Say the specific thing instead of the feeling, then say what happens next. "Your invoice was charged twice on Tuesday and I am pulling the record now" acknowledges the problem without conceding a cause nobody has established yet. Empathy statements without saying sorry are not evasive, they are precise: a lot of published lines open with an apology for exactly the kind of unverified cause nobody has pinned down yet, and in writing an apology is very hard to walk back once it has been forwarded. Keep sorry for the cases where the fault is yours and known. Carry the rest with the specific thing, a named owner and a time, which is what the reader wanted from the apology in the first place. Acknowledging a fact is not the same as accepting liability.

What empathy statements should an AI never send?

Anything that commits money or legal position, and anything in a crisis. Refunds, waivers, credits, rent abatement, admissions of fault, statements about a legal deadline, and medical reassurance all belong to a person with the authority to make them. Self-harm and acute crisis conversations, death notifications, and fair-housing or discrimination complaints should be detected and bridged to a human on the first signal rather than after a few exchanges. The workable rule is that an automated responder may express regret but never commitment: it can say it is sorry, and it cannot say what will be done about it beyond who is now involved.

How do empathy statements differ between chat, email and text?

Length, timing and permanence. Live chat rewards one idea per message because the reader is watching a typing indicator, so a paragraph reads as a stall. Email is read cold hours later, so it has to restate enough context to stand on its own and should name a date rather than a duration. Text and WhatsApp arrive as interruptions on a small screen and get skimmed to the last line, so the outcome goes at the end and the whole message stays under about two lines. Platform rules matter too: WhatsApp's 24-hour customer service window decides whether a follow-up can be free-form or has to be a pre-approved template.