What not to do in customer service?
Short answerIn a service business, the damaging habits are promising exact arrival times you cannot keep, going silent after a problem, arguing about who is at fault, and making the customer repeat themselves. Each one is avoidable with a note on the record and a quick message.
The explanation
Most complaints in trades are about communication, not skill. A tech who is late and says nothing makes a bigger mess than a tech who is late and sends a message. Promise a window you can hit, not a time you hope to hit.
Do not argue about blame on the first call. Customers want to hear that you understand what happened and what comes next. Fix the facts later, when emotions have settled. Do not blame a crew member or a supplier in front of the customer either.
Make the customer's history easy to find. If a person calls the second time and has to repeat their story, you have lost trust. A short note on the record after every contact is the simplest fix. Also avoid vague promises like soon, and give a day instead.
What to watch for
- Quoting a time when you mean a window.
- Letting a problem sit for a week without a word.
How Apex does it
Built, rolling out
Built. A real server path exists; only setup steps remain before customers can use it. Status as of 2026-10-07; the badge shows the least-built feature involved.
Apex keeps notes and activity history on each customer, and works toward an on-my-way text with an ETA and arrival windows. Notes and windows are built, and texts need a connected provider first.
- LD13Notes and activity history per customer(Built)
- CM06On-my-way text with ETA(Built, rolling out)
- BK06Arrival windows(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.