Useful prompts for work that needs doing.

Draft a concise, honest customer failure notification using only the facts provided. Do not invent details, blame the customer, use jargon, add hype, or include a greeting, sign-off, or politeness padding. Acknowledge the impact directly without excessive apology or defensiveness. State the root cause in plain language, describe the current resolution status and timeline exactly as provided, and include the specific goodwill offer. Return only this fixed structure:

Subject: Automation failure update for {{customer_name_or_id}}
What happened: The {{failed_process_name}} failed because {{root_cause_summary}}.
Current status: {{resolution_status_and_steps}}
Goodwill: {{goodwill_offer_details}}

Keep the notification concise and suitable for sending after one light edit. If the information does not confirm a fix or timeline, state that clearly rather than implying one.

Draft one ready-to-send verification message using only the information provided. Recipient: {{recipient_name_role}}. Confirm this specific detail: {{detail_to_confirm}}. Reference this context: {{context_reference}}. Use the {{contact_method}} format. Urgency: {{urgency_level}}. Requested next step: {{expected_next_step}}. Do not invent details or add unnecessary politeness. Keep it clear, concise, professional, and under 100 words. If the method is email, include a concise subject line; otherwise, start with the message. Return only the message.

Draft a concise cancellation-prevention message from a Customer Success Manager to {{customer_name}}.

Customer context:
- Cancellation reason: {{cancellation_reason}}
- Current plan tier: {{plan_tier}}
- Recent usage activity: {{recent_usage_activity}}

Acknowledge the customer's frustration without defensiveness. Ask exactly one clarifying question about the underlying cause. Suggest one specific alternative solution that fits the context, such as a configuration change, onboarding support, training, temporary plan adjustment, or workflow recommendation. End with a low-pressure invitation to stay. Do not invent facts, use hype, include fabricated proof, or ask the sender for more information.

Return only the finished message, ready to send after one light edit. Include a subject line followed by the message body.

Compose one calm, transparent crisis email for leadership communication using only the information provided below. Do not invent facts, causes, impacts, commitments, contact details, or recovery milestones. Avoid defensive language, blame, hype, and unnecessary jargon. Take clear ownership without assigning blame.

Use this exact plain-text structure:
Subject: [concise subject line]

Hello [appropriate audience],

Situation and impact:
[Direct explanation of what happened and who is affected.]

Our response:
[State ownership and summarize the proposed solution.]

Next steps and recovery timeline:
[List the immediate actions and the expected recovery timeline.]

Contact:
[Name and contact details of the primary contact person.]

Regards,
[Leadership team or organization]

Inputs:
Situation description: {{situation_description}}
Affected stakeholders: {{affected_stakeholders}}
Proposed solution: {{proposed_solution}}
Recovery timeline: {{recovery_timeline}}
Primary contact person: {{primary_contact_person}}

Return only the completed email, with no analysis, notes, placeholders, or markdown formatting.

Draft one win-back message for {{customer_name}} using the information below. Adapt the length and format to {{communication_channel}}.

Past usage or signup context: {{past_context}}
New feature or improvement: {{new_improvement}}
Returning incentive: {{returning_incentive}}
Re-engagement step: {{cta_method}}

Use only the supplied facts. Explain why the recipient may find returning valuable, briefly reference their past connection, highlight the improvement, state the incentive accurately, and end with one clear, low-friction next step. Personalize the opening with the recipient's name. Do not invent results, testimonials, deadlines, scarcity, or other claims. Avoid hype, excessive politeness, and generic filler.

Return exactly:
Subject: [include only when appropriate for the channel]
Message: [the ready-to-send message]

Write one concise complaint de-escalation response script for a customer whose product or service failed. Use only the provided facts; do not invent policies, timelines, refunds, or outcomes. Explicitly validate the customer's frustration, take ownership without deflection, propose the most specific feasible solution from the available options, and state a clear next step. Follow the brand tone guidance without using vague corporate language.

Customer complaint: {{customer_complaint}}
Product or service: {{product_or_service}}
Order or ticket reference: {{reference_number}}
Preferred contact method: {{contact_method}}
Available resolution options: {{resolution_options}}
Brand tone guidelines: {{brand_tone}}

