The 25 Best AI Prompts for Customer Support Replies

Good customer support replies are rare. Most responses either come across as canned ("Your satisfaction is our top priority") or they solve the literal question while missing what the customer was actually upset about. AI is useful when the agent has a clear understanding of the customer and needs help with the phrasing. It is harmful when the agent uses it to skip the understanding part. These prompts are written for the first scenario. You read the ticket carefully. Then you use the prompt to help you write something that sounds like a human who cared.

Below are 25 prompts I use when I am writing or reviewing support replies. Tickets, chat logs, angry emails, draft responses, and policy docs all go into {{clipboard}}. Pick the ones that fit the kind of tickets you handle and keep them a keystroke away so you are not rewriting prompts under the pressure of a piling queue.

---

Download Free for macOS

Understanding the customer's issue

1. Extract the real issue from a rambling ticket

I have a customer ticket that is long, unclear, or emotional. I need to understand what they are actually asking for before I write a reply.

Here is the ticket:

{{clipboard}}

Produce:

1. A one sentence statement of what the customer is actually asking for or experiencing.
2. A list of any secondary issues they raised along the way.
3. A separation of facts (what they say happened) from interpretations (what they are assuming).
4. Their emotional state: frustrated, confused, anxious, neutral, or angry.
5. The one thing they probably want more than the literal fix (respect, speed, acknowledgment, or compensation).
6. The information I still need from them before I can solve the issue.
7. A flag for any part of the ticket that sounds like it contradicts itself or needs clarification.

Do not write a reply yet. I want to understand the ticket first.

2. Identify the underlying problem behind a symptom

A customer is reporting a symptom but the real problem is probably something else. Help me figure out what is really going on.

Here is the ticket and any system context:

{{clipboard}}

Walk me through:

1. The literal symptom they are describing.
2. Three possible root causes, ranked by likelihood.
3. For each cause, a diagnostic question I could ask the customer to confirm or rule it out.
4. The single best first question to ask them.
5. A guess at whether this is a user error, a product bug, or a known issue (and why).
6. A recommendation on whether to ask the customer more questions or escalate to engineering based on the pattern.

Do not assume user error. Do not assume product bug. Reason from the evidence.

3. Summarize a long ticket thread for a colleague taking over

I am handing off a ticket to a colleague and I need a short briefing that catches them up without them reading the whole thread.

Here is the thread:

{{clipboard}}

Produce:

1. Who the customer is and a one line description of their setup.
2. The original issue in one sentence.
3. What has been tried so far and what the result of each attempt was.
4. Where the customer is currently emotionally: patient, tense, frustrated, ready to churn.
5. The current state: waiting on us, waiting on them, escalated, resolved.
6. What the next step should be.
7. One piece of context about the customer that my colleague should know before replying.

Under 200 words. Facts and state, no editorial.

First response drafts

4. Draft a first response that acknowledges and investigates

I have a ticket and I want to write a first response that acknowledges the issue, gathers the information I need, and sets expectations.

Here is the ticket:

{{clipboard}}

Write a response with:

1. A warm opener that names the customer and the specific thing they reported.
2. A brief acknowledgment of the impact without overdoing it.
3. A short statement of what I am going to do next.
4. The specific questions I need answered to investigate, phrased so the customer can reply in a single message.
5. A rough expectation of timing.
6. A close that is human, not a corporate signoff.

Under 150 words. No "I apologize for the inconvenience" as an opener. No "please rest assured." No "We value your business."

5. Draft a response that provides a fix in the first reply

I already know the fix for this issue and I want to write a response that delivers it cleanly, without the usual support theater.

Here is the ticket and the fix:

{{clipboard}}

Write a response that:

1. Opens by confirming the issue they described.
2. Gives the fix in clear numbered steps if it is a multi step fix, or a single paragraph if it is one action.
3. Explains briefly why this fixes the issue (the customer will often want to understand, not just comply).
4. Offers help if the steps do not work.
5. Ends with a small warm close.

Under 200 words. Avoid "please follow these steps" language. Just give the steps. If the fix is reversible, say so.

