Customer Service AI Prompt Templates

Reusable AI prompts for customer service teams: draft replies, de-escalate angry customers, summarize tickets, explain policies, and write help docs. Use the variants as-is, edit the placeholders, or download the editable Word doc.

Format
Editable Word .docx
Length
6 variants · copy-paste
Price
100% free
Setup
Copy or download

Get the editable Word doc in one click.

4.9·Free · No signup · Instant download
Connects to WebsiteWhatsAppTelegramInstagram
Support

Template preview

Draft a support reply

Prompt

You are a role for company, a product description. A customer wrote in about issue. Write a support reply to audience that answers the question, explains the fix in plain language, and reassures them. Use this context: context. Keep it under word limit words, in a tone tone, and end with a single clear next step.

How to adapt it

  • Replace context with the real ticket text, the account plan, and any error messages -- vague context produces a vague, generic reply.
  • Name the issue precisely so the AI answers the actual question instead of a nearby one.
  • Tighten word limit and tone until the reply sounds like your team, not a robot, and never promises a fix you cannot ship.

Why it works

It assigns a role, supplies the real ticket as context, names the deliverable, and constrains length and tone, which is what separates a usable support draft from filler an agent still has to rewrite from scratch.

Download free template

6 ready-to-use variants

1

Draft a support reply

When to use: Reach for it when an agent needs to answer quickly without sounding like a canned macro.

Prompt

You are a role for company, a product description. A customer wrote in about issue. Write a support reply to audience that answers the question, explains the fix in plain language, and reassures them. Use this context: context. Keep it under word limit words, in a tone tone, and end with a single clear next step.

How to adapt it

  • Replace context with the real ticket text, the account plan, and any error messages -- vague context produces a vague, generic reply.
  • Name the issue precisely so the AI answers the actual question instead of a nearby one.
  • Tighten word limit and tone until the reply sounds like your team, not a robot, and never promises a fix you cannot ship.

Why it works

It assigns a role, supplies the real ticket as context, names the deliverable, and constrains length and tone, which is what separates a usable support draft from filler an agent still has to rewrite from scratch.

2

De-escalate an angry customer

When to use: Use it the moment a message arrives heated, hostile, or threatening to churn.

Prompt

You are a role for company, a product description. A customer is angry about issue and their last message was heated. Write a reply to audience that opens with a sincere acknowledgement, takes ownership without excuses, states exactly what you will do next, and lowers the temperature. Use this context: context. Keep it under word limit words, in a tone tone, and end with a single clear next step.

How to adapt it

  • Replace context with the real angry message and the account history so the AI responds to what actually happened, not a generic complaint.
  • Match the tone to how upset they are -- a furious long-time customer needs more warmth than a mildly annoyed one.
  • Cut any line that sounds defensive or blames the customer, because a single excuse can reignite the whole thread.

Why it works

It leads with acknowledgement, assigns ownership, and names one concrete next step, which is what calms a heated customer far faster than a polished apology that promises nothing they can hold on to.

3

Summarize a long ticket thread

When to use: Use it before reassigning a ticket or escalating, so nothing gets lost between people.

Prompt

You are a role for company, a product description. Read the long ticket thread below and summarize it for audience. Capture what the customer wants, what has already been tried, where things stand now, and the single next action owed. Use this context: context. Present it as format, keep it under word limit words, in a tone tone, and end with a single clear next step.

How to adapt it

  • Replace context with the complete thread and any internal notes so nothing important is dropped between agents.
  • Set the format to match how your team reads handoffs, such as a one-line status followed by bullet points.
  • Tighten word limit and tone until the summary can be scanned in ten seconds without opening the original thread.

Why it works

It names exactly which four facts to extract and constrains the format, which is what turns a rambling thread into a handoff the next agent can act on without re-reading the entire conversation.

4

Explain a policy or refund decision

When to use: Use it when you have to say no, or explain a rule, and want the customer to still feel respected.

Prompt

You are a role for company, a product description. You need to explain decision to a customer who may not like it. Write a reply to audience that states the decision plainly, explains the reasoning in human terms, points to the relevant policy, and offers any alternative you genuinely can. Use this context: context. Keep it under word limit words, in a tone tone, and end with a single clear next step.

