The work that isn't software.

Give every conversation an owner

This single change fixes more than any tool. A shared mailbox fails in exactly one way: everybody can see a message and nobody is responsible for it, so a customer waits four days and nobody was being careless. One name against every conversation, always, even if that name changes three times.

Separate 'waiting on us' from 'waiting on them'

A single open status hides the most important distinction in support. Three states — waiting on the customer, waiting on us, waiting on a colleague — turn an undifferentiated queue into a list you can act on, and make the question "how many customers are waiting on Finance?" answerable.

Write down what you promised

The commitments made in replies are the least tracked and most damaging thing in customer service. "I'll come back to you Thursday" is a real obligation and it is currently stored in one person's memory. Writing them down costs ten seconds and prevents the specific failure that loses customers.

• Capture the promise when you make it, not later
• Give it an owner and a time, not a day
• Show it to the customer — this is the uncomfortable part that works
• Treat a missed promise as an incident, not an oversight

Answer from one place

Two agents giving two answers about what is included is how trust erodes quietly. Pick the twenty questions you get most, write one verified answer each, and make everyone use them. This is a fortnight of work and it outperforms most software purchases.

Count what people ask about

Nobody in a small company knows their actual support demand — they know the last thing that annoyed them. Counting what customers contact you about, by subject, almost always produces a surprise, and it is usually a confusing process rather than a broken feature.

Close cases the customer agrees are closed

Resolution rate measured by the team is a measure of when the team stopped working. Asking one question — did we solve it — and treating "partly" as a no is the correction. Expect the number to drop initially; that is the point.

When several customers report the same thing, stop

Three similar reports in an hour is a pattern, and the instinct to answer them individually is expensive and produces three slightly different explanations. Group them, say something once, and tell everyone when it is fixed — including the ones who never wrote in.

Look at repeat contact, not satisfaction

People rate an interaction positively and still have to write again. Repeat contact about the same thing is the honest measure of whether support worked, and it points at causes you can actually fix: an incomplete answer, a premature close, an unclear article, an unfixed root cause.