Loading
Because anyone can save one and nobody owns them. Within a year there are nine variants of the same answer, three of which describe behaviour that changed two releases ago.
A new agent picks whichever comes up first and sends a customer something that is confidently out of date.
A canned response has an owner and a review date, and pulls live values — the customer's name, their plan, their next renewal — from the record rather than being a frozen block of text.
Internal notes sit on the same ticket but are visibly separate, in a different colour, and cannot be included in a reply by accident.
The library stays small enough to search. A response that has not been reviewed shows as stale to the person about to send it.
Agents stop rewriting the same explanation, and the explanation everyone sends is the one the product team last checked.
They will not send themselves. A macro drafts; a person sends, because a saved reply applied to the wrong situation reads worse than a slow answer.
And nothing about the internal note reaches the customer — it is not a permission setting, it is a separate field.
Nothing here is an integration. Each line is two products reading the same record from different sides.
A canned response has an owner and a review date, and pulls live values — the customer's name, their plan, their next renewal — from the record rather than being a frozen block of text.
The library stays small enough to search. A response that has not been reviewed shows as stale to the person about to send it.
They will not send themselves. A macro drafts; a person sends, because a saved reply applied to the wrong situation reads worse than a slow answer.
Fourteen days, every module, no card. Or half an hour with someone who will run it on your own records and tell you where it does not help.