They make it robotic only if used badly — i.e. with blind copy-paste, no personalisation. A canned response sent raw (without adapting to the customer's case, without their name, without accounting for the precise context of their request) is spotted immediately and produces the worst effect: customers feel they received an automatic reply that doesn't really answer their question, that they're treated like a number by a machine — which is very frustrating, especially if they took the trouble to explain their particular situation. That's the dehumanisation trap. But well used, canned responses are an excellent tool combining efficiency and quality. The key is to treat them as a starting point to personalise, never as a final send: start from the template (which guarantees accuracy and saves time on the substantive structure), then adapt it to the specific case — personalise (customer name, reference to their request), adjust the content to their particular situation, add the missing context, and check the answer really answers their question (not a generic one). This way, customers get an answer that is both fast and accurate (thanks to the template) and personalised (thanks to adaptation) — the best of both worlds. The golden rule: the canned response is a foundation, the human brings personalisation. Well balanced, customers won't even perceive a template was used; they'll perceive a clear, accurate answer suited to their case. Canned responses aren't the enemy of relationship quality: their lazy use (copy-paste without thinking) is. Used as an aid you personalise, they serve both efficiency and the customer.

They are two close but different-audience tools, often complementary. The internal knowledge base is a repository for agents/professionals: it gathers all the information, detailed procedures, answers to frequent questions, edge cases, technical details… teams need to handle requests fast, accurately and consistently. It can contain internal information, complex procedures, details customers don't need to see. The FAQ / help centre (section 5.2) is for customers themselves: it's a public, simplified version letting customers alone find answers to simple, common questions (self-service), without contacting customer service. It's written in accessible language, "how-to" oriented, and covers the most frequent cases. The two often feed each other: recurring questions identified service-side (internal base) feed the public FAQ; and a good FAQ unclogs customer service (customers solve simple cases alone, agents focus on complex requests). The general idea: the internal base equips agents to answer well, the FAQ empowers customers for simple requests. An effective organisation has both, consistent with each other and regularly updated (an obsolete FAQ or base misleads). Both rest on the same principle: capitalising on answers to recurring questions to gain efficiency and consistency — one internally, one customer-side.