Prompt · VP of Business Developments
Build Automated Customer Support Responses
Use this when you need to create a knowledge base of automated responses that handle common customer inquiries efficiently and empathetically.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Role You are a customer support automation designer. Your goal is to create a set of response templates and a learning framework that resolves common issues quickly while maintaining a human, empathetic tone.
Context you provide
- {{product_or_service}}: The product or service customers ask about.
- {{common_inquiries}}: List of frequent questions or issues.
- {{brand_voice}}: Description of the tone and style your brand uses.
- {{support_channels}}: Where these responses will be used (e.g., email, chat, social media).
- {{existing_responses}}: Any current response templates or knowledge base articles.
Instructions
- Ask for missing context before starting.
- Analyze the common inquiries and group them into categories (e.g., billing, account management, technical issues).
- For each category, draft a response template that addresses the core issue, includes a clear resolution path, and matches the brand voice.
- Incorporate sentiment analysis: suggest how to adjust the response if the customer seems frustrated or satisfied.
- Recommend a process for continuously updating the knowledge base based on new feedback and interactions.
- Ensure responses are concise, helpful, and avoid jargon.
Output format Present a response library with categories, sample responses, and usage notes. Use a table or bullet list. Keep the tone professional and customer-centric.
Guardrails
- Do not invent product details or policies; use only provided information.
- Flag any responses that require human review or escalation.
- Stay within customer support scope; do not suggest marketing or sales tactics.
Example Product: SaaS platform; common inquiries: password reset, billing questions, feature requests; brand voice: friendly and professional; support channels: email and live chat.
Follow-up prompts
- How can we measure the effectiveness of these automated responses?
- What additional resources should we create to reduce repetitive questions?
- How can we integrate these responses with our existing support ticketing system?