Canned response
What is a canned response and when does it work against you?
A canned response saves typing on questions that keep returning. It becomes harmful the moment it answers a question that was slightly different.
In short
A canned response is a pre-written text an agent inserts into a conversation, usually with fields filled automatically with the customer's name or order number. It's meant for questions whose answer is always the same, and differs from an auto-reply in that a person deliberately picks and adapts it.
Why a canned response can create more work
The saving is visible and the cost isn't. An agent under time pressure picking the response that looks closest sends a text answering most of the question and missing the part the customer cared about. That customer replies, and the second conversation is longer than the first needed to be.
Measure that effect before expanding a library. For the five most-used responses, check how often a second message from the customer follows. If one stands out, that text isn't answering the question.
What marks a good canned response
The usable form is short and incomplete. It covers the part that's always the same and leaves the sentence describing the case to the agent. A text that writes the whole message gets sent without reading; a text that writes half forces a look at the question.
It should also state what the customer can now expect. Most canned responses say what happened and forget when the next moment is. That single sentence prevents most follow-up questions.
Canned response, knowledge base article or AI draft?
These three need the same source and are usually maintained separately. That's exactly why after a year the canned responses claim something different from the knowledge base.
The workable split: the policy is fixed once in the knowledge base, and both the canned response and the AI draft take content from it. If a period changes, you change it in one place. Copy the text into fifteen canned responses and in practice you'll update twelve, leaving three behind.
Where it goes wrong
A library nobody can search
Beyond twenty texts, choosing becomes the work itself. Without keyword search everyone grabs the same five at the top, even when a better one exists.
Putting policy in the text instead of in a source
A return period stated in twelve canned responses is twelve places to update. Reference the source or fill the field automatically.
The customer's name as the only personal element
"Dear Jan" above a text that's otherwise about nobody reads as a template. A message becomes personal from the sentence about this case, not from the salutation.
Never clearing out
A library grows by itself and never shrinks by itself. Every six months, look at which texts were used zero times in that period and delete them.
What to do this week
Look up your five most-used canned responses and read them the way a customer reads them. Does each of the five say when the customer can expect the next message? Add that sentence where it's missing. It's the cheapest change in this whole category, because it removes exactly the chaser emails.
What this looks like in a system
In Cuego canned responses sit next to the conversation and fill customer name, order number and tracking link from data that's already there. The policy itself comes from your knowledge base, so a changed return period is updated in one place and carries into both the responses and the AI drafts. For each response you can see how often it was used, so you can clear out the texts nobody picks.
KnowledgeRelated terms
Knowledge base
A knowledge base is the recorded version of what your team knows. Without an owner and a rhythm it's partly wrong within six months.
Read onWorkflow
A workflow is a sequence of steps that runs by itself once something happens. The skill is choosing which steps deserve it.
Read onQuality monitoring
Quality monitoring is reading conversations yourself instead of waiting for customer scores. It's the only measure showing whether the answer was also correct.
Read on