10 Prompts to Get the Most Out of Generative AI for Your Customer Communications
Stop getting generic results. The reason most teams are disappointed with AI-generated communications is simple: they aren't giving the AI enough context. These ten copy-and-paste templates fix that.
You have access to the most powerful writing assistant in history. But like any powerful tool, its output is only as good as your input. Many business teams experimenting with tools like ChatGPT are getting generic, unusable results — not because the AI is bad, but because vague prompts produce vague output. "Write a sorry email" is a bad prompt. It leads to a bad result.
This guide provides ten practical, copy-and-paste prompt templates designed specifically for B2B customer communications. Use these to save time, improve quality, and ensure your AI assistant sounds like a helpful expert, not a generic robot.
The Golden Rule of Prompting: Context is King
Before diving in, remember this one rule: the more context you provide, the better the output. A great prompt always tells the AI five things:
- Role — Who should it act as? (e.g., "Act as a senior customer support manager...")
- Task — What is the specific thing you want it to do?
- Context — What information does it need to complete the task?
- Constraints — What are the rules of the game? (e.g., "Do not make promises we can't keep")
- Tone — How should it sound? (e.g., "Apologetic and competent")
1. The Empathetic "Sorry" Email
Use case: Responding to a customer complaint about a service failure.
Act as a senior customer support manager. Your task is to draft an empathetic and professional email responding to the following complaint. Acknowledge the customer's frustration, take ownership of the problem without blaming other teams, explain the immediate next step we are taking, and provide a direct contact for follow-up. Do not make promises we can't keep. The tone should be apologetic, reassuring, and competent.
Here is the customer's complaint: "[Paste customer's email here]"
2. The "Just Checking In" Proactive Email
Use case: Following up with a high-value client who has gone quiet after you sent a proposal. This is a core tactic in a proactive CX approach.
Act as a B2B account manager. Draft a short, friendly, and low-pressure "checking in" email to a client whose project has been stalled for 3 weeks. The goal is to restart the conversation and offer help, not to sound like we are chasing them for a decision. Mention the project by name and offer a specific, helpful next step. The tone should be helpful and supportive.
Client Name: [Client Name] / Project Name: [Project Name]
3. Summarising a Complex Support Ticket
Use case: Creating a concise summary for an internal escalation to your engineering team.
Act as a technical support analyst. Read the following email thread and summarise it into a 3-bullet point summary for an internal escalation. The summary must include: (1) the core problem the customer is facing, (2) the troubleshooting steps already tried, and (3) the specific question we need the engineering team to answer.
Here is the thread: "[Paste email thread here]"
4. Turning Jargon into a Simple Explanation
Use case: Explaining a complex technical issue to a non-technical client — especially useful when augmented agents need to bridge the gap between technical teams and customers.
Act as a communications expert who specialises in simplifying complex topics. Take the following technical explanation and rewrite it for a non-technical audience. Use a simple analogy to explain the core concept. Avoid all industry jargon. The tone should be clear, simple, and confident.
Here is the technical explanation: "[Paste technical text here]"
5. The "New Feature" Announcement
Use case: Announcing a new product feature that solves a specific customer problem.
Act as a product marketer. Write a concise and exciting announcement email for our new feature called "[Feature Name]". Start by stating the customer problem it solves in one sentence. Then, explain how the feature works in 2–3 simple steps. End with a clear call to action. The tone should be benefit-oriented and energetic.
The problem this feature solves is: "[Describe the customer problem]"
6. Rewriting for a Different Tone
Use case: You have written a functional draft, but it does not sound right.
Take the following email draft and rewrite it to be more [formal / friendly / concise / empathetic / confident]. Make sure to retain all the key information.
Here is the draft: "[Paste your draft here]"
7. Brainstorming Follow-Up Questions
Use case: A customer sends a vague request and you need to understand it better before you can help.
Act as an experienced customer support agent. A customer has sent the following vague request: "[The customer's vague request]". What are the 3–5 most important clarifying questions I should ask them to fully understand their issue and be able to help effectively?
8. Creating a Knowledge Base Article from a Ticket
Use case: Turning a solved problem into a permanent, reusable asset — a key step in the Human-in-the-Loop virtuous learning cycle.
Act as a technical writer. Based on the following resolved support ticket, write a clear, step-by-step knowledge base article. The article should have a clear title (phrased as a question), a brief description of the problem, and a numbered list of steps for the solution.
Here is the ticket: "[Paste key details of the resolved ticket]"
9. The "Price Increase" Notification
Use case: Communicating a sensitive but necessary price increase to long-term customers.
Act as the Head of Customer Success. Draft a clear, honest, and respectful email announcing a price increase of [X%] effective from [Date]. Start by thanking the customer for their loyalty. Briefly and transparently explain the reason for the increase. Clearly state the new price and provide a link to an FAQ page for more details. The tone should be appreciative and direct, not defensive.
10. The "Onboarding Welcome" Email
Use case: Welcoming a new B2B client and setting them up for immediate success.
Act as an onboarding specialist. Write a warm and welcoming email to a new client who has just signed up. The email must: (1) congratulate them and express excitement for the partnership, (2) clearly state the single most important first step, (3) introduce their dedicated account manager by name, and (4) provide a single, clear link to the main support/help centre. The tone should be exciting, helpful, and exceptionally clear.
Client Company: [Company Name] / First Step: [Describe first action] / Account Manager: [Manager's Name]
A Final Reminder: AI is a Draft, You are the Editor
Never copy and paste without reading. Generative AI is an incredibly powerful starting point, but it is not infallible and it is not you. Always review and edit the output to add your personal touch, check for accuracy, and ensure it reflects your brand's voice. Think of the AI as a brilliant junior writer — it produces the first draft, but you, the expert, provide the final polish.
Want to go further? Our AI in CX Training programme helps your team build a systematic, scalable approach to using AI across every customer touchpoint. Or get in touch to explore how Kairos can help you design an Adaptive CX system around these capabilities.