How to deal with unhappy clients: tips?
Short answerReply to an unhappy client within hours, stay calm, ask what outcome they want, and agree on one concrete fix. Keep the conversation in writing where possible and record the cause. Most unhappy clients mainly want to know that someone owns the problem.
The explanation
Speed is the first tip. A same day reply, even just saying you are looking into it, lowers the temperature. Silence is what turns a small problem into a public review.
Ask what a good result looks like. Some clients want a redo, some want a credit, some want an apology and a promise. Guessing wastes money. Once you know, you can say yes, say partly yes, or explain what is fair.
Keep it factual. Do not argue about tone, and do not blame a crew member by name. Write down the date, the job, what went wrong and what you offered. If the client later posts a review, a calm public reply that states the facts and the fix reads well to future buyers. Finally, change something. If three complaints share a cause, such as late arrival, fix the cause in scheduling rather than apologizing three times.
What to watch for
- Matching an angry tone with an angry reply.
- Giving a refund with no written closure.
- Fixing the client and not the process.
How Apex does it
Rolling out
The screen and the rules are built and tested. Saving real customer data is not connected yet. Status as of 2026-10-07; the badge shows the least-built feature involved.
Apex is designed to keep a history of notes on each customer and set follow-up call tasks, and to show reviews in one place. The reputation dashboard is rolling out, per its badge.
- LD13Notes and activity history per customer(Built)
- MK03Reputation dashboard (all reviews in one place)(Rolling out)
- CM21Follow-up call tasks(Built)
Apex Flow Scheduler is in early access. See how we label status.
Where this question comes from: owners type it, or a close variant, into search boxes. It was returned by public search suggestions (Google, Bing or DuckDuckGo) when we collected them on 2026-10-06. We do not have search volumes.