6. Draft a response when I need to say "we are looking into it"

I cannot solve the issue yet. I need a response that acknowledges the problem and sets a real expectation without sounding like a stalling tactic.

Here is the ticket:

{{clipboard}}

Write a response that:

1. Confirms I have read and understood the specific issue.
2. Admits honestly that I do not have an answer yet.
3. States what I am doing about it: who is looking, what they are looking at, and when I will know more.
4. Gives a specific next check in time, not "as soon as possible."
5. Invites the customer to share anything new they observe in the meantime.
6. Closes in a way that respects their frustration without being syrupy.

Under 120 words. No "We are working hard to resolve this." Be specific or be quiet.

Handling frustrated customers

7. Respond to an angry customer without matching the tone

A customer is angry and their message is intense. I need to reply in a way that de escalates without being dismissive of their anger.

Here is the message:

{{clipboard}}

Write a response that:

1. Acknowledges their frustration directly, in their own words where possible.
2. Does not use the phrase "I understand how you feel" (it almost always reads as fake).
3. Addresses the specific thing they are most upset about, not just the technical issue.
4. Takes ownership where ownership is warranted.
5. Offers a concrete next step, not a vague reassurance.
6. Stays warm without being groveling.

Under 150 words. Do not apologize for feelings that are legitimate. Apologize for the thing that caused them.

8. Reply to a customer who is threatening to leave

A customer is threatening to cancel, churn, or move to a competitor. I need to reply in a way that takes the threat seriously without panicking.

Here is the message:

{{clipboard}}

Write a response that:

1. Acknowledges the threat directly, without dismissing it or pretending it was not made.
2. Asks a question that helps me understand what would actually keep them.
3. Offers a specific thing I can do now, not "let's schedule a call."
4. Is honest about what I cannot do, if applicable.
5. Respects their choice if they still want to leave.
6. Does not beg or overpromise.

Under 150 words. Do not use the phrase "we would hate to lose you." Mean it or do not say it.

9. Respond to a personal attack without being defensive

A customer made a personal attack, accusation, or hostile comment. I need to respond without being defensive, without escalating, and without letting it slide.

Here is the message:

{{clipboard}}

Write a response that:

1. Stays calm and does not react to the tone.
2. Addresses the substance of their complaint separately from the tone.
3. Declines to engage with the personal content, firmly but politely.
4. Focuses on the actionable issue, if there is one.
5. Sets a boundary if needed, without threatening or moralizing.
6. Ends professionally, not coldly.

Under 120 words. If the customer should be escalated or banned rather than replied to, say so.

Apologies that work

10. Write an apology that is specific and not performative

I need to apologize for a specific mistake my company made. I want the apology to be real, specific, and not sound like it came from a legal department.

Here is the situation:

{{clipboard}}

Write an apology that:

1. Names the specific thing we did wrong.
2. Acknowledges the specific impact on the customer.
3. Does not use "I am sorry you feel that way" or any other fake apology pattern.
4. Takes responsibility without excessive self flagellation.
5. States what we are doing to fix it.
6. States what we are doing to prevent it.
7. Ends warmly without asking for forgiveness.

Under 150 words. Write like a real person apologizing, not like a corporation.

11. Apologize for something that was not technically our fault

A customer is upset about something that is not technically our fault, but they had a bad experience and I want to acknowledge that honestly.

Here is the situation:

{{clipboard}}

Write a response that:

1. Acknowledges the bad experience without claiming responsibility for the root cause.
2. Avoids "unfortunately" (it sounds cold).
3. Takes ownership of the parts we are responsible for, even if small.
4. Explains the facts clearly, without sounding like I am making excuses.
5. Offers something helpful, even if it is not a refund or a fix.
6. Does not gaslight the customer about whose fault it is.

Under 150 words. Sincere and factual, not defensive.

12. Apologize for a repeat issue

This is the second or third time something has gone wrong for the same customer. An apology has to do more than the previous ones did.

Here is the history and the current issue:

{{clipboard}}

Write a response that:

