draft-response

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md . Draft a professional, customer-facing response tailored to the situation, customer relationship, and communication context. Examples: Parse the user's input to determine: Gather relevant background from available sources: ~~email: ~~chat: ~~CRM (if connected): ~~support platform (if connected): ~~knowledge base: Produce a response tailored to the situation: Before presenting the draft, verify: After presenting the draft: For most customer communications, follow this structure: New Customer (0-3 months): Established Customer (3+ months): Frustrated or Escalated Customer: DO: DON'T: Answering a product question: Responding to an issue or bug: Handling an escalation: Delivering bad news (feature sunset, delay, can't-fix): Sharing good news (feature launch, milestone, recognition): Declining a request (feature request, discount, exception): Escalate to your manager when: Escalate to product/engineering when: Escalation format: - /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 - Customer : Who is the communication for? Look up...