Customer service phrases that sound like a person, not a policy
Paste an agent reply or a stock phrase and get it back with positive scripting: same facts, same answer, framed around what the customer can do next.
This is the Customer Service Phrases snippet. In Snippetbar, draft your reply in Zendesk or Intercom, select it, and rewrite it in place before you hit send.
Customer service phrases: what to say instead
Saying no
| Instead of | Try | Why |
|---|---|---|
| We can't do that. | That's not something we offer, but here's what we can do: {alternative}. | The answer is still no. The customer just hears it next to an option. |
| Our policy states refunds are only available within 30 days. | Refunds cover the first 30 days after purchase, and this order is past that window. | “Our policy” sounds like a wall. The plain rule sounds like a fact. |
| Unfortunately, that feature isn't available on your plan. | That feature is part of the Pro plan. Here's what's included: {link}. | Lead with where the feature lives, not with “unfortunately”. |
| There's nothing I can do. | Here's what happens from here: {what the customer can expect}. | Describe the outcome. Don't add a promise you can't keep. |
Setting expectations and waiting
| Instead of | Try | Why |
|---|---|---|
| You'll have to wait 5–7 business days for the replacement to ship. | Your replacement ships within 5–7 business days. | Same timeline, framed as what's happening, not as a burden. |
| I can't give you a date, engineering hasn't told us anything. | Engineering hasn't shared a date for the fix yet. I'll update you by {day}. | Honest about the gap. The update time is yours to set, so set one you'll keep. |
| Hold on. | I'm checking your order now. This will take about two minutes. | Tells them what you're doing and for how long. |
On the phone, say the wait out loud before you go quiet. In chat, give a number: “about 2 minutes” beats “one moment” every time.
Transferring and escalating
| Instead of | Try | Why |
|---|---|---|
| That's not my department. | Billing handles this, and they'll reply to you here. | Who can help and what happens next, in one line. |
| Please hold while I transfer you. | I'm transferring you to {team}. I've shared your details, so you won't need to repeat them. | Only say the second part if it's true. When it is, it's the whole point. |
| I'll have to escalate this. | I'm passing this to our {team} team, who can {what they can do}. | “Escalate” is internal jargon. Say who and why. |
Asking for information
| Instead of | Try | Why |
|---|---|---|
| You didn't include your order number. | Just send your order number and I can look into this. | Asks for what's needed with no fault attached. |
| As per my previous email, you need to clear your cache. | Here's how to clear your cache: {steps or link}. Once that's done, reply here. | “As per my previous email” reads as “I already told you”. |
| What's the problem? | What were you trying to do when this happened? | Gets the steps to reproduce, not a vague summary. |
Closing a conversation
| Instead of | Try | Why |
|---|---|---|
| Is there anything else I can assist you with today? | Did that fix it on your end? | Checks the actual problem instead of reading a script. |
| We apologize for any inconvenience. | Thanks for sticking with this while we sorted it out. | Specific thanks beats a blanket apology for something unnamed. |
| Closing this ticket due to no response. | I'll close this for now. If it comes back, reply here and it reopens. | Same action, and the customer knows the door is open. |
In email, one closing line is enough. In live chat scripts, confirm the fix before you close, because the customer can't see you wrapping up.
Phrases to avoid in customer service
| Avoid | Why | Say instead |
|---|---|---|
| “Calm down.” | It never works and tells them they're the problem. | “Let's get this sorted.” |
| “To be honest…” | Implies the rest wasn't. | Just say the thing. |
| “You're wrong.” | Starts an argument about who's right. | “Here's what I'm seeing on our side.” |
| “I'm just the messenger.” | Distances you from the answer. | “Here's where this stands.” |
| “Kindly revert.” | Stiff, and unclear to many readers. | “Reply here when you can.” |
| “Per our records…” | Sounds like evidence against them. | “Your account shows…” |
What makes good customer service phrases
Lead with what the customer can do
That's the whole idea of positive scripting. The facts don't change, only the order. Put the option first and the limit second, and the same no reads as help.
Keep the answer honest
Positive doesn't mean yes. If the refund window closed, say so. A rewrite that hints at an exception you can't give creates a second, angrier ticket.
Give the reason, not the rulebook
“Our policy states” asks the customer to respect a document. “Refunds cover the first 30 days” just tells them how it works. If there's no real reason, say the rule plainly and move on.
Drop the robot words
“We apologize for any inconvenience”, “kindly” and “as per” read as copied from a macro, because they usually are. Customers notice, and trust the rest of the reply less.
Match the channel
Live chat wants short lines and a time estimate for every pause. Phone needs you to say out loud what you're doing. Email can carry steps and links, but still needs one clear next action.
The snippet
This is the exact prompt the tool above runs. Save it as a snippet in Snippetbar and it works on any text you select.
You are a support lead who coaches agents on positive scripting. Rewrite the customer service reply or phrase below so it sounds like a helpful person, not a policy: same facts, same answer, positive framing.
Rules:
- Keep every fact, number, date and policy, and keep the actual answer. If the answer is no, it stays no.
- Add nothing new: no refunds, exceptions, reasons, offers or requests the text doesn't contain.
- No new promises. The agent decides what to commit to, so never add "right away", "I'll keep an eye on it", "I'll keep you posted" or "I'll share an update" unless the original says it.
- Open with what the customer can do, what you're doing, or what happens next. State a no once, briefly, with the reason if the text gives one ("Refunds cover the first 30 days after purchase, and this order is past that window").
- "You need to" / "you have to" becomes a friendly instruction ("Just send…", "Here's how…").
- "Our policy states" / "unfortunately" becomes the plain reason. If the text gives no reason, don't invent one.
- Blame ("you didn't", "you failed to") becomes what's needed next, with no fault assigned.
- "There's nothing I can do" becomes a plain statement of what the customer can expect, and nothing more.
- "I don't know" / "that's not my department" becomes who can help and what happens next ("Billing handles this, and they'll reply to you here").
- Cut robotic filler: "we apologize for any inconvenience", "as per", "kindly", "is there anything else I can assist you with today". At most one apology, and only if something actually went wrong.
- Warm, but no scripted empathy ("I completely understand your frustration") unless the original has it.
- Where the positive version needs a specific the text doesn't give (a link, a date, a name, an alternative), write it as a {placeholder}.
- Keep the channel and length: a chat line stays a chat line, an email stays an email. Keep any greeting and sign-off.
- If the input is a single stock phrase, return one reusable phrase. A bare "we can't do that" becomes what you can do, with the specifics as {placeholders}.
- Plain words, short sentences, contractions. Say each fact once. No exclamation marks.
Example:
Before: "You'll have to wait 3 days for the refund, there's nothing I can do. Unfortunately you didn't select express."
After: "Your refund will reach your account within 3 days. Express refunds are available when you choose express at checkout."
Return only the rewritten reply, in the same format. No other text.Use it where you work
In your help desk
Write the reply the way it comes to you in Zendesk, Intercom or Help Scout, select it, and run the snippet. The positive version replaces your draft before the customer sees it.
On your saved replies
Old macros are where “we apologize for any inconvenience” lives. Open each one, run the snippet, and your customer service scripts get fixed once instead of every ticket.
In Mail
For the escalated email to a customer who has written three times, select your draft and get a version that says no clearly and points to what happens next.
More snippets
All snippets →Empathy statements
Paste a blunt or defensive support reply and get the same answer with specific, human empathy statements in front of it. The facts and the fix stay exactly as they were.
Thank you for your patience
“Thank you for your patience” is polite, but on its own it says nothing. Paste a reply that leans on stock phrases and get one that thanks the customer for something real, says what happened and what happens next.
Customer service email templates
Paste your rough notes or a draft reply, pick the situation, and get a clear, friendly customer service email with the answer up front and one next step.
Questions
Run it in any app
Select the text, pick Customer service phrases from the menubar or press its shortcut, and the result replaces it in place.
Better replies, before you hit send.
Snippetbar runs your snippets on anything you copy, in any Mac app. $29, one-time purchase.