1. Acknowledges the pattern explicitly, not just the current issue.
2. Does not lean on "this is not typical" because at this point it is typical for them.
3. Offers something tangible: a credit, a discount, a dedicated contact, a call with a senior person.
4. Gives a specific commitment about what will change.
5. Does not promise "this will not happen again" unless I can actually guarantee it.
6. Ends with warmth that does not feel scripted.

Under 180 words. The stakes are higher than a first time apology. The response should reflect that.

Follow ups and resolution

13. Write a follow up when the customer has not replied

I sent a response to a ticket and the customer has not replied. I want to follow up in a way that is helpful, not pushy.

Here is the previous exchange:

{{clipboard}}

Write a follow up that:

1. Does not say "just checking in."
2. Restates the specific thing I am waiting on, briefly.
3. Offers a way to make the reply easier: a one word answer, a yes or no, or a timeframe.
4. Gives them permission to close the ticket if the issue is no longer an issue.
5. Is warm and low pressure.

Under 80 words. Subject line that signals the thread without annoying them.

14. Confirm a fix worked and close the ticket warmly

The customer confirmed the fix worked. I want to close the ticket in a way that leaves a good impression.

Here is the exchange:

{{clipboard}}

Write a closing message that:

1. Acknowledges that the fix worked, specifically.
2. Offers one small piece of help: a tip, a link to related docs, a heads up about something related.
3. Invites them to reach out again if anything comes up.
4. Does not ask for a review, a rating, or social proof in the same message.
5. Ends warmly, not formally.

Under 80 words. A short, human close beats a long, scripted one.

15. Follow up proactively on a known issue that will affect this customer

We have a known issue that will affect a specific customer and I want to reach out proactively before they notice.

Here is the issue and the customer:

{{clipboard}}

Write a message that:

1. Opens by naming the specific issue and how I know it affects them.
2. Explains the impact plainly.
3. States what we are doing and when it will be resolved.
4. Offers a workaround if one exists.
5. Acknowledges the inconvenience without overdoing it.
6. Invites them to reply with questions but does not require it.

Under 150 words. Proactive transparency builds more trust than silent fixes.

Saying no without losing the customer

16. Decline a feature request

A customer is asking for a feature we are not going to build. I need to say no in a way that respects their request and preserves the relationship.

Here is the request:

{{clipboard}}

Write a response that:

1. Acknowledges the request specifically, not just "thanks for the feedback."
2. Explains why we are not building it, honestly but briefly.
3. Asks a question that helps me understand what they are really trying to do, in case there is a different solution.
4. Offers a workaround or alternative if one exists.
5. Does not promise "we will consider it for the roadmap" if we will not.
6. Ends warmly, without pretending the answer is yes.

Under 150 words. Respect the customer enough to tell them the truth.

17. Decline a refund or compensation request

A customer is asking for a refund or compensation that I cannot or should not grant. I need to say no without escalating their frustration.

Here is the request and the context:

{{clipboard}}

Write a response that:

1. Acknowledges the specific request.
2. Explains why the answer is no, briefly and honestly, without hiding behind policy.
3. Offers the thing I CAN do, even if it is smaller.
4. Does not use the phrase "I am unable to" (it sounds passive and evasive).
5. Stays respectful without being syrupy.
6. Leaves the door open for escalation if the customer wants it.

Under 150 words. Be firm and warm, not firm and cold.

Escalation and complex issues

18. Write an escalation summary for engineering or product

I have a customer issue that needs to be escalated to engineering or product. I need a summary that gives them everything they need without making them read the ticket.

Here is the ticket and what I have diagnosed so far:

{{clipboard}}

Produce:

1. A one line headline of the issue.
2. The customer impact: how many users, how often, how severe.
3. Steps to reproduce.
4. What I have already tried and what I learned.
5. Any environment details (browser, OS, account type, plan).
6. A link or screenshot reference placeholder.
7. A clear ask: diagnose, fix, confirm, advise.

Under 250 words. Engineering should be able to act on this without reading the thread.

19. Translate an engineering update back to the customer

