Apology for delayed response templates
When a ticket sat for days, the apology should take one sentence and the answer should take the rest. This template opens with a plain sorry and a short reason if there is one, then goes straight to the help the customer was waiting for. It avoids the long preamble that makes a late reply feel even later.
;cs-slow-reply;cs-slow-reply in any app.Variations
The same message for a different channel or tone. Copy the one that fits.
For a chat that's been waiting in the queue for more than a few minutes.
For the reply that goes out to everyone after a launch, outage or holiday pile-up.
When to use it
- A ticket has gone past your usual response time.
- The customer has followed up asking if anyone's there.
- You're clearing a backlog after a launch, a holiday or an outage.
What to avoid
- Don't send the apology on its own. Always pair it with an actual answer or a clear next step.
- Don't over-explain the reason. "We've had a busy week" is fine; your staffing problems aren't the customer's.
- Don't use it for a reply that's on time. Apologising by reflex makes every reply sound late.
The fields in this template
Retext fills these in when the snippet expands. In plain text they become [brackets] to replace by hand.
- Customer name
{fill:Customer name} - Their first name.
- Short reason
{fill:Short reason} - One optional line, e.g. "We've had an unusually busy week after the launch." Leave it blank if there's nothing useful to say.
- Cursor
{cursor} - Where your cursor lands after the snippet expands, so you can start typing the personal part straight away.
- Your name
{fill:Your name} - Your first name.
Tips
- •Leave the short reason empty when there isn't a good one. "Sorry for the slow reply" stands on its own.
- •With autocomplete (beta) on, type ;cs-sl and pause, and Retext offers the rest of the trigger, so it's quick to add at the top of any reply.
- •The chat version is a good first message to send while you read the history.
Works in Zendesk, Intercom, Help Scout, Front and every other app
Retext types the snippet wherever your cursor is. To use a different version in one app, give it the same trigger and limit it to that app with per-app snippets. They go by app, not website, so every tab in your browser counts as one app.
Keep the backlog variant in the team pack ready for launch week. When volume spikes, everyone uses the same honest wording instead of improvising.
See Retext for TeamsQuestions
How do you apologise for a late response to a customer?
One line of apology, an optional short reason, then the answer. Customers care far more about getting help than about a long explanation of why it was late.
Is "sorry for the delay" unprofessional?
Not at all, as long as it's followed by something useful. What reads as unprofessional is an apology with no answer attached.
Related templates
Waiting on your reply
;cs-nudgeCustomer support
Hi [Customer name], Just checking in on this. To keep going, I still need [What you need]. If it's already sorted, no ne…
Service outage update
;cs-outageCustomer support
Hi [Customer name], Thanks for reporting this. It's not you: we're having an issue with [Affected service] since [Start…
Apology email to a customer
;cs-apologyCustomer support
Hi [Customer name], I'm sorry. [What went wrong], and that's on us. Here's what I've done so far: [What you fixed]. So t…
Type ;cs-slow-reply, get the whole reply
Retext expands your snippets in every Mac app and fills in names, dates and order numbers for you.
Free to start. No account required on the Mac.