Canned Response Library Builder
The Canned Response Library Builder generates a complete set of template responses for your support team, organized by category, with built-in personalization slots and tone variants. It replaces the ad-hoc "copy from the last similar ticket" approach with a structured library that ensures consistent quality regardless of which agent responds.
Support team leads building their first response library, managers standardizing tone across a growing team, and solo founders who want professional-sounding support without writing every response from scratch use this template. It is especially valuable during onboarding: new agents can deliver quality responses from day one by using the library while they learn the product.
The prompt works because it goes beyond generic templates by building in personalization points that prevent responses from sounding robotic. Each canned response includes slots where the agent inserts customer-specific details, along with guidance on when to use it, when to escalate instead, and how to adapt the tone based on customer sentiment. The result is a library that saves time without sacrificing the human feel that customers notice and appreciate.
This prompt is just the starting point
Score it with AI, optimize it with one click, track versions, and build your prompt library.
The Prompt
Build a canned response library for our support team based on the following: **Product/Service**: [YOUR PRODUCT OR SERVICE NAME AND A ONE-SENTENCE DESCRIPTION] **Support Channels**: [WHERE THESE RESPONSES WILL BE USED, e.g., "Email and live chat", "Zendesk tickets only", "Intercom chat and email"] **Team Tone**: [DESCRIBE YOUR BRAND VOICE, e.g., "Professional but friendly, like a helpful colleague. We use first names, avoid jargon, and keep it concise.", "Formal and enterprise-appropriate. No slang, no emojis, structured and thorough."] **Categories to Cover**: ``` [LIST THE TYPES OF TICKETS YOUR TEAM HANDLES MOST OFTEN, e.g., - Password reset and login issues - Billing questions and refund requests - Feature not working (bug reports) - Feature requests - Account cancellation - Onboarding help - Integration setup issues - General product questions] ``` **Personalization Requirements**: [ANY CUSTOMER DATA YOUR AGENTS CAN ACCESS, e.g., "We can see the customer's first name, plan type, and account age", "We only have their email address"] For each category, generate: ### [Category Name] **Response 1: [Scenario Label, e.g., "Standard Password Reset"]** - **When to use**: One sentence describing the exact situation this response fits - **When NOT to use**: Situations that seem similar but require a different approach - **Response**: [The full response text with personalization slots marked as [CUSTOMER NAME], [SPECIFIC DETAIL], etc. Each slot includes a brief note on what to insert.] - **Neutral tone variant**: [Same response adjusted for a matter-of-fact customer] - **Empathetic tone variant**: [Same response adjusted for a frustrated customer] - **Follow-up if no reply in 48h**: [A brief follow-up message] **Response 2: [Next Scenario]** [Same format] Requirements: - Generate 2-4 responses per category (covering the most common scenarios) - Every response must have at least one personalization slot (never fully generic) - Responses should be 50-150 words for chat, 100-250 words for email - Include a greeting and sign-off appropriate to the channel - Never promise specific timelines unless specified in the input (use "as soon as possible" or "within [YOUR SLA TIMEFRAME]") - End every response with a clear next step for the customer After the library, include: ### Library Usage Guide - How agents should select the right response - Rules for personalizing (what to always customize, what is okay to send as-is) - When to write a custom response instead of using the library - How to flag responses that need updating
Usage Tips
- Provide real ticket categories from your helpdesk: Pull your actual top 10 ticket types from Zendesk, Intercom, or whatever tool you use. Real categories produce responses that match real customer situations.
- Include your brand voice guidelines: The difference between "Hey Sarah!" and "Dear Ms. Johnson" matters. The more specific you are about tone, the more usable the responses become without editing.
- Test with your newest agent: Give the library to your least experienced team member and have them handle 10 tickets using only canned responses. Where they struggle or choose the wrong response, the library needs refinement.
- Update quarterly: Customer questions evolve with your product. Schedule a quarterly review to retire outdated responses, add new scenarios, and update any references to features that have changed.
Get more from this prompt
Save it, score it with AI, optimize it, and track every version. Free to start.