How to adapt it

  • Replace context with the exact policy wording and the account details so the explanation is accurate and defensible.
  • State the decision up front instead of burying it, because a customer trusts a straight answer more than a soft dodge.
  • Offer a real alternative where one exists, and never invent an exception your policy does not actually allow.

Why it works

It states the decision, gives a human reason, and cites the policy, which is what lets a customer accept a no without feeling dismissed, misled, or brushed off by a scripted non-answer.

5

Turn a resolved ticket into a help-doc

When to use: Do it right after you solve a question you can tell will be asked again and again.

Prompt

You are a role for company, a product description. Turn the resolved ticket below into a reusable help article for audience. Build it around the topic, with a one-line summary, numbered steps, and a short note on common mistakes. Use this context: context. Keep it under word limit words, in a tone tone, and end with a single clear next step.

How to adapt it

  • Replace context with the real ticket and the final working solution so the article documents what actually fixed the problem.
  • Title the article with the topic a customer would search for, not your internal feature name.
  • Tighten word limit and tone until the steps are skimmable and complete enough to deflect the next identical ticket.

Why it works

It reuses a solved problem, structures it around a real search phrase, and constrains length, which is what turns a one-time answer into a doc that quietly keeps the same question out of your queue.

6

Draft a proactive check-in

When to use: Use it when a real signal appears, such as low usage, a milestone, or an upcoming renewal.

Prompt

You are a role for company, a product description. Reach out proactively to a customer because of trigger. Write a short check-in to audience that references something specific about their account, offers one useful thing, and invites a reply without any pressure. Use this context: context. Keep it under word limit words, in a tone tone, and end with a single clear next step.

How to adapt it

  • Replace context with the real usage and support history so the message feels personal rather than mass-sent.
  • Name the trigger you actually saw, because a renewal nudge and a low-usage nudge need different offers.
  • Keep the ask light and the tone warm, since a proactive message should feel like help, not a sales push.

Why it works

It ties the outreach to a real signal, leads with something useful, and keeps the ask low-pressure, which is what makes a proactive check-in earn a reply instead of feeling like one more automated email.

Do it in sem.chat

Let your AI agent put this to work

Load this template into sem.chat and your agent uses it automatically, in your brand voice, around the clock.

  • Save as reusable replies, scripts, or rules
  • Keeps every message on-brand and consistent
  • Hands the hard cases to a human

How to use this template

  1. 1

    Pick the closest variant. Choose based on the situation, not only the channel.

  2. 2

    Replace every placeholder. If you cannot fill a field, ask one clarifying question first.

  3. 3

    Save the final version into sem.chat, your CRM, or your help desk so the team stays consistent.

  4. 4

    Review results weekly. Drop variants that create confusion and improve the ones that work.

Frequently asked questions

Can I use these templates commercially?
Yes. Copy, edit, and use them in your business, client work, CRM, help desk, or sem.chat workspace.
Why are there six variants?
One generic template rarely fits every situation. Six variants give your team practical choices without a messy library.
Should I paste these into sem.chat?
Yes. Save the best variants as canned replies, knowledge base entries, routing rules, or CRM notes so your AI agent and team stay consistent.
How do I stop the AI from sounding generic?
Give it real context every time -- the actual ticket, the account plan, the policy wording. Every prompt leaves a context slot precisely because that is where quality comes from. A role and a word limit shape the output, but real data is what makes the reply specific to your product and your customer.
Can I reuse these prompts across my whole team?
Yes, that is the point of a template. Set the role, product description, and word limit once for your team, then let each agent drop in the specific ticket or decision. Consistent structure means consistent quality no matter who runs the prompt.
Should I edit the AI reply before sending it?
Always read it before it goes out. These prompts get you to a strong draft fast, but a human should confirm the facts, the tone, and any promise about timing, fixes, or refunds. Treat the AI as a fast first writer, not the final approver.
What tone should I use for an upset customer?
Calm, human, and free of excuses. Acknowledge the frustration first, take ownership, then state one concrete next step. A defensive or over-formal tone reads as a brush-off and usually makes an angry customer angrier.

Put this template to work in sem.chat

Use this in sem.chat and let your agent handle it, in your voice, around the clock.