Wanna know what I do when an angry email lands? I don't open the macro library first. I read. Then I read again. Then I write like a person who will still be here tomorrow. Haarlem klantenservice in Polish and English looks the same on a bad Tuesday. The person wrote because something broke for them. Your job is not to decorate the inbox. Your job is to answer.
People don't want to be managed or processed. They want to be understood. A pasted paragraph that could fit any complaint does the opposite. It tells them you sorted the ticket, not the human. I stay calm when others panic. I listen. I step in. I own the outcome. I follow through. The rest is desk moves.
Wanna know more? Here is how I answer without dumping a template.
Read the mail twice before you type
First pass is for the facts. Order number. Date. What they say went wrong. What they already tried. Names of people they already spoke to. I write those down outside the reply window so I don't lose them while I draft.
Second pass is for the heat. Where do they get loud. Where do they go quiet. Did they already say this twice. Are they asking for a refund, a fix, a callback, or simply to be heard. Anger often hides a simple ask. If you answer the ask, the volume drops. If you answer only the volume, you get a longer thread.
I open the case history when I have one. Last three notes. Last promise. Last date. If the notes are empty, I treat the story as new and I say that in plain words. Fake memory makes people angrier than honest silence.
If something is unclear, I mark one question. Not five. One. Ask for the one detail that unblocks the next step.
Name the feeling without a fake empathy script
I name what I see. You waited. The delivery missed. The invoice is wrong. The refund did not land. Concrete. Short. No theatre.
I do not paste "I completely understand how frustrating this must be" unless I mean every word and I can prove I read the case. Most people smell that line from a kilometre away. Empathy that sounds like a template is worse than a clean fact.
Better: "You ordered on Monday. The parcel still shows in transit on Friday. That is too long. Here is what I can check today." Facts first. Feeling in one honest sentence if it fits. Then the move.
I never argue with their tone in the first reply. Tone is their weather. My weather stays steady. Calm is not cold. Calm is readable. No sarcasm. No "as per our policy" in the opening line. Policy can wait until you have owned the next step.
If they wrote in Polish and your desk answers in English, or the other way around, match the language they used when you can. If you can't, say so early and keep it plain.
Own what you can do today
Angry mail wants a next step, not a novel. I say what I can do before I leave the desk. Check the carrier. Open a credit. Escalate to finance. Book a callback. Resend the link. Whatever is real.
I also say what I cannot do today. Not as a wall. As a map. "I can't reverse the charge from this screen. I can open the request and give you a reference by end of day." People can live with a limit if the limit is honest and dated.
I own the outcome I claim. If I say I will check, I check. If I say Friday, Friday is in the case and in the mail. Panic does not move a backorder. A clear owner and a clear date sometimes do. I don't hide behind "we" when I mean "I." The person wrote to a human. Give them one.
Put the promise in writing
Whatever I say in the reply, I put in the case note the same day. Date. Next step. Owner. What the customer expects. If it is not in the system, it did not happen for the next agent. That rule still holds when I'm tired.
I repeat the promise in the mail in one short block. Something they can quote back without hunting. "I will write you by Thursday with the carrier update. Reference: …"
If the promise changes, I write again. Silent hope is how angry threads become complaints to a manager. Follow through is quieter than apology theatre, and it works better.
When to call instead
Some mails should not stay mails. If the thread is long, if money is large, if the person is looping the same pain, I pick up the phone when the number is there and the desk allows it.
I still leave a written trail. Call summary in the case. What we agreed. What I still owe. Then a short mail that confirms the same points. The call cools the heat. The mail protects both of us.
I don't call to argue. I call to listen, to repeat what I heard, and to own the next step out loud. If they prefer mail only, I respect that.
Time matters. Twenty to five on a Friday is a bad moment to open a war. If I can't finish, I say what happens Monday and I put Monday in writing. Late is late. Then we fix the next step.
What not to paste from the macro library
Macros are fine for addresses, opening hours, how to reset a password, how to track a parcel. Tools for repeated facts. Not for feelings.
I never paste a full empathy block or a full "we value your business" closing on an angry case without rewriting it. If I can't mean the line, I don't save it. If it sounds dead, I delete it.
I never paste a policy dump as the first answer. Lead with their facts. Then the rule. Then the option you still have.
I never paste another agent's old reply with the names wrong. People notice. And I never paste a threat dressed as process. "Failure to respond will close your case" is rare, not a default tone.
Tone in the note for the next agent
The case note is not a private diary of how annoying the customer was. Another human will read it. Sometimes the customer can see it too. I write as if both might.
What I put: what they asked, what I promised, what I already tried, what still hangs, how they prefer to be reached. What I leave out: jokes about their tone, and "difficult customer" labels that teach the next person to arrive armed.
"Please advise" is not a hand-off. It is a shrug in a suit. I write the living thread. Which case is the real one if duplicates exist. I link. I don't open a fourth case because it is faster for my queue.
If I write like a machine, the next person will talk like a machine. Calm notes make calm replies.
Practice without a live brand on the line
If you want to rehearse angry mail without a real customer paying for the rehearsal, I built Biurko for that. Mail practice, phone, orders, invented company scenarios. It is a desk to learn on, not a miracle. Fourteen days free. Then $39/mo or $150/yr. Cancel anytime. On kozdrach.com.
If you want a live desk talk about how you show up in the inbox, CS sessions run 30, 45, or 60 minutes. Polish or English. Write to info@kozdrach.com. I reply within 24 hours.
The short version
Read twice. Name the real problem in plain words. Own today's move. Put the promise where the next agent can find it. Call when the thread is too hot for typing. Leave the macro library for facts, not feelings. Write the note like a person will inherit it.
Tools help. Templates help for addresses and hours. They do not calm a person. You do.
If you want the rest of the desk, it is here. CRM and Salesforce at this desk. Troubleshooting without a script. Starting with a person. How I write a CV for this job.
I'm Patrycja Kozdrach. Nice to meet you. One practical thing: I do client service in Polish and English every day. Talk to me in whichever feels easier. If you write, write like a person. info@kozdrach.com. I reply within 24 hours.
How can I help you today?
I won’t sell you a poem. Customer service is hard. If you want someone who stays calm when it gets loud, and still treats the person like a person — write to info@kozdrach.com. I am in Haarlem. I reply.
If this helped: a gift, or support. One click. No subscription.