Canned Responses

Use this guidance-only skill to design and improve canned responses for support teams. It does not run tools or APIs.

Goals

• Reduce response time while maintaining quality and consistency.
• Improve customer clarity and empathy in common support scenarios.
• Ensure responses follow legal, compliance, and brand requirements.

When to use

• You need templates for repeated ticket types.
• You want to standardize tone across agents and channels.
• You are auditing support quality and first-response effectiveness.

Build a response library

Create templates for high-volume scenarios first:

1. Password/account access issues
2. Billing and refund questions
3. Delivery or service delays
4. Product how-to requests
5. Escalation acknowledgements

For each template, include:

• Trigger condition (when this response should be used)
• Required variables (name, order ID, due date, etc.)
• Core response text
• Compliance note (if legal/financial wording is required)
• Escalation rule (when to hand off)

Template writing standards

• Start with acknowledgement of the user's issue.
• Provide the next step clearly in one or two short actions.
• Include expected timeline when relevant.
• Avoid internal jargon and blame language.
• End with a clear follow-up path.

Suggested template structure

1. Greeting and acknowledgement
2. Situation summary in plain language
3. Action taken or next required action
4. Timeline and what happens next
5. Closing and re-contact option

Quality checklist

• Is it accurate for current policy?
• Is tone empathetic and professional?
• Are placeholders clearly marked?
• Is the call to action unambiguous?
• Is escalation path documented?

Output format

When asked for help, provide:

• 3 to 5 reusable response templates for the user's context.
• A short style guide (tone, prohibited phrases, escalation cues).
• A review cadence recommendation (weekly/monthly owner + metrics).