--- name: draft-response description: Draft a professional customer-facing response tailored to the situation and relationship. Use when answering a product question, responding to an escalation or outage, delivering bad news like a delay or won't-fix, declining a feature request, or replying to a billing issue. argument-hint: "" --- # /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 ``` 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 existing thread **~~chat:** - Internal discussions about this customer or topic - Any guidance from product, engineering, or leadership - Similar situations and how they were handled **~~CRM (if connected):** - Account details and plan level - Contact information and key stakeholders - Previous escalations or sensitive issues **~~support platform (if connected):** - Related tickets and their resolution - Known issues or workarounds - SLA status and response time commitments **~~knowledge base:** - Official documentation or help articles to reference - Product roadmap information (if shareable) - Policy or process documentation ### 3. Generate the Draft Produce a response tailored to the situation: ``` ## Draft Response **To:** [Customer contact name] **Re:** [Subject/topic] **Channel:** [Email / Ticket / Chat] **Tone:** [Empathetic / Professional / Technical / Celebratory / Candid] --- [Draft response text] --- ### Notes for You (internal — do not send) - **Why this approach:** [Rationale for tone and content choices] - **Things to verify:** [Any facts or commitments to confirm before sending] - **Risk factors:** [Anything sensitive about this response] - **Follow-up needed:** [Actions to take after sending] - **Escalation note:** [If this should be reviewed by someone else first] ``` ### 4. Run Quality Checks Before presenting the draft, verify: - [ ] Tone matches the situation and relationship - [ ] No commitments beyond what's authorized - [ ] No product roadmap details that shouldn't be shared externally - [ ] Accurate references to previous conversations - [ ] Clear next steps and ownership - [ ] Appropriate for the stakeholder level (not too technical for executives, not too vague for engineers) - [ ] Length is appropriate for the channel (shorter for chat, fuller for email) ### 5. Offer Iterations After presenting the draft: - "Want me to adjust the tone? (more formal, more casual, more empathetic, more direct)" - "Should I add or remove any specific points?" - "Want me to make this shorter/longer?" - "Should I draft a version for a different stakeholder?" - "Want me to draft the internal escalation note as well?" - "Should I prepare a follow-up message to send after [X days] if no response?" --- ## Customer Communication Best Practices ### Core Principles 1. **Lead with empathy**: Acknowledge the customer's situation before jumping to solutions 2. **Be direct**: Get to the point — customers are busy. Bottom-line-up-front. 3. **Be honest**: Never overpromise, never mislead, never hide bad news in jargon 4. **Be specific**: Use concrete details, timelines, and names — avoid vague language 5. **Own it**: Take responsibility when appropriate. "We" not "the system" or "the process" 6. **Close the loop**: Every response should have a clear next step or call to action 7. **Match their energy**: If they're frustrated, be empathetic first. If they're excited, be enthusiastic. ### Response Structure For most customer communications, follow this structure: ``` 1. Acknowledgment / Context (1-2 sentences) - Acknowledge what they said, asked, or are experiencing - Show you understand their situation 2. Core Message (1-3 paragraphs) - Deliver the main information, answer, or update - Be specific and concrete - Include relevant details they need 3. Next Steps (1-3 bullets) - What YOU will do and by when - What THEY need to do (if anything) - When they'll hear from you next 4. Closing (1 sentence) - Warm but professional sign-off - Reinforce you're available if needed ``` ### Length Guidelines - **Chat/IM**: 1-4 sentences. Get to the point immediately. - **Support ticket response**: 1-3 short paragraphs. Structured and scannable. - **Email**: 3-5 paragraphs max. Respect their inbox. - **Escalation response**: As long as needed to be thorough, but well-structured with headers. - **Executive communication**: Shorter is better. 2-3 paragraphs max. Data-driven. ## Tone and Style Guidelines ### Tone Spectrum | Situation | Tone | Characteristics | |-----------|------|----------------| | Good news / wins | Celebratory | Enthusiastic, warm, congratulatory, forward-looking | | Routine update | Professional | Clear, concise, informative, friendly | | Technical response | Precise | Accurate, detailed, structured, patient | | Delayed delivery | Accountable | Honest, apologetic, action-oriented, specific | | Bad news | Candid | Direct, empathetic, solution-oriented, respectful | | Issue / outage | Urgent | Immediate, transparent, actionable, reassuring | | Escalation | Executive | Composed, ownership-taking, plan-presenting, confident | | Billing / account | Precise | Clear, factual, empathetic, resolution-focused | ### Tone Adjustments by Relationship Stage **New Customer (0-3 months):** - More formal and professional - Extra context and explanation (don't assume knowledge) - Proactively offer help and resources - Build trust through reliability and responsiveness **Established Customer (3+ months):** - Warm and collaborative - Can reference shared history and previous conversations - More direct and efficient communication - Show awareness of their goals and priorities **Frustrated or Escalated Customer:** - Extra empathy and acknowledgment - Urgency in response times - Concrete action plans with specific commitments - Shorter feedback loops ### Writing Style Rules **DO:** - Use active voice ("We'll investigate" not "This will be investigated") - Use "I" for personal commitments and "we" for team commitments - Name specific people when assigning actions ("Sarah from our engineering team will...") - Use the customer's terminology, not your internal jargon - Include specific dates and times, not relative terms ("by Friday January 24" not "in a few days") - Break up long responses with headers or bullet points **DON'T:** - Use corporate jargon or buzzwords ("synergy", "leverage", "paradigm shift") - Deflect blame to other teams, systems, or processes - Use passive voice to avoid ownership ("Mistakes were made") - Include unnecessary caveats or hedging that undermines confidence - CC people unnecessarily — only include those who need to be in the conversation - Use exclamation marks excessively (one per email max, if any) ## Situation-Specific Approaches **Answering a product question:** - Lead with the direct answer - Provide relevant documentation links - Offer to connect them with the right resource if needed - If you don't know the answer: say so honestly, commit to finding out, give a timeline **Responding to an issue or bug:** - Acknowledge the impact on their work - State what you know about the issue and its status - Provide workaround if available - Set expectations for resolution timeline - Commit to updates at regular intervals **Handling an escalation:** - Acknowledge the severity and their frustration - Take ownership (no deflecting or excuse-making) - Provide a clear action plan with timeline - Identify the person accountable for resolution - Offer a meeting or call if appropriate for the severity **Delivering bad news (feature sunset, delay, can't-fix):** - Be direct — don't bury the news - Explain the reasoning honestly - Acknowledge the impact on them specifically - Offer alternatives or mitigation - Provide a clear path forward **Sharing good news (feature launch, milestone, recognition):** - Lead with the positive outcome - Connect it to their specific goals or use case - Suggest next steps to capitalize on the good news - Express genuine enthusiasm **Declining a request (feature request, discount, exception):** - Acknowledge the request and its reasoning - Be honest about the decision - Explain the why without being dismissive - Offer alternatives when possible - Leave the door open for future conversation ## Response Templates for Common Scenarios ### Acknowledging a Bug Report ``` Hi [Name], Thank you for reporting this — I can see how [specific impact] would be frustrating for your team. I've confirmed the issue and escalated it to our engineering team as a [priority level]. Here's what we know so far: - [What's happening] - [What's causing it, if known] - [Workaround, if available] I'll update you by [specific date/time] with a resolution timeline. In the meantime, [workaround details if applicable]. Let me know if you have any questions or if this is impacting you in other ways I should know about. Best, [Your name] ``` ### Acknowledging a Billing or Account Issue ``` Hi [Name], Thank you for reaching out about this — I understand billing issues need prompt attention, and I want to make sure this gets resolved quickly. I've looked into your account and here's what I'm seeing: - [What happened — clear factual explanation] - [Impact on their account — charges, access, etc.] Here's what I'm doing to fix this: - [Action 1 — with timeline] - [Action 2 — if applicable] [If resolution is immediate: "This has been corrected and you should see the change reflected within [timeframe]."] [If needs investigation: "I'm escalating this to our billing team and will have an update for you by [specific date]."] I'm sorry for the inconvenience. Let me know if you have any questions about your account. Best, [Your name] ``` ### Responding to a Feature Request You Won't Build ``` Hi [Name], Thank you for sharing this request — I can see why [capability] would be valuable for [their use case]. I discussed this with our product team, and this isn't something we're planning to build in the near term. The primary reason is [honest, respectful explanation — e.g., it serves a narrow use case, it conflicts with our architecture direction, etc.]. That said, I want to make sure you can accomplish your goal. Here are some alternatives: - [Alternative approach 1] - [Alternative approach 2] - [Integration or workaround if applicable] I've also documented your request in our feedback system, and if our direction changes, I'll let you know. Would any of these alternatives work for your team? Happy to dig deeper into any of them. Best, [Your name] ``` ### Outage or Incident Communication ``` Hi [Name], I wanted to reach out directly to let you know about an issue affecting [service/feature] that I know your team relies on. **What happened:** [Clear, non-technical explanation] **Impact:** [How it affects them specifically] **Status:** [Current status — investigating / identified / fixing / resolved] **ETA for resolution:** [Specific time if known, or "we'll update every X hours"] [If applicable: "In the meantime, you can [workaround]."] I'm personally tracking this and will update you as soon as we have a resolution. You can also check [status page URL] for real-time updates. I'm sorry for the disruption to your team's work. We take this seriously and [what you're doing to prevent recurrence if known]. [Your name] ``` ### Following Up After Silence ``` Hi [Name], I wanted to check in — I sent over [what you sent] on [date] and wanted to make sure it didn't get lost in the shuffle. [Brief reminder of what you need from them or what you're offering] If now isn't a good time, no worries — just let me know when would be better, and I'm happy to reconnect then. Best, [Your name] ``` ## Follow-up and Escalation Guidance ### Follow-up Cadence | Situation | Follow-up Timing | |-----------|-----------------| | Unanswered question | 2-3 business days | | Open support issue | Daily until resolved for critical, 2-3 days for standard | | Post-meeting action items | Within 24 hours (send notes), then check at deadline | | General check-in | As needed for ongoing issues | | After delivering bad news | 1 week to check on impact and sentiment | ### When to Escalate **Escalate to your manager when:** - Customer threatens to cancel or significantly downsell - Customer requests exception to policy you can't authorize - An issue has been unresolved for longer than SLA allows - Customer requests direct contact with leadership - You've made an error that needs senior involvement to resolve **Escalate to product/engineering when:** - Bug is critical and blocking the customer's business - Feature gap is causing a competitive loss - Customer has unique technical requirements beyond standard support - Integration issues require engineering investigation **Escalation format:** ``` ESCALATION: [Customer Name] — [One-line summary] Urgency: [Critical / High / Medium] Customer impact: [What's broken for them] History: [Brief background — 2-3 sentences] What I've tried: [Actions taken so far] What I need: [Specific help or decision needed] Deadline: [When this needs to be resolved by] ``` --- Attribution added by YourAIKit. It is not part of the upstream file. - Source: https://github.com/anthropics/knowledge-work-plugins/tree/main/customer-support/skills/draft-response - Credit: Anthropic, Knowledge Work Plugins (customer-support) - Upstream copy: anthropics/knowledge-work-plugins at commit 33d3dea41a341b341d4f5da2e8801ae0c89be2b8, customer-support/skills/draft-response/SKILL.md - Copyright: held by the upstream authors credited above - License: Apache-2.0. Full text: https://youraikit.com/licenses/anthropics-knowledge-work-plugins-customer-support/LICENSE - The full upstream license text (LICENSE) follows. License (LICENSE): ```text Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. "You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License. "Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. "Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. "Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). "Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. "Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution." "Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work. 2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form. 3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed. 4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions: (a) You must give any other recipients of the Work or Derivative Works a copy of this License; and (b) You must cause any modified files to carry prominent notices stating that You changed the files; and (c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and (d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License. 5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions. 6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file. 7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License. 8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. 9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability. END OF TERMS AND CONDITIONS APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. ```