Saved replies your support team can use every day

Saved replies cut repeat typing without forcing customers to read a script. MakesYouLocal found order tracking was the most common question in its analysis of 787,000 ecommerce support interactions from 2024. Start with daily questions, then personalize before sending.

A saved reply is a reusable answer that an agent checks and inserts into a conversation. It gives your team a starting point, not a message that should go out untouched.

Speed matters because the customer may still be waiting on the page. CX Dive reported in April 2025 that about two in five surveyed customers expected a response within five minutes when contacting a brand about a problem.

Compared with writing from scratch, a saved reply helps your team respond faster and include the same policy details each time. Saved replies are best for stable facts and repeat processes, such as opening hours, shipping windows and return instructions. They aren’t a substitute for judgment.

How should you write saved replies that don’t sound scripted?

Write each saved reply as a short answer with a clear next step and a place for a customer-specific detail.

Customers notice when a message ignores what they said. A Gradient Labs survey of 1,500 US adults conducted in April 2025 found that 53% thought scripted responses made support worse. The problem isn’t reusable text itself. It’s sending that text without checking whether it fits.

Build each reply from four parts:

• Use the customer’s name when you know it.
• Give the direct answer in the first sentence.
• Add a detail from the order, product or conversation.
• Finish with the next action and who will take it.

Delete any sentence that doesn’t apply. If the customer already supplied an order number, don’t ask for it again. CX Dive reported in June 2026 that 60% of respondents in a survey of 1,001 US consumers would abandon an automated support experience after repeating themselves once.

Use this reply when you need a missing fact before you can answer.

Template: Hi {name}, I can help with {issue}. To make sure I give you the right answer, could you send {missing detail}? Once I have that, I can {next action}.

Use this reply when another person needs to take over. Include what the customer has already told you.

Template: Hi {name}, this needs a closer look from {team or person}. I’ve passed along {details already provided}, so you won’t need to repeat them. You can expect a reply by {time or date}.

If live chat is your main channel, this larger set of canned responses gives you more starting points for routine conversations.

Which saved replies cover shipping and order status?

Use separate saved replies for orders awaiting dispatch, orders in transit and delayed deliveries.

Don’t answer every shipping question with a tracking link. First identify what the customer needs to know: whether the order left your business, where the carrier last scanned it or what you’ll do about a delay.

Use this after an order has been received but hasn’t shipped.

Template: Hi {name}, your order {order number} is confirmed and is due to ship by {date}. We’ll send the tracking link to {email or phone} as soon as the carrier collects it.

Use this when the parcel is moving normally.

Template: Hi {name}, order {order number} shipped on {date}. The carrier’s latest update says {tracking status}. You can follow it here: {tracking link}. The current delivery estimate is {date or delivery window}.

Use this when a shipment has missed its expected date. State what you’ll do instead of telling the customer to keep waiting.

Template: Hi {name}, your order {order number} hasn’t arrived within the expected window. I’m sorry about the delay. I’ve {contacted the carrier or opened an investigation}, and I’ll update you by {time or date}. If it can’t be located, we’ll {replacement or refund action}.

Only promise a delivery date if your order or carrier data supports it. If tracking questions take up much of the day, a self-service order-status setup can keep simple lookups out of the agent queue while leaving exceptions with your team.

What should you say about returns and refunds?

Tell the customer whether the item qualifies, what they need to do next and when the refund or exchange will happen.

A vague returns answer creates another conversation. A harsh answer can lose the next order. In a 2025 National Retail Federation and Happy Returns survey, 71% of US online returners said a poor returns experience made them less likely to shop with that retailer again.

Use this when the return meets your policy.

Template: Hi {name}, you can return {item} because it is within our {return period} policy. Please {return steps}. Once {condition for processing}, we’ll send the refund to {payment method}. It usually appears within {refund timing}.

Use this when an exchange is available. Confirm the replacement before asking the customer to send anything back.