Return exactly this format and nothing else:
Acknowledgement: [one sentence validating the customer's experience]
Ownership: [one sentence taking responsibility]
Resolution: [one or two sentences proposing a concrete available solution]
Next step: [one sentence stating what will happen next and using the reference number or preferred contact method where relevant]

Draft one sincere apology email using the information below. Take clear responsibility without excuses, blame, defensiveness, hype, or excessive politeness. Briefly explain the impact on the recipient, offer the stated solution or next step, and close in a way that supports rebuilding trust. Do not invent facts or request clarification; make reasonable neutral wording choices when details are limited. Match the selected tone and relationship.

Situation details: {{situation_details}}
Recipient relationship: {{recipient_relationship}}
Desired solution or next step: {{desired_solution}}
Tone: {{tone}}
Constraints or required points: {{constraints}}
Brief background: {{brief_background}}

Return only this fixed format, with no commentary:
Subject: [clear apology subject line]

[complete email draft]

Draft a concise meeting-decline message based on the details below. Output only the message body, with no subject line, labels, commentary, quotation marks, or follow-up questions.

Meeting topic: {{meeting_topic}}
Their intended outcome: {{meeting_outcome}}
Reason for declining: {{decline_reason}}
Specific async alternative: {{async_alternative}}
Requested response time or deadline: {{response_deadline}}

Acknowledge their intended outcome in the opening sentence. State the decline plainly without over-explaining or over-apologizing. Propose the specific async alternative exactly and include the response time or deadline when relevant. Close with one clear next step. Do not invent details, testimonials, social proof, or a future meeting invitation.

Convert the provided customer feedback and context into one neutral, factual engineering issue report. Remove emotional, accusatory, and speculative language. Preserve concrete actions, exact error text, timestamps, environment details, identifiers, and reproduction information. Do not invent, infer, or normalize missing facts. If information is absent, write "Not provided" or list it under Unknowns. Return only this format:

Title: [Feature/Module] - [Brief Issue Summary]

Summary: [One concise factual description]

Steps to Reproduce:
1. [Factual step]
2. [Factual step]

Expected Behavior: [What should have happened]

Actual Behavior: [What happened, including exact errors or observable effects]

Environment: [OS, browser, device, product version, deployment environment, or Not provided]

References: [Relevant account/order ID, incident timestamp, logs, screenshots, or Not provided]

Unknowns:
- [Missing debugging information]

Customer message:
{{customer_message}}

Attached evidence or error details:
{{diagnostic_evidence}}

Account or order context:
{{account_context}}

Incident timing and environment:
{{incident_details}}

Reproduction steps described by the customer:
{{reproduction_steps}}

Rewrite the message below so it professionally pushes back on the request, deadline, or decision while remaining constructive.

Original message or request:
{{original_message}}

Specific constraint or limitation:
{{constraint}}

Proposed alternative or compromise:
{{alternative}}

Recipient relationship:
{{recipient_context}}

Write only the revised message. Clearly state the constraint, briefly explain its impact, and offer the proposed alternative. Preserve the facts provided and do not invent details, statistics, commitments, or excuses. Use a direct, professional, non-aggressive tone; avoid excessive apologizing, blame, hype, and filler. Keep it concise and ready to send after one light edit. Format it as one to three short paragraphs with no heading, commentary, or bullet points.

Draft a ready-to-send client message about the issue below. Return exactly two parts: a concise subject line or opening, followed by the message body.

Client: {{client_name_or_title}}
What went wrong: {{mistake_description}}
Impact on the client: {{client_impact}}
Immediate fix: {{immediate_fix}}
Next step or timeline: {{next_step_or_timeline}}

Acknowledge the mistake directly without excuses, external blame, or defensiveness. Explain the impact from the client's perspective, state the concrete corrective action, and make the next step or timeline unmistakable. Keep the language professional, direct, calm, and accountable. Avoid hype, excessive apology, vague assurances, and invented details. Write for one light edit and do not ask follow-up questions.

You are an expert customer support coach. Generate exactly 3 distinct, context-appropriate next responses for a support agent based on the provided conversation transcript, agent history, and ticket context.

Ticket Context:
{{ticket_details}}

Agent History / Previous Messages:
{{agent_history}}

Customer Message Transcript:
{{customer_transcript}}

Desired Tone:
{{tone_setting}}

Provide your output in this exact format:
Response 1: Empathetic and clarifying (asks for more information)
Response 2: Direct and solution-oriented (provides immediate troubleshooting)
Response 3: Escalation or process-focused (sets expectations for next steps)

Analyze the following customer support interaction to uncover the true root, underlying problem driving the interaction, distinguishing it from the surface-level complaint.

Initial Stated Complaint: {{stated_complaint}}

Conversation Transcript:
{{conversation_transcript}}

Context/Environment: {{context_environment}}

Provide your analysis using the following strict structure:

1. STATED COMPLAINT VS. UNDERLYING PROBLEM
- Stated Complaint: Summarize the surface-level issue presented by the customer.
- Underlying Problem: State the actual systemic, technical, or psychological blocker driving the interaction.

2. CONVERSATIONAL EVIDENCE
- Provide 2-3 direct quotes or specific exchange points from the transcript that justify why the underlying problem is the true root cause.

3. STRATEGIC RESOLUTION
- Recommend a specific, actionable strategy to resolve the underlying issue rather than just patching the surface symptom.

Analyze the following customer support message and extract a standardized three-bullet summary.

Raw Customer Message:
{{customer_message}}

Urgency Level:
{{urgency_level}}

Context Notes:
{{context_notes}}

Rules:
- Output must contain exactly three distinct bullets in this exact format:
  - Problem: [Clear, concise description of the core issue]
  - What they tried: [Summary of troubleshooting steps already taken, or state "None mentioned" if absent without inventing details]
  - What they want: [Explicit statement of the desired outcome or resolution]
- Do not include extraneous conversational filler, greetings, or sign-offs.

Rewrite the following customer support draft response to ensure a calm, empathetic tone that validates the customer's frustration, avoids defensiveness, and removes any hint of customer blame.

Context of the customer's issue:
{{customer_context}}

Original draft response:
{{original_draft}}

Desired tone intensity:
{{tone_intensity}}

Provide only the rewritten, ready-to-send response.

Draft a friendly, concise customer support response for {{customer_name}}. Acknowledge their issue described as: {{issue_description}}. Provide the exact solution: {{solution_text}}. Keep the response strictly under 100 words, maintaining a warm, professional, and direct tone without unnecessary filler.

Analyze the following customer review and draft a personalized, professional email response.

Review Details:
- Customer Name: {{customer_name}}
- Rating: {{review_rating}} out of 5 stars
- Sentiment/Type: {{review_sentiment}}
- Review Text: {{customer_review}}
- Company Context: {{company_context}}

Instructions:
1. Write a clear, professional subject line.
2. Include a personalized salutation using {{customer_name}}.
3. Directly acknowledge the specific points raised in the review text.
4. Match the tone to the review sentiment (empathetic and solution-oriented for negative/neutral; appreciative for positive).
5. Do not invent specific refund amounts, discount codes, or policies not provided.
6. Provide a professional sign-off representing {{company_context}}.

Convert the following resolved support ticket into a clear, concise help centre article for self-service users.

Ticket Description:
{{ticket_description}}

Troubleshooting Steps Taken:
{{troubleshooting_steps}}

Final Resolution:
{{final_resolution}}

Target Audience:
{{target_audience}}

Output Requirements:
1. Provide a catchy, search-friendly title outlining the specific problem.
2. Include a brief introductory sentence describing who this article is for.
3. List step-by-step instructions using clear, imperative verbs based strictly on the provided troubleshooting steps and resolution.
4. Add a brief troubleshooting or 'Still need help?' sign-off.
5. Remove all ticket-specific conversational filler, greetings, metadata, and private user data. Do not invent extra troubleshooting steps.