1. Plain-English reply draft
Prompt: Act as a customer service writer for [BUSINESS]. Draft a clear, helpful reply to the customer message below. Use only the facts in the context. If a fact is missing, put it under “Needs confirmation.” Keep the tone calm and human. Customer message: [PASTE]. Approved context: [PASTE].
Review: Confirm price, date, service scope, warranty, and any promise before sending.
2. Angry customer de-escalation
Prompt: Draft a short response to an upset customer. Acknowledge the concern, avoid blame, do not admit fault, do not promise a refund, and invite one clear next step with a real person. Customer note: [PASTE]. Safe facts: [PASTE].
Review: Owner or manager approves every dispute reply.
3. Review response
Prompt: Draft a public review response. Thank the reviewer, stay professional, avoid private details, and keep it under 90 words. If the review is negative, move the discussion to a private channel without arguing. Review: [PASTE]. Safe context: [PASTE].
Review: Remove private facts, medical/legal claims, refunds, or blame.
4. FAQ answer from policy notes
Prompt: Turn this repeated customer question into a website FAQ answer using only the policy notes below. Use plain language, no hype, and list anything that needs owner confirmation. Question: [PASTE]. Policy notes: [PASTE].
Review: Check pricing, service area, guarantees, licensing, and exclusions.
5. Support macro builder
Prompt: Create a reusable support macro for [COMMON ISSUE]. Include empathy, the likely reason, what the customer should do next, what the team should check internally, and when to escalate. Keep it short enough for email or chat.
Review: Test against three recent real tickets before saving.
6. Call-note summary
Prompt: Summarize these call notes into: customer goal, key facts, commitments made, open questions, follow-up owner, follow-up deadline, and risks to confirm. Do not add facts. Notes: [PASTE].
Review: Confirm every commitment before sending a recap.
7. Tone check before sending
Prompt: Review this draft for tone problems, unclear next steps, risky promises, missing empathy, and confusing wording. Suggest edits but do not change the facts. Draft: [PASTE].
Review: The sender chooses the final wording.
8. Weekly customer insight summary
Prompt: Summarize these anonymized customer messages into recurring questions, objections, complaints, praise, and improvement ideas. Separate repeated patterns from one-off comments. Messages: [PASTE].
Review: Do not change policies based on one anecdote.