Acknowledge a new request
Suggested shortcut/receivedUse this when a customer first contacts you. Set a realistic time for the next update.
Copy-ready customer service response templates and examples — from the first acknowledgment to the final resolution.
Edit any message below before copying. Replace the details in [square brackets]; they are plain text, not automatic fields. Edits stay on this page and are not saved when you leave.
/receivedUse this when a customer first contacts you. Set a realistic time for the next update.
/detailsRequest only the information needed to understand the issue.
/progressUse this before a promised update is due, even if the issue is still open.
/workaroundOffer a temporary option and state its limits clearly.
/resolvedUse after verifying the fix; give the customer a clear next step.
/refundreviewAcknowledge the request without promising an outcome before reviewing it.
/complaintRecognize the specific problem and set a realistic next update. Do not promise a resolution before checking.
/escalationUse after the specialist or team has accepted the handoff. Say who will follow up and when.
/feedbackName what they shared and what happens next.
/featurerequestAcknowledge the request honestly without committing to a roadmap.
/bugloggedConfirm the report is recorded and set expectations.
/orderconfirmGive the key order facts in one place.
/shippingdelayExplain the delay and the new estimate without guessing.
/trackingGive the link and what to do if it doesn’t update.
/refundapprovedUse only after the refund is processed.
/refunddeclinedExplain the reason and any alternative you can offer.
/loginhelpGive safe steps; never ask for a password.
/helparticleSay which part of the article answers the question.
/cancelconfirmState what ends and when.
/checkinClose the loop when a customer hasn’t answered.
/closeticketConfirm the outcome and how to reopen.
/reviewrequestSend only after a good outcome, and make it optional.
/calmreplyStay specific and calm; focus on the next step.
/afterhoursSet expectations for the next response.
In LazyBoard for desktop or Chrome, create a snippet called “Support acknowledgment” with the shortcut ;supportack. Paste the snippet below into its content field. When you insert it, fill in the four fields.
Unlike the square-bracket placeholders above, these double-brace fields prompt you for values in LazyBoard. This example uses desktop and Chrome syntax; see the mobile variables guide for your phone.
Review the inserted reply before sending. Use an update time you can meet. Follow the Chrome setup guide or desktop setup guide to try your first snippet.
Updated October 25, 2026 (16 examples added). Examples prepared with AI assistance and checked against LazyBoard’s template renderer.
Keep each response specific to the customer’s issue. Replace every bracketed detail, remove anything irrelevant, and only promise response times your team can meet.
Want to fill in names and other details each time you expand a snippet? See the LazyBoard variables guide.