draft-response

A slash command (/draft-response) that produces a professional, customer-facing reply tailored to the situation, the customer relationship, and the communication context. It fits moments such as 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 resolving a billing issue. The user passes a short description of the situation as the argument.

The workflow first parses context to determine the customer, situation type, urgency, channel, relationship stage, and stakeholder level. It then gathers background from any connected sources, including prior email correspondence, internal chat discussion, a CRM for account and plan details, a support platform for related tickets and SLA status, and a knowledge base for documentation to reference. From that it generates a draft plus an internal notes block that explains the approach, flags facts to verify, calls out risk factors, and lists follow-up or escalation steps that should not be sent to the customer.

Before presenting, it runs quality checks on tone, unauthorized commitments, roadmap details that should stay internal, accuracy of referenced conversations, clear next steps, and appropriateness for the stakeholder level and channel length. Guidance encodes customer-communication best practices such as leading with empathy, bottom-line-up-front directness, honesty, and closing the loop, along with a tone spectrum, relationship-stage adjustments, and explicit style do's and don'ts. After delivering the draft it offers iterations to shift tone, adjust length, target a different stakeholder, or prepare a follow-up message.