response-drafting_skill

Overview

This skill drafts professional, empathetic customer-facing responses tailored to situation, urgency, and channel. It converts incident details, tickets, or feature notes into clear, action-oriented messages that respect relationship stage and stakeholder level. Use it to produce responses that lead with empathy, own outcomes, and close the loop with specific next steps.

How this skill works

The skill inspects the situation type (e.g., bug, outage, billing, feature request), the customer relationship stage, and the communication channel to select tone and structure. It generates a concise acknowledgment, a clear core message with relevant details, explicit next steps, and a warm closing. It enforces writing rules like active voice, specific dates, named owners, and minimal jargon to keep responses actionable and trustworthy.

When to use it

• Responding to support tickets or bug reports
• Communicating outages or incident updates
• Replying to billing or account inquiries
• Handling feature requests and roadmap rejections
• Drafting escalation messages to leadership or internal teams

Best practices

• Lead with empathy and acknowledge impact before solutions
• Use bottom-line-up-front: concise core message first
• State concrete commitments with dates, names, and owners
• Offer clear next steps for both you and the customer
• Match tone to situation and relationship stage (more formal for new customers)
• Avoid internal jargon and never deflect blame

Example use cases

• Acknowledging a bug report with known cause, workaround, and ETA for fix
• Sending an outage notification with impact summary, current status, and update cadence
• Responding to a billing discrepancy with factual findings and remediation steps
• Tactfully declining a feature request while proposing alternatives and logging feedback
• Escalating a critical customer issue to leadership with a one-line summary and required decision