What is a canned response?

A canned response is a block of reply text you save once and reuse many times. When a familiar question lands, you insert the matching saved reply, adjust the details for that specific customer, and send. The point is not to remove the human; it is to stop re-typing the same paragraphs and to keep your answers accurate and on-brand.

You will meet several names for the same idea. The wording differs by tool, but the concept is the same: stored, reusable reply text.

Canned response	The classic helpdesk term for a saved, reusable reply.
Saved reply	The same thing, named for what it is. Solves uses this term.
Macro	A reusable reply, sometimes bundled with small actions like setting a tag or status.
Snippet	A short reusable fragment, often inserted mid-reply rather than as a whole message.
Template	A reusable starting point for a full message, often with blanks to fill in.

Throughout this page you will see placeholders like [customer name] or [order number] in square brackets. Those are just a writing convention to show where you fill in the specific detail; they are illustrative copy, not a special field you have to set up.

The day-to-day shape is simple. You build a small library of replies for your most common questions, give each one a clear name, and pull the right one into the reply box when a matching question arrives. The saved text is the skeleton; you add the specifics before you send.

1. A familiar question arrives, for example a request for a refund or a delivery update.
2. You find the matching saved reply by name and insert it into your reply.
3. You adjust it for this customer: their name, their order, the actual situation.
4. You read it back as if you were the customer, then send.

Some tools let a single saved reply also nudge the ticket along, for example by adding a tag, so a refund reply and a refund tag travel together. That overlap is why the word macro exists. In Solves, saved replies and actions such as tags, status and priority are separate controls that sit beside each other on the ticket, so you stay in charge of what changes.

The obvious win is speed: you stop re-typing the same paragraphs twenty times a week. The quieter, bigger win is consistency. When a refund answer lives in one saved reply, every customer gets the same correct policy, whoever is on the queue, and when the policy changes you edit one place instead of hoping everyone remembers.

• Faster first replies, because the bones of the answer are ready to go.
• Consistent wording, so two customers with the same question get the same answer.
• Fewer mistakes, because agreed policy lines are written once and reused, not reinvented.
• A gentler load on newer teammates, who can lean on trusted wording while they learn.
• Easier updates, since changing one saved reply updates the answer everywhere it is used next.

None of this works if the replies sound like a machine wrote them. The goal is to remove the typing, not the care. A canned response should give a human a strong head start, then get out of the way.

A good saved reply reads like a thoughtful person who happens to be quick. These habits keep them warm, useful and easy to maintain.

Write to one real person

Open with the customer, not your process. Start with [customer name] where it fits, name the thing they asked about, and answer the actual question before you explain anything else. A reply that begins with the answer feels written for them, even when the words are reused.

Leave room to be specific

Build a deliberate gap into every reply where the real detail goes: the order number, the date you will have an update, the exact next step. Mark those gaps clearly with a placeholder like [order number] so it is obvious you must fill them in before sending, not after.

Keep it short and skimmable

Cut anything that is not load-bearing. One clear paragraph and, where it helps, a short list of steps beats a dense block. People read support email quickly, often on a phone, so the answer should be visible without scrolling.

Name them so people can find them

A saved reply nobody can find gets retyped by hand. Use plain, predictable names that describe the situation, for example Refund approved or Delivery delay, so the right reply is one obvious search away in a busy queue.

Review them on a schedule

Prices, hours, links and policies drift. Put a recurring date in the diary to read your saved replies as a customer would and fix anything that has gone stale, so old wording never goes out as if it were current.

Most canned-response failures come from leaning on them too hard, not from using them at all. These are the patterns that make customers feel processed rather than helped.

• Paste and send: firing off the saved text without reading the customer's actual message, so the reply answers a question they did not ask.
• Unfilled placeholders: an email that goes out still saying [customer name] or [order number] because someone skipped the personalising step.
• Too many to choose from: a sprawling library where finding the right reply takes longer than writing a fresh one.
• Set and forget: replies that quietly go out of date because no one ever reviews the prices, links or hours inside them.
• Wrong-context tone: a cheerful template used to answer an angry or distressing message, which reads as tone-deaf.
• One brand voice for several brands: reusing the same wording across brands that should each sound like themselves.

The fix for every one of these is the same discipline: a small, well-named, regularly reviewed set of replies, each treated as a draft you finish by hand. That last brand point is worth its own answer, which is where the right tooling helps.

Solves calls canned responses saved replies, and treats them as exactly what they are: a head start for a human reply. You insert a saved reply into the composer, edit it for the specific customer, then send. The saved text never leaves on its own.

Because Solves runs several brands from one queue, a saved reply can be scoped to a single brand or shared across the whole organisation. That means a Refund approved reply can carry one brand's warm, chatty tone and another brand's formal tone, while a genuinely shared answer stays in one place. The placeholders you see on this page, such as [customer name], are simply a writing convention you type and fill in yourself; they are not a Solves merge-field feature.

Saved replies sit alongside the rest of the ticket: states, assignment, priority, tags, public replies, private notes and wall-clock SLA timers. The saved reply gets the words out quickly; the rest of the desk makes sure the ticket is owned, timed and visible until it is genuinely resolved.

Macro	A reusable reply that may also trigger small ticket actions, such as adding a tag or changing status.
Snippet	A short reusable fragment of text, usually inserted partway through a reply rather than as a whole message.
Template	A reusable starting point for a full email, typically with blanks you fill in for each customer.
Help desk	The wider system that turns support email into owned, trackable tickets, where saved replies live.
Saved reply	The Solves name for a canned response: stored, reusable reply text you adapt and send.