Write the Sorry Email Before You Need It: A UK Complaint Desk for Launch Week

Launch day has a choreography. The staging link is checked, the analytics dashboard is open, the first sign-ups trickle in, and someone says the word 'traction' without irony. Then the inbox moves.

The first unhappy customer is not a launch failure. It is the first piece of product feedback with a deadline attached. In the UK, that deadline is shaped by consumer law, by card-scheme rules, and by how quickly a bad experience turns into a public review. The founder who has already written the awkward email is the one who gets to respond like a company rather than a person refreshing their phone.

The first hour: triage, not therapy

Not every complaint is the same animal. Sort them into three buckets before you start writing paragraphs.

• Broken promise: the thing did not work, did not arrive, or did not do what the checkout page said. This is the urgent one.
• Unmet expectation: the customer assumed a feature, a format, or a level of support that you did not intend to offer. This is usually a copy problem wearing a support ticket.
• Payment dispute: a duplicate charge, a failed refund, or a chargeback notification from your payment provider. This has its own clock and its own evidence pack.

Use a shared inbox, not your personal email. Give every thread one owner. If you are a team of one, that owner is still you, but the thread should be findable by someone else at 11pm.

What UK customers are actually entitled to

You do not need to be a lawyer to run a complaint desk, but you do need to avoid inventing policy on the fly. The Consumer Rights Act 2015 sets the baseline for goods, services and digital content: satisfactory quality, fit for purpose, and as described. Services must be carried out with reasonable care and skill. If you sell to consumers online, the Consumer Contracts Regulations 2013 generally give a 14-day cancellation right for distance sales, with exceptions such as bespoke items, sealed hygiene products, and certain digital content once download has started with the customer's acknowledgement.

That is the shape of the law, not the whole of it. Your terms should say what happens in plain English, and your complaint reply should point to the relevant policy rather than paraphrase legislation at a frustrated customer. If a refund is owed, process it without theatre. If you are offering a goodwill gesture instead, call it goodwill and cap it. 'As a gesture' is fine; 'as per our policy' is the sound of a one-star review being drafted.

The tone: British, brief and non-defensive

Most bad complaint emails are not rude. They are defensive. They explain the roadmap, mention the server issue, and ask the customer to sympathise with a founder who has not slept. The customer does not owe you sympathy. They owe you a clear answer.

A useful structure is three lines: acknowledge, own, next step. 'I'm sorry, that's not the experience we intended. I've refunded the order and it should land in three to five working days. I'm also fixing the checkout copy that made it look like next-day delivery was included.'

Avoid 'unfortunately', 'we apologise for any inconvenience caused', and 'as per'. Avoid copying the customer's angry tone back at them. Keep one thread, no CC chains, and never argue the detail in public. If the complaint is on social media, acknowledge once, move it to email, and resist the urge to quote-tweet your own terms and conditions.

Response windows that do not become review windows

During launch week, aim to acknowledge within two working hours. A substantive reply should go out within one working day. If you cannot resolve it that fast, give a timeline: 'I'm investigating with our payment provider and will update you by Thursday at noon.' A missed self-imposed deadline is worse than a longer honest one.

If you approve a refund, say when it will land. Card refunds commonly take three to five working days, and can take longer depending on the bank. Do not say 'immediately' unless you control the rails, and you do not.

The chargeback notification

A chargeback is a process, not a verdict. It arrives with a deadline set by the card schemes and your payment provider, and it usually asks for evidence: the order record, the delivery or access log, the customer's acceptance of your terms, and any communication between you. Keep those artefacts in one folder per order. If you use Stripe, Shopify or a similar platform, read their chargeback guidance rather than guessing at the window.

Respond with facts, not frustration. If the customer genuinely did not receive what they paid for, refund and close the loop. If the dispute is a misunderstanding, supply the evidence and let the process run.

The escalation path

Write down who handles what before launch day: who replies to press, who handles legal threats, who owns the public social reply, and who has the payment provider login. Even if every name is the same person, the list stops you from improvising at the worst moment. For public complaints, use a 24-hour rule: acknowledge, move the conversation to a private channel, and do not relitigate the issue in the replies.

The 48-hour debrief

Two days after launch, read every complaint in one sitting and tag them by bucket. Count how many were caused by copy, how many by a missing feature, and how many by a payment edge case. Fix one copy line. Add one FAQ entry. Update the onboarding email. The first angry message is cheap research. The public one-star review is expensive.

Write the sorry email before you need it. Keep the templates in a shared drive, test them on a colleague, and accept that the first unhappy customer is not a crack in the launch. They are the first person to use the product hard enough to find the edge. The reply you send in the next two hours decides whether they tell you about it or tell everyone else.