Template: Hi {name}, we can exchange {original item} for {replacement item}. I’ve confirmed that {replacement detail} is available. Please {return steps}, and we’ll send the replacement {dispatch timing or condition}.

Use this when the request falls outside the standard policy, but check whether a manager can make an exception first.

Template: Hi {name}, I checked your request against our return policy. We can’t accept this return because {specific reason}. The option we can offer is {repair, store credit, partial refund or escalation}. If you’d like, I can {next action}.

Don’t leave the customer guessing about when their money will return. The same 2025 US survey from the National Retail Federation and Happy Returns found that 76% of online returners were more likely to choose a return option offering an instant refund or exchange.

How can you answer pricing, opening hours and order changes?

Give the exact fact first, then tell the customer what you need from them or what happens next.

These replies look simple, which makes stale wording easy to miss. Tie the answer to a current price list, schedule or order process. If the source changes, update the saved reply at the same time.

Pricing reply

Use this when the customer asks what a product or service costs. Say what the price includes and identify any variable part.

Template: Hi {name}, {product or service} costs {price} and includes {included items}. {Tax, shipping or setup fee} is {included or added separately}. Your total for {quantity or scope} would be {total}, valid until {date if applicable}.

Opening hours reply

Use this when someone asks when your team, store or service is available.

Template: Hi {name}, we’re open {days} from {opening time} to {closing time} in {time zone}. We’re closed on {closed days or holiday}. Messages received outside those hours are answered by {expected reply time}.

For nights, weekends and holidays, keep separate away message templates so the promised reply time matches the actual schedule.

Order change reply

Use this when you can still edit the shipping address, product or quantity.

Template: Hi {name}, order {order number} hasn’t shipped, so I can change {requested detail}. Please confirm the new information: {new address, product or quantity}. I’ll send confirmation once the update is saved.

Use this when the order has passed the point where your team can change it.

Template: Hi {name}, order {order number} has already reached {packing or shipping stage}, so I can’t change {requested detail}. Your available options are {carrier request, return, replacement or new order}. I can help you with {best available next step}.

A saved reply gives you more control than an improvised answer because the approved policy is already present. The agent still needs to verify the customer’s order stage, current price or local opening hours before sending it.

How should you handle complaints and keep replies useful?

Acknowledge the problem before using a saved reply, then review the library whenever a policy or process changes.

Complaints need more than a polished apology. The customer needs to know that you understood the specific failure and what you’ll do next. Accuracy matters too. The Gradient Labs survey of 1,500 US adults found that 22% said they had lost significant money after support staff gave them incorrect information.

Use this when an item arrived damaged or a service wasn’t delivered correctly.

Template: Hi {name}, I’m sorry that {specific problem} happened with {order or service}. That’s not what you should have received. Please send {evidence or missing detail}, and I’ll arrange {replacement, repair, refund or investigation} by {time or date}.

Use this when your team previously gave the wrong information. Correct it plainly instead of defending the earlier reply.

Template: Hi {name}, the information we gave you about {topic} was incorrect. The correct answer is {accurate information}. I’m sorry for the confusion. I’ve now {corrective action}, and the next update will come by {time or date}.

Use this when the complaint needs authority or investigation beyond the current agent.

Template: Hi {name}, I understand that the main issue is {customer’s concern}. I’ve sent the conversation and {supporting details} to {manager or specialist}. They’ll review it and reply by {time or date}. You won’t need to explain the issue again.

Keep saved replies grouped by subject and give each a plain name such as “Order delayed” or “Return approved.” In LenoChat, teams can keep saved replies as macros and use tags to group conversations, making it easier to find and review messages by topic.

Review your library before predictable busy periods. MakesYouLocal’s 2024 ecommerce support data showed that the busiest week generated 2.5x as many inquiries as the quietest, while first-contact resolution fell by 13% during peaks.

Start with order-status replies because the research shows that question appears most often. Add returns, opening hours and order changes next. Save complaint replies last, and treat them as frameworks that your team rewrites around the customer’s actual problem. Fast matters, but a relevant answer is what closes the conversation.