name	support-reply
description	Draft a customer-facing support reply. Use when writing the final answer to a customer ticket - covers structure, tone, and length so every reply lands the same way.

Support reply skill

A repeatable format for the customer-facing reply, so every response lands the same way regardless of which model or sub-agent drafts it.

When composing the final reply to a customer ticket, once the research findings are in hand.

One-line acknowledgment - name the problem and the order, showing you read the ticket. One sentence.
The fix - the specific documented fix (firmware version + steps), or, if none exists, the best next step and what you're doing about it.
Close - what happens next (e.g., "reply here if it persists and we'll escalate"). No sign-off boilerplate.

Under 150 words.
No forbidden phrases: "we apologize for any inconvenience", "thank you for your patience", "we value your business".
Cite the fix exactly as the knowledge base states it - don't paraphrase a version number.

name	support-reply
description	Draft a customer-facing support reply. Use when writing the final answer to a customer ticket - covers structure, tone, and length so every reply lands the same way.

A repeatable format for the customer-facing reply, so every response lands the same way regardless of which model or sub-agent drafts it.

When composing the final reply to a customer ticket, once the research findings are in hand.

One-line acknowledgment - name the problem and the order, showing you read the ticket. One sentence.
The fix - the specific documented fix (firmware version + steps), or, if none exists, the best next step and what you're doing about it.
Close - what happens next (e.g., "reply here if it persists and we'll escalate"). No sign-off boilerplate.

Under 150 words.
No forbidden phrases: "we apologize for any inconvenience", "thank you for your patience", "we value your business".
Cite the fix exactly as the knowledge base states it - don't paraphrase a version number.

support-reply