The complaint that names the fix

1

A client complaint is a document, even when it arrives as a phone call. The useful version names the order, the failure, and the cost of the failure to the client. A sentence that only says the client is unhappy cannot be routed. A sentence that says order 441 arrived on Thursday, two days after the line needed it, and the night shift stopped for six hours can. Staff who rewrite a complaint into a feeling lose the fact that would have told operations what to change.

2

The reply has a shape that is easy to get backwards. An apology that fills the whole first paragraph delays the remedy. The client already knows something went wrong. What they cannot see is whether anyone will repair it, by when, and who owns that repair. A reply that opens with the remedy — a replacement on Monday at 10, and Mina owns the shipment — and then gives a short reason treats the client as a partner who needs a date. A reply that opens with the company's embarrassment treats the client as an audience.

3

There is a limit to speed. A promise made before the plant has confirmed the stock is a second failure. The discipline is to separate what is already true from what is still a hope. We can confirm Monday at 10 is a fact. We hope to sort this out as soon as possible is a hope, and clients have learned to hear it as a refusal to commit. Teams that keep a same-day rule for the first reply, but allow that reply to say the date will be confirmed by 4 p.m., lose fewer accounts than teams that promise a truck they do not have.