Name the failure in plain language
Say what did not happen as promised: a delivery was late, a booking failed, information was wrong, or support did not respond. Avoid passive phrases such as mistakes were made.
If personal data, safety, finance, or regulated service is involved, follow the required incident and notification process before improvising a message.
Pair ownership with a remedy
Explain what has already been corrected and what the customer can choose next. A refund, replacement, credit, correction, or named support contact should be specific and proportionate.
Do not make the remedy conditional on removing a review, ending a complaint, or praising the response. That turns repair into leverage.
- What failed and when.
- What has been fixed.
- A clear remedy and contact route.
Use the customer's preferred support channel
Ordinary email, account messaging, or support tools should come first. A single announced request is only for a lawful case where the customer cannot otherwise be reached and the message contains no sensitive account data.
If they have opted out of contact, respect that choice and use only communications required or permitted by applicable law.