draft-responselisted

# /draft-response > If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Draft a professional, customer-facing response tailored to the situation, customer relationship, and communication context. ## Usage ``` /draft-response <context about the customer question, issue, or request> ``` Examples: - `/draft-response Acme Corp is asking when the new dashboard feature will ship` - `/draft-response Customer escalation — their integration has been down for 2 days` - `/draft-response Responding to a feature request we won't be building` - `/draft-response Customer hit a billing error and wants a resolution ASAP` ## Workflow ### 1. Understand the Context Parse the user's input to determine: - **Customer**: Who is the communication for? Look up account context if available. - **Situation type**: Question, issue, escalation, announcement, negotiation, bad news, good news, follow-up - **Urgency**: Is this time-sensitive? How long has the customer been waiting? - **Channel**: Email, support ticket, chat, or other (adjust formality accordingly) - **Relationship stage**: New customer, established, frustrated/escalated - **Stakeholder level**: End user, manager, executive, technical, business ### 2. Research Context Gather relevant background from available sources: **~~email:** - Previous correspondence with this customer on this topic - Any commitments or timelines previously shared - Tone and style of the exi