New

Chatboq Ticketing System launching soon — Join the waitlist for early access

Chatboq

12 Live Chat Scripts for a Late Delivery Complaint

A chat conversation acknowledging a late delivery and offering a remedy

Glossary & How-Tos

Kevin Tan

October 5, 2026

Reading Time

6 minutes

Acknowledge the specific failure and its impact before explaining anything, since explanation offered first reads as excuse.

1. The straightforward acknowledgement

Your order should have been with you on [date] and it wasn't. That's our failure and I'm sorry. Let me tell you where it actually is and what I can do about it.

Accountability before explanation is what distinguishes this from the enquiry response.

2. Asking what it cost them

Before I look at options — did the delay cause you a problem beyond the wait? It changes what I can do.

This single question identifies the difference between an inconvenience and a genuine loss, which should change the remedy.

3. When they are clearly angry

You're right to be annoyed. I'm not going to explain it away. Here's where it is and here's what I'll do.

Short, plain and immediately practical. Length reads as defensiveness at this point.

When they went public first

A complaint raised publicly should be acknowledged there briefly and moved to a private channel for the detail.

Attempting to resolve it entirely in public rarely works and attempting to ignore it works less well.

Summarize this article with AI

ChatGPT

Perplexity

Claude

Table of content

Where the Order Is Still Coming

A late but arriving order needs a credible new commitment and something to acknowledge the failed one.

4. New date with confidence

It's [current status] and will be with you [date]. I've refunded the delivery charge of [amount] since you paid for a service you didn't get.

Refunding the delivery charge is the minimum proportionate response and requires no negotiation.

5. New date without confidence

I'm not going to give you another date I'm not sure of. It's currently [status]. I'll check tomorrow and message you either way, and if it hasn't moved I'll send a replacement.

A second broken promise damages trust more than the original delay, which makes honesty about uncertainty the better option.

6. Offering to cancel instead

If it's too late to be useful, I can cancel and refund in full rather than sending something you no longer want.

Offering this proactively is what prevents the refund request becoming a second frustrating conversation.

Where the Occasion Was Missed

A delivery that missed the date it was needed for is a different failure, and standard remedies are inadequate.

7. Acknowledging what it was for

It was for [occasion] and it didn't arrive in time, which is the whole point of ordering it. I'm sorry — that's a genuine failure on our side.

Naming what the order was for demonstrates the situation was understood rather than processed.

8. Asking rather than offering

I can refund in full, refund and let you keep it, or send something as an apology. What would actually help at this point?

Asking is more effective than offering, since the customer knows what would help and being asked is itself part of the recovery.

9. Where a replacement can still work

If [later date] would still be useful, I can send a replacement on next day at no cost. Otherwise a full refund and we'll leave it there.

Absorbing expedited cost on a business-caused failure is standard and should be stated rather than negotiated.

Repeated Failures

A customer let down more than once needs a different response, since the standard remedy has already been shown not to prevent recurrence.

10. Acknowledging the pattern

This is the [second or third] time. Individually I'd apologise and refund the delivery, but that's clearly not the issue. I'm escalating this so someone looks at why it keeps happening to your orders.

Naming the pattern before the customer does is what separates a genuine response from a scripted one.

11. Investigating rather than compensating

Repeated failures to one address frequently have a specific cause such as a routing or address issue that compensation does not address.

Committing to investigate, with a date to come back, is more valuable to the customer than a larger gesture.

Escalating repeated failures

These should reach a person regardless of the individual order value, since the relationship rather than the transaction is now at stake.

They are also a useful operational signal, since repeated failures to one customer frequently indicate a wider problem.

Compensation Decisions

Compensation should be proportionate to consequence rather than to order value, and consistent across customers.

12. The proportionate gesture

I've refunded the delivery charge and added [amount] as a credit. It doesn't undo the inconvenience but it's what I can do directly.

Being honest that a gesture does not undo the problem lands better than presenting it as making things right.

Documented thresholds

What is offered should come from a documented policy rather than individual judgement, since customers compare outcomes and perceive unfairness quickly.

Delivery complaints are discussed publicly more than most, which makes consistency here unusually visible.

Costs the customer incurred

Where a customer has incurred actual costs because of the delay, the remedy is a separate question requiring judgement and a person.

An automated gesture in this situation will understate it and produce a further complaint.

What Not to Say

Several standard responses reliably escalate a delivery complaint rather than resolving it.

Blaming the carrier

The customer bought from you and chose your delivery service, which makes carrier blame read as avoiding responsibility.

Explaining the cause is fine, provided accountability stays where the customer placed it.

Citing the terms

Pointing out that delivery estimates are not guarantees is factually correct and never improves a complaint conversation.

It also invites the customer to escalate to someone who will not lead with the terms.

Asking them to wait longer

Requesting further patience without a date after which you will act leaves the customer with nothing and reads as a delay tactic.

Every waiting request should carry a commitment attached.

Excessive apology

Repeated apology without a remedy reads as discomfort rather than accountability and lengthens a message that should be practical.

Once, followed immediately by what is being done, is the effective structure.

Handling These in Chatboq

Chatboq detects complaint language, shifts register and escalates the cases that should not receive an automated remedy.

Recognising a complaint

Complaint and frustration language triggers a shorter, plainer register rather than the informational response used for delay enquiries.

This distinction is what prevents the cheerful tracking update appearing when a customer is telling you the service failed.

Remedies from policy

Delivery charge refunds and gesture thresholds are configured from the same rules agents apply, so outcomes are consistent regardless of route.

Above the thresholds, and for repeated failures or incurred costs, the conversation escalates before any remedy is offered.

Learning from the pattern

Complaints grouped by carrier, route and destination frequently identify a systemic cause rather than a series of individual failures.

Track complaint volume, remedy cost and whether complaining customers order again, since the last is what the recovery is actually for.

Following through afterwards

Confirming when the promised remedy actually happened is what completes the recovery, and it is frequently omitted.

A customer who was promised a refund and never told it went through remains dissatisfied despite being compensated.

Frequently AskedQuestions

By detecting complaint language and shifting register, applying remedy thresholds from your policy, and escalating repeated failures and incurred costs before offering anything.

You can explain the cause, but accountability should stay with you, since the customer bought from you and chose your delivery service.

Name the pattern before the customer does, escalate regardless of order value, and commit to investigating the cause rather than only compensating again.

Acknowledge what it was for, then ask what would actually help rather than offering a standard remedy, since the customer knows and being asked matters.

Refunding the delivery charge is the minimum proportionate response, with anything further based on the actual consequence rather than the order value.

By acknowledging the specific failure and accepting accountability before explaining anything, since explanation offered first reads as an excuse.