How Good Is Your Customer Service Email?
Most businesses judge their support inbox by whether anyone is complaining. That measures the loudest customers, not the service. Eight questions on speed, resolution, backlog, after-hours cover, tone and tracking give a score you can act on.
Answer for the inbox customers write to when something has gone wrong, not the sales inbox. Be honest about weekends.
Customer Service Email Scorecard
Answer for the inbox customers use when something has gone wrong.
A self-assessment to structure an internal review. It is not an audit. Nothing entered is recorded or transmitted.
What the Score Measures
Six things customers experience directly, plus two that decide whether the first six stay good. Each is scored on what actually happens, not on what the policy says.
Speed and resolution are scored separately
A fast first reply that says nothing is not service. A complete answer that arrives three days later is not either. The scorecard asks how quickly the first reply arrives and, separately, how often that first reply actually resolves the matter. High scores on both is the target.
Backlog age is the hidden number
A team can answer new mail quickly while a set of older messages ages unnoticed. The oldest open message is a better measure of service than the average, because it is the customer most likely to be writing a review right now.
Tracking is what keeps the score from sliding
Without recorded outcomes, nobody knows whether a reply worked, whether the same problem keeps recurring, or whether service is better or worse than last quarter. The last two questions score whether you could answer those questions today.
How the Score Works
Eight questions, each with four options scored from zero to three. The total is shown as a fraction of the maximum and placed in one of three bands.
Speed
First-response time during business hours, and what happens to a message that arrives after hours or on a weekend.
Resolution
How often the first reply resolves the matter, and how complaints are handled when they arrive.
Backlog and ownership
The age of the oldest open message, and whether every message has a named owner.
Consistency and tracking
Whether replies sound the same whoever writes them, and whether outcomes are recorded and reviewed.
The Patterns Behind a Low Score
Four situations that produce most low scores, and what changes each one.
Service stops at 5pm and restarts Monday
A customer who writes on Friday evening about a problem waits until at least Monday morning for any sign they were heard. That is the longest gap in the week and it lands on the customers who are already unhappy. An automatic acknowledgement with a real expected time, and triage that sorts the weekend mail before Monday, closes most of the gap without rostering weekend staff.
- Acknowledge after-hours mail automatically, with an honest time
- Sort and prioritise overnight so urgent items are first on Monday
- Give an alternative for genuine emergencies
- Measure weekend response separately from weekday
The first reply asks a question the customer already answered
A large share of second and third emails on a support thread exist because the first reply did not read the whole message or did not have the customer history in front of it. First-reply resolution improves when the reply is drafted with the order, the account and the previous thread visible, and when the reviewer checks for the question before sending.
- Draft with the customer record and order history attached
- Answer every question in the message, not only the first
- State the next step and who owns it in every reply
- Track how many threads close after one reply
Tone depends on who picked it up
One person writes warmly, another writes in two words, and a third apologises four times. Customers who write twice get two different businesses. A short voice standard, drafted replies that follow it, and a reviewer who checks tone as well as facts make the service feel like one team.
- Write the voice standard from your own best replies
- Draft replies to the standard so the baseline is consistent
- Reviewers check tone, not just accuracy
- Review a sample of sent replies monthly for drift
Complaints are handled the same as questions
A complaint that receives a template acknowledgement, sits in the general queue and is answered by whoever is free is a complaint that escalates. Complaints need to be recognised on arrival, routed to a named person, answered within a shorter target, and recorded with the outcome so the same cause is fixed rather than repeated.
- Detect complaint language on arrival and route it separately
- Never send an automatic reply to a complaint
- Shorter target and a named owner for every complaint
- Record the cause and the outcome, and review causes monthly
Next Steps
Shared Inbox SLA Calculator
Check whether the support inbox is staffed to meet the response target you want to score well on.
Check the staffing →AI Email for Customer Service
How triage, drafting and after-hours acknowledgement work in a support inbox.
See how it works →Email Triage Rules Checklist
Write the categories, owners and complaint routing that raise the backlog and ownership scores.
Write the rules →Frequently Asked Questions
It depends on what customers were told and what they are waiting on. If your website or your automatic acknowledgement promises a time, that is the target and it needs to be met. Where nothing is promised, a reply within business hours the same day is a reasonable standard for a support inbox, with a shorter path for anything urgent or anything that reads as a complaint. Measure it from the customer's message, not from when someone opened it.
Because they fail in different ways and are fixed by different things. Slow first replies are usually a staffing, coverage or triage problem. Low first-reply resolution is usually a context problem: the person replying did not have the order, the history or the full message in front of them, or did not answer every question. A fast inbox with low resolution generates a long thread for every customer. Scoring both shows which one you have.
Sort the inbox or the helpdesk queue by date, oldest first, and look at the top. If the answer is embarrassing, that is the finding. Then look at why it is still open: nobody owned it, it was waiting on someone internal, or it was misfiled. Most teams that start reporting the oldest open message weekly find it falls quickly, because a visible number gets attention that an average never does.
An acknowledgement is useful when it tells the customer something true: that the message arrived, roughly when to expect a reply, and how to reach someone if it is urgent. It is harmful when it promises a time you do not meet, or when it goes to a complaint, a legal matter or a distressed customer as if it were a routine question. Send acknowledgements after hours and to routine categories, and exclude complaints and sensitive matters from automatic replies altogether.
At minimum: the category, who owned it, when the first reply went, whether it resolved on the first reply, and the outcome. For complaints, add the cause. That is enough to report first-response time, resolution rate, backlog age and recurring causes each month. If your replies about faults, refunds or remedies need to line up with the Australian Consumer Law, recording what was offered and why also gives you a record to stand on later.
No. The scorecard runs in your browser, nothing is sent anywhere, and there is no email gate on the result. Screenshot it for a team discussion if that helps. The questions ask only about your process, so no customer details or email content are requested at any point.
Sources and further reading
- Consumer guarantees under the Australian Consumer Law (Australian Competition and Consumer Commission)
Know Which Question Cost You the Points?
Tell us your lowest-scoring answers and the volume your support inbox handles. We will tell you whether the fix is a process change, a staffing change or triage and drafting, and what each would cost.