Saved reply text for the questions your team answers again and again.
Canned response. A canned response is a pre-written reply template a support team inserts instead of typing the same answer repeatedly. Canned responses cover recurring questions — billing, password resets, shipping windows — and usually support placeholders for names and order details. Teams use canned responses to answer faster and keep wording consistent.
Canned responses live in a shared library inside the support tool. An agent inserts one with a keyboard shortcut or a search, placeholders fill in from the conversation — the customer’s name, the order number — and the agent edits before sending. Because the library is shared, a policy change is fixed in one place instead of in forty people’s muscle memory.
The craft detail most teams miss: the best canned responses are composable blocks, not complete emails. A block answers exactly one thing — how refunds are timed, how to reset two-factor auth — and an agent stacks two or three blocks with a personal opening line. Templates written as finished letters force awkward surgery every time the customer asked two questions, and the seams are what customers smell when a reply feels canned. Blocks also survive channel changes: the same refund-timing block reads naturally in an email and in a chat reply, where a formal letter template cannot.
The obvious wins are speed and consistency: common questions get answered in seconds, and every customer hears the same correct version of the policy. The subtler win is accuracy under change — when terms change, the template changes once, and nobody keeps sending last quarter’s answer from memory.
Done badly, canned responses damage exactly what they were meant to protect. A template that answers the frequent question while ignoring the customer’s second sentence improves first response time and lowers satisfaction at the same moment — the metric goes up, the relationship goes down. Speed that skips reading is not speed; it is a second round trip.
Mine your sent mail: the replies your team has typed three times this month are your first templates. Write them as blocks, keep the tone of your best writer, and review the library quarterly — stale templates spread stale answers with perfect efficiency. Name templates by the question they answer (“refund timing”), not by an internal code, so agents find the right one in two keystrokes instead of scrolling a list; a library nobody can navigate quietly stops being used, and the retyping returns.
Then watch the edit rate, because it is the library’s built-in roadmap. A template agents heavily rewrite every time is a bad template — rewrite it once, properly. A high-volume template nobody ever edits is telling you something better: that answer no longer needs a human at all, and belongs in a help center article or an automated reply instead.
Canned responses sit halfway between typing and automation — these entries cover the neighbors on both sides.
Give your customers faster answers and your team their evenings back.
Desktop and mobile. Free for solo.