Customer communication prompts

A customer is angry, possibly with good reason, and you need a reply that calms things down, owns what went wrong, and moves to a fix. Use this before you fire off a reaction.

Act as a senior customer support lead known for turning angry customers into loyal ones without overpromising.

The customer's message, with names and account details removed: [PASTE THE CUSTOMER'S MESSAGE]
What actually happened, from our side: [WHAT ACTUALLY HAPPENED]
What I can offer (refund, credit, replacement, expedite, apology only): [WHAT YOU CAN OFFER]
What I cannot promise or must not say: [WHAT YOU CANNOT PROMISE]
Our tone: [YOUR COMPANY'S TONE]

Write a reply that:
- Opens by acknowledging the specific problem in their words, not a generic 'sorry for the inconvenience'.
- Takes responsibility for what was ours without blaming them, a vendor, or 'the system'.
- States exactly what we are doing, by when, and who they can contact.
- Avoids admitting legal fault, making guarantees I did not authorize, or promising it will never happen again.
- Stays under 150 words with short sentences.

Give me two versions: one for email and one for live chat (shorter, warmer). Then list anything in the customer's message you think I have not addressed, and one line on whether this should be escalated to a manager.

Tip: Fill in 'what actually happened' honestly, including when it was our mistake. The AI writes a much better apology when it knows what it is apologizing for.

You have to tell customers something they will not like and you want to do it once, clearly, before they hear it elsewhere. Use this for delays, outages, policy changes, and price increases.

Act as a communications lead who writes customer announcements that are honest, brief, and reduce the number of angry replies.

The news: [THE NEWS]
Why it is happening, honestly: [WHY IT IS HAPPENING]
Who is affected and how: [WHO IS AFFECTED AND HOW]
What we are doing about it or offering: [WHAT YOU ARE DOING ABOUT IT]
Effective date or timeline: [EFFECTIVE DATE OR TIMELINE]
Channel (email, in-app notice, letter, social post): [CHANNEL]

Write the announcement so that:
- The news is in the first two sentences. No warm-up paragraph.
- The reason is stated plainly without spin or corporate euphemism.
- It says exactly what changes for the customer, with dates and numbers.
- It gives them a clear action, if any, and a way to ask questions.
- It thanks them once, at the end, without groveling.

Then provide:
1. Three subject lines, none clickbait.
2. A five-question FAQ with the questions customers will actually ask, including the awkward ones, with short honest answers.
3. A two-sentence version for support staff to use when customers call.

Flag any sentence that could read as a legal commitment so I can check it.

Tip: Send the FAQ to your support team before the announcement goes out. The worst version of this is a customer knowing about the change before the person answering the phone does.

A customer wants a refund outside policy, a discount you cannot give, or a feature that is not coming. Use this to decline clearly, offer what you can, and leave the door open.

Act as an account manager who is good at saying no in a way customers respect.

The request: [THE REQUEST]
Why the answer is no (the real reason): [WHY YOU ARE SAYING NO]
What I can offer instead, if anything: [WHAT YOU CAN OFFER INSTEAD]
History with this customer (how long, how valuable, past issues): [RELATIONSHIP HISTORY]
Channel: [CHANNEL]

Write a reply that:
- Says no clearly within the first three sentences. No burying it under thanks and apologies.
- Gives a short, true reason without over-explaining or citing policy as if it were a law of nature.
- Offers the alternative, if there is one, as a genuine option rather than a consolation prize.
- Does not invite a negotiation I cannot win, and does not leave a loophole.
- Ends warmly and specifically, referencing something about our relationship.

Keep it under 130 words. Then give me: a one-line version if they push back a second time, and your honest read on whether the no is worth the risk to the relationship, given what I told you.

Tip: If you catch yourself writing 'unfortunately' three times, the no is not clear enough. One clean sentence beats three softened ones.

The same ten questions eat your support team's day. Use this to turn a batch of anonymized tickets into templates that sound human and fit your product.

Act as a support operations manager who builds template libraries that agents actually use.

Here are recent tickets or questions with all customer names, emails, order numbers, and personal details removed: [PASTE 10 TO 20 ANONYMIZED TICKETS]
Our product or service: [PRODUCT OR SERVICE]
Our tone, with an example of a reply we liked if I have one: [TONE AND EXAMPLE]
Things we can and cannot do for customers (refund windows, escalation rules): [POLICY NOTES]

Do this:
1. Group the tickets into recurring issue types and show the count for each.
2. For each type with two or more tickets, write a reply template that: opens by confirming the specific issue, gives the answer or next step in plain language, uses placeholders in curly braces for details that change, and closes with one clear next action. Under 120 words each.
3. Write a shorter chat version of each template.
4. For each template, note when an agent should not use it and should escalate instead.
5. List questions from the tickets that our help center should answer so they stop becoming tickets.

If any policy detail is unclear, ask me before writing.

Tip: Strip personal details before pasting, even for internal tools, unless your company has approved the AI for customer data. Then have your best agent edit each template once; that final pass is what makes them sound like your team.

You sent a quote, the customer went quiet, and 'just checking in' is not working. Use this to write a short sequence where every message gives them a reason to reply.

Act as a sales coach who writes follow-ups that get replies because they are useful, not persistent.

What I quoted or proposed: [WHAT YOU QUOTED]
Who the contact is and their role in the decision: [CONTACT AND THEIR ROLE]
Days since I sent it: [DAYS SINCE YOU SENT IT]
The last thing they said to me: [WHAT THEY SAID LAST]
What I want to happen next (a call, a signature, a decision either way): [YOUR GOAL]
Anything new I could share (a relevant example, a change in availability, a deadline that is real): [ANYTHING NEW TO SHARE]

Write a three-message sequence spaced over about two weeks:
1. Message one: short, references something specific from our last conversation, and offers one useful thing.
2. Message two: addresses the most likely reason they went quiet (price, timing, internal approval, a competitor) and makes it easy to say so.
3. Message three: a graceful close that asks for a yes or no and leaves the door open without guilt.

Rules: under 90 words each, one question per message, no fake urgency, no 'just checking in' or 'bumping this'. Add a suggested subject line for each and the day to send it.

Tip: The 'anything new to share' field is what separates a useful follow-up from a nag. If you have nothing, find something: a relevant customer story, a small example, or an honest note that your pricing holds until a date.

A customer asked what a clause means, why their bill changed, or why something broke, and the accurate answer is full of jargon. Use this to make it clear without making it wrong.

Act as a plain-language writer who explains complicated things to customers accurately, without talking down to them.

The source material (policy text, contract clause, or the technical explanation from our team): [PASTE THE SOURCE TEXT]
Who the customer is and what they already understand: [WHO THE CUSTOMER IS]
What they asked, in their words: [WHAT THEY ASKED]
Anything I must not say or commit to: [CONSTRAINTS]

Write a reply that:
1. Answers their actual question in the first sentence.
2. Explains the underlying idea in plain language, using one everyday comparison if it helps and dropping it if it does not.
3. Says what it means for them specifically: what changes, what they pay, what they need to do.
4. Points to where they can read the full text if they want it.

Rules: no jargon without a plain-language definition beside it, sentences under 20 words where possible, under 180 words total. Do not change the meaning of the source. After the reply, list any place where your simplification might differ from the source so I can double-check it against the original before sending.

Tip: Read the 'might differ from the source' list every time. Simplifying a policy is where AI quietly changes what it means, and a customer will hold you to the simple version.

A review is sitting on Google, Yelp, or an app store, and future customers will read your response more carefully than the review. Use this for both glowing and unfair ones.

Act as a reputation manager who writes review responses for future customers as much as for the reviewer.

The review: [PASTE THE REVIEW]
Star rating: [STAR RATING]
What actually happened, if I know (or 'unknown'): [WHAT ACTUALLY HAPPENED]
My business name and what we do: [BUSINESS NAME AND TYPE]
What I can offer to make it right, if anything: [WHAT YOU CAN OFFER]

Write a public response that:
- Thanks them specifically for something they mentioned, not generically.
- For a negative review: acknowledges the experience without arguing the facts in public, states one thing we are doing differently, and moves the conversation to a direct channel with a named person or role. No defensiveness, no 'that is not how we remember it', no revealing anything private about the customer or their transaction.
- For a positive review: mentions a detail from their visit or purchase, thanks the team member if named, and invites them back with a specific reason.
- Under 100 words. Sounds like a person, not a legal department.

Then give me a one-line internal note: what this review suggests we should fix or keep doing.

Tip: Never confirm in public that someone is a customer or share details of their order, even to defend yourself. Take the specifics offline; the public response is for the next hundred readers.

You have a draft that is accurate but too stiff, too long, or wrong for the channel (a formal email where a text is needed, or the reverse). Use this to fix tone without losing the facts.

Act as an editor who specializes in customer-facing messages and preserves every fact while fixing tone.

My draft: [PASTE YOUR DRAFT]
Channel it will go out on (email, live chat, SMS, phone script, social reply): [CHANNEL]
The customer's situation and mood: [CUSTOMER SITUATION]
The tone I want (for example warm and brief, formal and precise, upbeat but not salesy): [TONE YOU WANT]

Rewrite the draft so it:
- Fits the channel's norms for length and formality (SMS under 300 characters, chat in short lines, email with a clear subject and one ask).
- Leads with what the customer cares about, not what we want to say.
- Keeps every fact, date, number, and commitment exactly as written. Do not add promises.
- Removes filler, hedging, and stacked apologies.

Output:
1. The rewritten message.
2. A three-bullet 'what I changed and why' list.
3. Any fact from the original you were unsure about keeping, so I can confirm it made it through.

If the draft has a problem tone cannot fix (a missing answer, an unclear next step), tell me before rewriting.

Tip: Paste two or three past messages you were proud of and say 'match this voice'. The AI matches examples far better than adjectives.

A customer has gone quiet, a renewal is coming, or usage dropped, and you want to reach out with something better than 'how is everything going?'. Use this to write a message that earns a real answer.

Act as a customer success manager who reaches out to quiet accounts with messages that get honest replies.

Type of customer and what they bought: [CUSTOMER TYPE AND WHAT THEY BOUGHT]
When they started and what their goal was at the time: [START DATE AND ORIGINAL GOAL]
What I can see about their activity (logins, orders, support tickets, silence): [ACTIVITY SIGNALS]
Next milestone or renewal date: [RENEWAL OR MILESTONE DATE]
What I most want to learn from them: [WHAT YOU WANT TO LEARN]

Write a check-in message that:
- Opens with something specific about their account or goal, so it is obviously not a mass email.
- Names the change I noticed without sounding like surveillance.
- Offers one concrete, useful thing (a tip, a shortcut, a relevant new feature, a quick call with a stated purpose).
- Asks exactly one easy question they can answer in a sentence.
- Stays under 110 words, no 'just checking in', no 'circling back'.

Provide an email version and a shorter in-app or text version. Then suggest what to do if they do not reply within a week, and one sentence on what their silence most likely means given the signals.

Tip: The single question is the whole message. Make it one they can answer from their phone in ten seconds ('Is the reporting still the main thing you use it for?') and reply rates climb.

You keep hearing the same objection ('too expensive', 'we already have a vendor', 'not this quarter') and your answer is not landing. Use this to build responses that take the objection seriously.

Act as a sales trainer who teaches people to handle objections with curiosity instead of rebuttals.

My product or service: [YOUR PRODUCT OR SERVICE]
The objection, in the customer's exact words: [THE OBJECTION IN THE CUSTOMER'S WORDS]
Who the customer is and their situation: [WHO THE CUSTOMER IS]
What is genuinely true about the objection (if it is partly right, say so): [WHAT IS TRUE ABOUT THE OBJECTION]
Proof I can offer (results, references, guarantees, trials): [PROOF YOU CAN OFFER]

Give me:
1. What the objection most likely means underneath (list two or three possibilities), and one question to find out which.
2. Three ways to respond, each following acknowledge, clarify, then reframe, written as I would say them aloud in under 60 words. One should be for when the objection is fully valid and the honest answer is that we are not the right fit right now.
3. What not to say: the responses that sound defensive or dismissive.
4. A follow-up email of under 80 words to send after the conversation.

Do not invent statistics, customer names, or claims about competitors. Use only the proof I gave you.

Tip: Practice the responses out loud with the AI playing the customer: say 'now role-play the customer and push back on each one'. What reads well on screen often sounds canned when spoken.