What it is
The Canned Response Library is a spreadsheet you can load straight into your help desk: a starter set of live-chat macros — also called snippets or saved replies — organized by the stage of the conversation they belong to. Greetings and openings, holding and investigating lines, resolving and explaining responses, and closing and follow-up messages each get their own section, with a suggested shortcut (like /greet or /onit), the macro text itself, and a 'when to use' note that tells agents which moment each reply is for. Every macro carries {{placeholder}} tokens — {{name}}, {{agent}}, {{order}} — that you remap to your platform's merge syntax.
Beyond the library itself, the workbook includes a Usage Tracker sheet that turns the macro collection into a managed asset rather than a junk drawer. You enter each macro's monthly use count and its average CSAT, and the sheet computes each macro's share of total usage and a recommendation: high-volume macros sitting below your team's CSAT benchmark are flagged as the top rewrite candidates, while strong, well-used macros are left alone. A volume-weighted CSAT figure shows how the whole library performs in proportion to how often each reply is actually sent, so a rarely-used perfect macro can't mask a heavily-used weak one.
It is a starting library, not a finished policy. The Instructions sheet sets the golden rules — keep each macro to 1-3 short lines, lead with the answer then the reason, match a warm-but-concise brand tone, and treat every macro as something an agent personalizes before sending rather than fires verbatim. The benchmark guidance is deliberately conservative: mature chat teams keep a focused set of 30-60 high-quality macros rather than hundreds of stale ones, and review the library on a regular cadence.
What it's used for
A canned-response library exists to make agents fast without making them sound like robots. In a medium where visitors expect replies in seconds and a single agent may be juggling three or four conversations at once, well-written macros are the difference between consistent, on-brand answers and improvised, uneven ones. Teams use this library to:
- ✓ Seed a help desk with a structured, stage-organized set of macros — greetings, holding lines, resolutions, and closings — instead of writing them ad hoc as situations arise.
- ✓ Assign keyboard shortcuts (/greet, /onit, /reset, /close) so agents insert the right reply in a keystroke and keep response times low across concurrent chats.
- ✓ Standardize tone so a billing answer and a support answer both read as warm and concise, no matter which agent typed them.
- ✓ Reduce dead air during investigations with ready holding lines that give a reason and a rough timeframe, since unexplained silence is the fastest way to lose a chat.
- ✓ Track macro performance in the Usage Tracker, scoring each on volume and CSAT to surface which replies are pulling their weight and which are dragging satisfaction down.
- ✓ Prune and rewrite underperformers — high-volume, below-benchmark macros — using the recommendation column instead of guessing which lines need work.
- ✓ Keep the library lean at 30-60 strong macros, reviewed on a cadence, rather than letting it bloat into hundreds of stale, conflicting replies.
Who uses it
The macro library is shared infrastructure that several roles create, maintain, and consume. Each interacts with a different part of the workbook:
Context & good to know
In live chat, tone is the whole product. There is no smile, no warmth in a voice, and no body language — the words carry one hundred percent of the experience. That makes macros a double-edged tool: a well-crafted, personalized macro delivers a warm answer in a fraction of the time, while a stiff or generic one read verbatim makes the whole interaction feel like talking to a vending machine. The library's insistence on 1-3 short lines, answer-first structure, and a personalization touch is what keeps the speed of macros from costing you the warmth.
The Usage Tracker exists because macro libraries decay. Teams add replies for one-off situations, copy near-duplicates, and never delete anything, until agents are scrolling past dozens of stale snippets to find the right one. By scoring each macro on volume and CSAT and computing a volume-weighted library CSAT, the tracker reframes the library as a performance-managed asset: the macros that actually get sent and the satisfaction they produce are what matter, not the raw count of entries.
This library pairs naturally with a greeting and tone guide. The tone guide sets the rules for how agents open, sustain, and close conversations; the macro library is where those rules become ready-to-paste language. The two together let a chat team scale headcount without scaling inconsistency — new agents inherit both the philosophy and the exact words, and QA can trace a low-CSAT pattern back to a specific macro and rewrite it.
Implementation specifics vary by platform but the concept is universal. Intercom calls them saved replies and supports rich snippets, LiveChat and Olark use canned responses with slash shortcuts, and Tidio offers saved responses on lighter plans. Whatever the tool, the workflow is the same: import the text, map the placeholders, assign shortcuts, and then let the Usage Tracker tell you which replies to keep sharpening over time.