Business WritingClaudeWritingSalesOperations

Customer Support Macro Library

Build warm and controlled support reply macros.

Prompt

# Role
You are a customer experience lead balancing efficiency, compliance, and user sentiment.

# Task
Using product notes, support policy, and common issues, generate a customer support macro library.

# Inputs
Ask me to provide or paste: product/project background, target audience, use case, constraints, existing assets, desired language, and channel. If data, screenshot descriptions, competitors, or past examples are included, prioritize those facts and do not invent missing details.

# Output Format
1. Issue categories and priority
2. Three macros per category
3. Escalation, compensation, and refusal scripts
4. Risk notes for sensitive scenarios
5. QA scoring criteria

# Quality Bar
1. Sound sincere, not robotic
2. Do not promise beyond policy
3. Keep variable placeholders in each macro

# Avoid
Do not provide generic advice. Do not use unverifiable hype. Do not pad the answer with irrelevant completeness. If business, medical, financial, legal, or security risks are involved, clearly state assumptions and boundaries.

# Process
First decide whether the information is sufficient. If key information is missing, ask up to five clarifying questions. If enough information is available, produce the actionable version directly. Then provide three optional improvement directions for iteration.

# Final Deliverable
End with a concise copy-ready version that preserves the key constraints, output structure, and quality bar.

Curated by the editorial team · Updated 06/28/2026 · Model: Claude

Usage guide

How to use this prompt

This template is designed for business writing tasks. Replace the sample details with real constraints before running it in Claude.

Step 1
Add the task context, reader, and desired business outcome.
Step 2
Provide verifiable facts, examples, and constraints before generating.
Step 3
Check facts, tone, and action items before using the result externally.

Details to replace or add

Specific inputs produce more useful results. Do not submit passwords, private information, or confidential business data.

Business context and goal
Target reader
Facts, data, and source material
Tone and length
Output format and deadline

Output checklist

Facts and numbers are supported
The conclusion answers the original task
Tone fits the reader
Structure is easy to scan
Owners and next actions are explicit

Common adjustments

Add real data, named audiences, and decision criteria when the draft is generic.

Provide a reference paragraph and name the traits to preserve when tone misses.

Request a table, checklist, or owner-based action plan when the result is hard to execute.

This prompt separates Business Writing, Writing, Sales, Operations requirements into context, constraints, and output format. Keep the objective fixed and revise only the conditions that failed before rewriting the whole template.