LazyBoard team · · 3 min read
What is a canned response?
A canned response is a saved message used for a recurring question or situation. It can be a complete acknowledgment, a troubleshooting step, or a short paragraph you combine with a personal reply. The goal is to reuse accurate wording without losing the context of the conversation.
The most useful responses have clear boundaries. “Request received” should acknowledge a request; it should not claim that you have investigated it. “Issue resolved” belongs after you have confirmed a fix, not simply after opening a ticket.
Use a three-part structure
- Acknowledge the specific issue. Briefly say what you understand. “I see the export stops before the file finishes” is more useful than a generic thank-you.
- Explain the next action. Tell the customer what you will do or what you need from them. Ask for one focused set of details, and avoid making them repeat information already in the conversation.
- Set an expectation you can meet. Include a next update time when you can commit to it. If you do not know when the problem will be fixed, say that rather than guessing.
Compare a generic reply with a useful one
Generic: “Thank you for contacting us. We apologize for the inconvenience. Your request is important to us.”
More useful: “Hi [Name], I understand that [specific issue] is preventing you from [task]. I’ll check [next step] and update you by [day and time]. In the meantime, could you share [needed detail]?”
The second version gives the reader something concrete: a description of the problem, an action, and an expectation. Replace every bracketed detail before sending. Remove the final question if you already have everything needed.
Save building blocks, not just whole emails
A long saved response can be awkward when only one paragraph fits the situation. Keep separate snippets for an acknowledgment, a progress update, a workaround, and a closing. That lets you assemble a relevant reply without deleting half of a template each time.
For example, use /received for a new request, /progress while work is ongoing, and /resolved after verifying the outcome. Store them in a Customer replies folder with titles that explain when to use each one.
Our six editable customer service templates include those situations, plus requests for more details and refund-review acknowledgments. Copy the ones you need and adapt them to your process.
Review before you send
- Does the message answer what this customer asked?
- Are the name, product, dates, and links correct?
- Does it promise a refund, fix, or deadline you have not confirmed?
- Are there leftover placeholders or irrelevant paragraphs?
- Is the next step clear?
Review saved responses when your process changes. A quick shortcut should not make it easier to repeat an outdated policy. Keep policy-sensitive wording separate from everyday greetings so it is easier to find and update.
Use the response in LazyBoard
Create a snippet with your edited text and assign a shortcut you do not normally type. Add fill-in fields for details that change, then test the final message in a supported text field. See the Chrome extension or Mac setup guide to get started.
Expansion inserts your saved text; you still choose when to send it. Use that moment to check the context and make the reply sound like you.