A customer asks for an update in chat. Another sends a similar question by email. You know what to say, but the useful wording is in yesterday’s ticket, a document, or a different tool’s saved replies.
Canned responses are reusable starting points, not automatic answers. These twelve original examples cover six everyday situations: a short chat reply and a fuller email reply for each. Copy the text you need, then adapt it to the actual conversation.
Before you copy a reply
The words in square brackets are manual editing prompts, not fields that the extension fills automatically. Replace every prompt in the destination application and read the entire message before sending. Add an email subject and signature appropriate to your team.
Use only wording your organization allows. Confirm the facts, the next action, and any commitment you make. Never say a refund, fix, escalation, or investigation happened unless it did. Do not add an arbitrary resolution deadline to make a reply sound reassuring.
1. Acknowledge a request
Use this when opening a conversation; it does not claim the problem is already fixed.
Live chat
Thanks for explaining. Let’s look at [issue] together. What happens when you try [relevant step]?
Hello, thank you for contacting us about [issue]. To understand what is happening, could you describe the result of [relevant step]? That will help us choose the appropriate next step rather than ask you to repeat the whole story.
2. Ask for missing details
Ask for observable behavior, not passwords, payment information, or a complete customer record.
Live chat
Which step produces the error, and what does it say? Please remove personal or confidential details before sharing the message.
Hello, could you tell us which step triggers [issue] and share the error wording, with personal or confidential information removed? Please also describe what you expected to happen. You do not need to send a password or a copy of your full account information.
3. Explain that an investigation is underway
Use this only while you are actually investigating. A holding message must not imply a confirmed diagnosis or a guaranteed fix.
Live chat
I’m checking [specific issue] now. I’ll share the findings here when I have a confirmed update.
Hello, I am reviewing [specific issue] to understand the next step. I do not yet have a confirmed outcome. I will share a further update once there is verified information.
If you have agreed a next-update time with the customer, add it. Do not invent one; an update time is not a resolution promise.
4. Provide a progress update
Check the source of truth first. Replace both prompts with confirmed information, not assumptions.
Live chat
Here is the latest confirmed update: [verified status]. The next step is [confirmed next action].
Hello, here is the current update on [issue]: [verified status]. The next step is [confirmed next action]. This update describes the current position, not a completed resolution. Please let us know if the behavior you are seeing has changed.
5. Give an approved troubleshooting instruction
This is a fictional browser-app example. Use it only if your team’s guide approves the step and it is safe for this customer; never risk losing unsaved work.
Live chat
Keep this chat open in its original tab. If your work is saved and it is safe to open another tab, open [affected page] in a new tab, refresh only that new tab once, and try [approved action] again. What happens this time?
Hello, the next step in our troubleshooting guide is to refresh [affected page] once, after saving any work, and retry [approved action]. Please do this only if it is safe to reload. Tell us whether the behavior changes, and stop if you see a new error.
Do not use the wording as a substitute for diagnosis or an up-to-date support procedure.
6. Check whether the issue is resolved
Ask the customer to confirm the outcome instead of declaring success on their behalf.
Live chat
Does [action] now work as expected? If not, tell me what is still happening so we can choose the next step.
Hello, I am following up on [issue]. Could you confirm whether [action] now works as expected? If the problem remains, please describe the current behavior so we can continue from there without starting the conversation over.
Keep the replies beside your work
Saving useful wording is different from storing a customer’s case. Start with generic text and leave customer-specific details in the approved ticket or email system.
- Install Note-it Aside in desktop Chrome and open its side panel.
- Create a folder for support replies. Save the chat and email versions of one situation as separate notes, with titles that identify the situation and channel, such as “Investigation — chat” and “Investigation — email.” Keep editing reminders separate from the reply text.
- In a fictional support chat about a demo page that will not load, copy the “Investigation — chat” note from the panel. Paste it into the chat draft, replace the prompt with “the demo page,” and send only if the investigation is really underway.
- Switch to an email draft in Outlook on the web. The saved library is still available in the browser’s side panel; copy the “Investigation — email” note, adapt it to that conversation, and add the subject and signature there.
- Keep both saved notes generic. Review them when your team’s policy changes; do not accumulate customer histories in the folder.
Worked example — fictional demo page
Saved chat note: I’m checking [specific issue] now. I’ll share the findings here when I have a confirmed update.
Chat draft after manual editing: I’m checking the demo page now. I’ll share the findings here when I have a confirmed update.
Saved email note: Hello, I am reviewing [specific issue] to understand the next step. I do not yet have a confirmed outcome. I will share a further update once there is verified information.
Email draft after manual editing: Hello, I am reviewing the demo page to understand the next step. I do not yet have a confirmed outcome. I will share a further update once there is verified information.
This is a copy-and-edit workflow, not a connection to a customer’s helpdesk. Note-it Aside supplies saved text; you choose the correct reply, edit the facts, and send it. It does not automatically retrieve CRM records, transfer tickets, or update customer histories.
Try one example during your next repeated-writing task, rather than importing a large library you have not reviewed.
Try Note-it Aside free in Chrome and save your first reply
When your tool’s native templates are the better choice
Quiq already provides personal and company-wide snippets. Outlook provides full email templates and short reusable snippets. If your team’s native library already covers the work, use it—especially for centrally managed messages or integrated actions.
Note-it Aside is an optional browser-side library for reusable wording that you also need beside other applications. It does not synchronize those applications’ template catalogues or replace team approval, CRM automation, or access controls. Check your employer’s extension policy before installing it.
Build a small, trustworthy library
Keep generic structures in your notes. Customer identifiers, contact details, payment or health information, and authoritative case history belong in approved business systems. Remove outdated wording and check any policy link before reuse.
For more starting points, browse the customer-support templates, account-access reply, and resolution follow-up. For organization tips, read reply snippets beside the ticket and the customer-support workflow. The Salesforce workflow guide explains where native CRM tools and browser-side notes differ.