Engineering sent me an update about a customer's issue and I need to translate it into something the customer will actually understand.

Here is the engineering update and the customer context:

{{clipboard}}

Write a customer facing version that:

1. Removes engineering jargon.
2. Preserves the specific facts about the issue and the fix.
3. Translates the timeline into terms the customer cares about (when they can use the product again, what changes).
4. Acknowledges the impact without overselling the fix.
5. Gives them an actionable next step.
6. Uses "we" for the company and "you" for the customer.

Under 150 words. Clarity over cleverness.

Self service and FAQ writing

20. Write an FAQ entry from a common support ticket

I keep getting the same question in tickets and I want to turn it into a clean FAQ entry.

Here is the question and the typical answer:

{{clipboard}}

Write an FAQ entry that:

1. Has a question title that matches the phrasing customers use (not internal jargon).
2. Opens the answer with the direct answer in one or two sentences.
3. Provides the specific steps or details a customer would need to self serve.
4. Includes one common edge case or follow up.
5. Links to related articles if relevant.
6. Ends with a clear way to get more help.

Under 250 words. No marketing copy. No "we hope this helps."

21. Rewrite a help article to be actually helpful

I have a help article that is technically correct but customers still open tickets about the topic. Rewrite it to be more useful.

Here is the article:

{{clipboard}}

Produce:

1. A diagnosis of why the current article is not working: too long, wrong order, missing context, jargon, buried instructions, unclear outcome.
2. A rewrite that fixes the issues.
3. A clearer title that matches what customers search for.
4. A summary paragraph at the top for scanners.
5. Step by step instructions if the topic needs them, with screenshots referenced as placeholders.
6. A troubleshooting section for the common failure modes.
7. A link section at the bottom for related topics.

22. Create a decision tree for a common support flow

I have a common support flow where the right answer depends on the customer's situation. I want a decision tree that agents can follow.

Here is the flow:

{{clipboard}}

Produce:

1. A decision tree as nested bullets or a numbered branching structure.
2. Clear yes or no questions at each branch.
3. Concrete next actions at each leaf.
4. A flag for any branch that should escalate rather than self resolve.
5. A note on the common mistake agents make in this flow.
6. A short version for quick reference and a longer version with context.

Macros and canned responses

23. Write a macro that does not sound like a macro

I need a canned response for a common scenario. It will be sent to many customers, but I do not want it to sound generic.

Here is the scenario:

{{clipboard}}

Write a macro that:

1. Uses warm, specific language that could pass as a personal reply.
2. Has clear placeholders for the name and any specific detail the agent should personalize.
3. Does not start with "Thank you for contacting us."
4. Does not end with "Please let us know if you have any further questions."
5. Is under 150 words.
6. Has a version for a happy path and a version for when the customer is already upset.

The goal is a macro that an agent can send verbatim when needed, but that is easy to personalize when it is worth it.

24. Audit an existing macro library for dated language

I have a library of support macros and I want to find the ones that sound robotic, dated, or would feel worse than no response.

Here are the macros:

{{clipboard}}

For each macro, flag:

1. Corporate clichés ("we value your business," "your satisfaction is our priority").
2. Passive aggressive phrases ("as previously stated," "for your convenience").
3. Empty reassurances ("rest assured," "please be patient").
4. Outdated references (to old product names, old pricing, old policies).
5. Missing warmth or specificity.
6. A proposed rewrite for the three worst offenders.

Rank the macros from worst to best. Tell me which ones to retire entirely.

25. Personalize a macro for a specific customer

I have a macro and a specific customer situation. Help me personalize the macro so it feels like a real reply, not a template.

Here is the macro and the customer's context:

{{clipboard}}

Produce:

1. A personalized version of the macro with the customer's specific details woven in.
2. A flag for any part of the macro that does not fit this customer and should be cut.
3. A sentence added that acknowledges something specific about the customer's situation.
4. A note on whether the macro is even the right response, or whether this situation deserves a fully custom reply.
5. A shorter version if the full macro is too long for the customer's original message.

Do not blindly apply the macro. Use judgment.