Creating Canned Responses
Building an AI-Powered Support System Without Code
⚡ Want to supercharge your customer support with quick, consistent answers? Meet canned responses—your secret weapon for handling FAQs efficiently!
Not every response belongs in a knowledge base, and not every answer should be visible to customers. So how do you use canned responses effectively? Let’s break it down! 👇
🎯 Canned Responses vs. Knowledge Base Articles
- ✅ Knowledge Base (Public) → Customer-facing, detailed guides, product information, and FAQs.
- ✅ Canned Responses (Private) → Internal support replies for sensitive, situational, or temporary issues.
🛠️ When to Use Canned Responses
💡 Sensitive Information → Account adjustments, special pricing, or private troubleshooting.
💡 Temporary Issues → Quick, consistent updates about downtime or minor service disruptions.
💡 Internal Messages → Used within the team, like “We’re aware of this issue and working on it.”
⚠️ A Quick AI Training Tip!
🚫 Don’t train your AI on internal-only canned responses. If a temporary issue is resolved, but AI keeps saying, “We’re aware and working on it,” it confuses customers!
- ✅ Instead, train AI on evergreen, reliable information that customers can always trust.
📌 FAQs & Knowledge Base: When to Use Each?
- ✔️ Canned Responses → For private, short-term, or sensitive information.
- ✔️ Knowledge Base & FAQs → For public, long-term, and frequently asked questions.
🔥 Recap: Smarter AI, Better Support
Using canned responses + a strong knowledge base makes your AI smart enough to know when to respond publicly and when to keep it private—leading to a better, more professional customer experience.
🔜 Next Lesson: Intent Recognition! Learn how AI understands customer questions and matches them to the right response. Stay tuned!
Transcript
Auto-generated from the video captions; it may contain errors.
right so let's talk about canid responses they're the secret weapons for quick consistent answers these are the pre prepared replies to Common queries and they're essential for training your AI to respond accurately but there is a catch not every response belong in a knowledge base and not every answer should be visible to customers so let's break it down love what you're learning give this video a thumbs up and subscribe so you never miss a lesson from your customer Academy what's the difference between a count response and a noise bace think of your knowledge base as public facing is where your customers find Details guides out to things that you're happy to share openly can responses on the other hand are private they're used by suppor team in chats or email to and sensitive or very specific situation for example troubleshooting tips for Niche issues or responses with private Account
Details bong in caned responses not your knowledge base so when to use canid responses canid responses shine in a few key scenario like with sensitive information use them for details you want to keep private count adjustments or pricing exceptions also for temporary issues if a feature is down and there is a minor issue affecting a small group canet responses let you provide consistent upgrade without creating a public knowledge based article also for internal messages some things are for internal use only like we're aware of this issue and our team is working on it they're great for your team but not something you would want to publish it's something to watch out for avoid training your AI with Cent responses about internal processes or temporary issues for example if a customer is reporting a bu and you got a a kind of response with we're working on this issue and
we'll let you know about it um this would be great if you shared it but if then your AI using it and consider the de ass sold that might lead the ey to close the tickets and that buag or that issue will never get to your team Focus your AI training on consistent Evergreen Information that's appropriate for customers to hear directly kind of responses are perfect for private behind the scene communication while fqs and knowledge based articles on the other hands are public facing tools that that customer find answers on their own as a r CH use C responses for private or temporary informations use knowledge based articles and fq for public reliable and frequently asked questions by strategically using can responsiveness fiq you will build an AI that knows when to be direct and when to keep things private this creates a professional customer focus support experience let's
get started