Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Audit Guides

Customer Service Audit Scorecard

A scored customer service audit: channels and help centre, standards and replies, complaints and remedies, campaign briefs, AI assistants and insight.
Auditintermediate13 min readUpdated

Scope: what this audit covers and what it does not

The question this audit answers is whether customer service gives customers correct answers and fair fixes through channels they can use, stays in step with what marketing promises, and sends what it hears to the teams that can remove the causes, and which weakness should be fixed first. It covers the support operation as customers meet it, from the channels on offer to the tagging, metrics and quality review that turn contacts into decisions.

It does not re-teach the work: the methods sit in the guides and tutorials of the service and support hub. Scoring a sample of replies is the tutorial on reviewing support conversations for quality; this scorecard asks whether that review happens. An assistant about to answer its first customer is checked with the AI customer service launch checklist.

Why customers leave is scored by the customer retention audit, which takes service as one part of the system that keeps customers. Public reviews are scored by the customer reviews and reputation audit, and replies on the brand's social profiles by the social media presence audit, with moderation left to the community management guide. Staffing levels, workforce planning and legal compliance are out of scope. Every scorecard sits in the audit library.

Before you score: access and evidence

Ask for read access to the support tool, with its tags, statuses and saved replies, and to the help centre with its search log; without them the measurement rows stay provisional. Fix an evidence window that includes at least one campaign or promotion and the contacts it caused, and keep the same window for every rescore.

Collect:

  • the written service standards for each channel, the routing rules and the tone guidelines;
  • the complaints procedure, the complaint log and the remedy table with its approval levels;
  • contact reason counts, the weekly service report and the latest quality review scorecards;
  • the briefs support received before recent campaigns, and the messages sent about a recent disruption;
  • the instructions, source content and a sample of conversations of any assistant that answers customers;
  • notes from a walk through each channel as a customer, including reaching a person and making a complaint.

Before looking at any counts, write down what the team believes customers contact it about most, and compare it with the tagged reasons. As the expectation-disconfirmation model suggests, contacts cluster where the experience falls short of what customers were led to expect.

Criteria and scoring

Rate each row missing (absent or broken), partial (present but incomplete, inconsistent or out of date) or solid (matches the "what good looks like" column). The scale is your judgement against that column, not a number. Rows marked gate decide the band on their own when they score missing, because they are the records that show what customers need and where the business fails them.

Channels and self-service

CriterionWhat good looks likeScore guidance
Channels matched to questionsEach channel offered suits the customers and the questions that arrive in it, has an owner and a standard, and is staffed whenever it is shown as openMissing: unowned channels, or chat shown open with nobody there / Partial: owned, but questions forced into the wrong channel / Solid: chosen, owned, staffed
Help articles found at the point of needHelp articles are titled the way customers phrase the question, open to search engines, linked from the pages and messages where the question arises, and kept current by an ownerMissing: no help content, or hidden behind a login / Partial: stale or unlinked / Solid: owned, dated, linked
A person within reachCustomers can reach a person at any point in more than one way, written and spoken, through forms and chat usable by keyboard and screen readerMissing: the route is hidden behind a bot / Partial: one route only, or not accessible / Solid: several routes, tested
Assistant answers and handoverAny bot or AI assistant answers only from approved content, says when it does not know, hands the whole conversation to a person and has a sample of its answers readMissing: answers from general knowledge or stale content, or traps customers / Partial: handover loses the history, or nobody reads its answers / Solid: grounded, honest, sampled

The support channels guide owns the first and third rows, with accessibility as it states it from the Web Content Accessibility Guidelines. Findability follows the help centre SEO guide, any assistant the guide to AI in customer service, and wrong answers already given the diagnosis for an assistant giving customers wrong answers.

Standards and replies

CriterionWhat good looks likeScore guidance
Standards written per channelResponse and resolution standards are set from customers' expectations and the team's capacity, published where customers write in and reported by channel with an ownerMissing: none written / Partial: unpublished, unowned or set from ambition / Solid: published, owned, reported
Routing on written rulesContacts are routed by channel, type of question and the customer's situation on a few written rules, so complaints and urgent cases reach people who can actMissing: one queue in arrival order / Partial: rules in one person's head / Solid: written, complaints first
Tone guidelines in useTone decisions are written once on top of the brand voice, by situation and channel, with approved examples from real replies, and updated from what quality reviews findMissing: each agent decides / Partial: adjectives without examples / Solid: decisions, examples, kept current
Saved replies owned and currentSaved replies start from contact reasons, answer one question each, mark the parts an agent must change, link help articles and carry an owner and a review dateMissing: copied from old emails / Partial: no owners, or articles pasted in / Solid: built from reasons, owned, dated
Pre-purchase questions ownedQuestions from people deciding whether to buy are tagged, answered in approved wording by someone with product knowledge, handed to sales with the question intact and used to fix the pagesMissing: buyers wait in the general queue / Partial: answered but never recorded / Solid: owned, honest, fed back to the pages

Standards follow the support channels guide, routing the service and support hub, and tone the tutorial on writing customer service tone guidelines, which builds on the Brand Voice rather than inventing a second one. Each Saved Reply is judged against the tutorial on building a library of saved replies, and buyers' questions against the guide to answering pre-purchase questions.

Complaints and remedies

CriterionWhat good looks likeScore guidance
One complaint log for every channel (gate)What counts as a complaint is defined, every channel feeds one log, and each complaint is closed with the response sent and its cause recordedMissing: no log / Partial: some channels only, or closed without a cause / Solid: defined, every channel, causes recorded
Recovery sequence followedComplaints are acknowledged quickly, fixed, put right where due and followed up, and public complaints get a calm reply before moving to a private channelMissing: remedy without acknowledgement, or arguments in public / Partial: some agents only / Solid: the same sequence every time
Written remedies and goodwill limitsEach common failure has a standard remedy, customers' rights are kept apart from goodwill, agents use an allowance without asking and every remedy given is recordedMissing: every gesture needs a manager / Partial: rights and goodwill mixed, or nothing recorded / Solid: a table, an allowance used, a record
Customers in vulnerable circumstancesAgents notice signs without labelling people, adapt the process within set limits, record only the support agreed with the customer's agreement and can stop automated messagesMissing: one process for everyone / Partial: sympathy without authority, or too much recorded / Solid: limits set, minimum recorded, automation stopped

The log follows the tutorial on writing a complaints procedure, the sequence the service recovery and complaints guide and remedies the tutorial on setting remedies and goodwill limits, with a written escalation route beyond the allowance. Those guides describe consumer rights from the Competition and Markets Authority's pages as general direction, never legal advice. The last row follows the guide to supporting customers in vulnerable circumstances, which keeps what is recorded to the support agreed, in line with the GDPR.

In step with marketing

CriterionWhat good looks likeScore guidance
Support briefed before campaignsEvery campaign and promotion reaches support as a brief with the exact terms, the claims, likely questions, saved replies, what agents may offer and the end date, before customers see itMissing: agents learn the offer from customers / Partial: briefed on launch day, or on the creative only / Solid: briefed before launch and for the end
Customers told first about disruptionCustomers affected by a delay, fault or cancellation hear it from the business first, with what changes for them, a promised update and a closing message, and support has the same factsMissing: customers find out by chasing / Partial: no update or close, or support not told / Solid: told first, updated, closed
Hours and languages stated plainlyEach channel states its hours in the customer's own time and the languages it answers in, and those promises are kept and reported by marketMissing: unstated / Partial: stated in the business's own time, or not kept / Solid: stated, kept, reported

Briefings follow the tutorial on briefing customer service before a campaign, and disruption messages the guide to proactive service messages, which keeps a notice a service message rather than a promotion, in line with the ICO's direct marketing guidance. Hours and languages follow the guide to supporting customers in several languages and time zones, and a promise the experience cannot keep goes to the tutorial on checking marketing promises against the experience.

Measurement and insight

CriterionWhat good looks likeScore guidance
Contacts tagged by reason (gate)Every contact is tagged on closing with a single main reason drawn from a short list worded as customers put it, agreement is checked on a sample and changes to the list are loggedMissing: no tags, or free text / Partial: used inconsistently, or changed without a record / Solid: one list, tagged at close, checked
Service metrics read in pairsFirst reply, resolution, repeat contacts and contact rate are defined once, each read beside a guardrail and by reason and channel, in a weekly report that ends in decisionsMissing: one headline average / Partial: no definitions, guardrails or base / Solid: paired, by reason, ending in actions
Conversation quality reviewedA fair sample of whole conversations, with every complaint and escalation added, is read against a short scorecard drawn from the written standards by calibrated reviewersMissing: nobody reads replies / Partial: failures only, or no calibration / Solid: fair, traced to standards, calibrated
Causes sent to their ownersThe largest contact reasons and complaint causes are reviewed monthly against a base, each goes to the team that can remove it, marketing included, and the change is recordedMissing: counted and forgotten / Partial: no owners, or marketing absent / Solid: owners named, changes recorded

Each Contact Reason is judged against the tutorial on tagging support contacts by reason. Metrics follow the customer service metrics guide, which reads Contact Rate against orders or customers and treats each Repeat Contact as an answer that was fast but incomplete. The last row is scored against the prevention routine in the diagnosis for rising customer complaints, and the five whys takes a recurring reason from symptom to a cause someone owns.

How to score and prioritise

Score the two gates first. If contacts carry no reason, the channel, help article and saved reply rows describe a guess: mark them provisional. If complaints have no single log, the recovery, remedy and cause rows rest on whichever complaints were remembered.

Then rank the remaining weaknesses in this order:

  • Whatever leaves customers without an answer or a fair fix: no route to a person, an assistant that guesses, no recovery sequence and agents who cannot act.
  • Whatever makes answers wrong or inconsistent: stale articles and saved replies, unwritten tone, unowned pre-purchase questions and campaigns that reach support before the brief.
  • The loop that removes causes, with marketing in it, and disruption told to customers before they chase it.
  • Measurement polish last, unless a missing quality review or a single headline metric is hiding a problem above.

Within each group, rank by the contacts the weakness touches: a fix behind the largest reason outranks the same fix behind a rare one.

Reading the result: what to do with each band

Red means a gate scored missing. Hold changes to channels or staffing, start tagging every contact and logging every complaint from every channel, and read a full cycle before deciding anything else. If contacts are also rising faster than customers, the diagnosis for rising support ticket volume ranks the reasons once tags exist. Rescore on the same evidence window.

Amber means the gates hold at least partially but several other rows are partial or missing, the usual outcome. Work a short ordered list, one area at a time, and read the reasons after each change.

Green means the gates are solid and most rows are too. Move effort into the causes the reasons point at, often on product pages, delivery promises and campaign terms, and rescore each quarter to catch drift.

From findings to a prioritised fix list

Write each partial or missing row as a finding in plain words: what you saw, the evidence and why it matters to customers. Then build one fix list with a line per fix: the finding, the fix, the owner, the guide that explains it and the rescore date, ordered by the priorities above rather than by ease.

Group the lines by who does the work: the reason list and the log with the support lead, articles and saved replies with the content owner, remedies with whoever holds their budget, campaign briefs with marketing and an assistant's sources with its named owner. Show the band, the gate findings and the first fixes to the owner of the customer experience, and keep the full scorecard for the rescore.

Illustrative example

Illustrative example — not a real result

An online wallpaper shop scores its support after a sale

Fenquibrath Wallpapers, an invented online wallpaper shop with a support team of three, runs the audit over the eight weeks around its spring sale, when contacts rose from about 600 to 1,450 a month. Contacts carry no reason, so the first gate scores missing; a hand-tagged sample of 200 shows 38% asking whether rolls from different orders will match and 21% chasing deliveries. The complaint log scores partial: email complaints are logged, but 40 that arrived by phone or in reviews are not. The sale reached support from customers rather than a brief, so that row scores missing, and the chat assistant scores missing because it quotes a returns window the shop changed in the spring; 9 of 26 saved replies repeat the same old window. The band is red. The fix list puts reason tagging and one complaint log first, the assistant's source articles and the stale replies second, a batch-matching article linked from every product page third and a support brief for the summer sale fourth. A month later both gates score partial or better, batch questions fall to 14% of contacts and the band moves to amber.

Common mistakes

  • Scoring speed before reasons. A fast reply to a question nobody should have needed to ask is not good service. Score the gates first and read every metric by reason.
  • Logging only the complaints that arrive by email. Calls, reviews and social comments are complaints too.
  • Treating the assistant as a channel nobody reviews. Its answers are the business speaking; read a sample.
  • Counting saved replies instead of owners. A big library with stale facts is worse than a short current one.
  • Treating repeated failures as agent faults. Failures repeated across agents point at a reply, an article, a policy or a promise.
  • Leaving marketing out of the loop. Many contacts start with a campaign's terms or a page's claim; score whether marketing hears the reasons, not only support.

Frequently asked questions

How is this audit different from the customer retention audit?

The customer retention audit rates the whole system that keeps customers, from churn measured by cohort to onboarding, cancellation, win-back and loyalty, and gives service two of its rows. This scorecard rates the support operation in depth: the channels and help customers can reach, the standards and replies they get, how complaints are put right, whether support hears about campaigns before customers do, and whether what support learns reaches the teams that can fix the cause. Run both when customers leave and complain about the same things.

Why are contact reasons and the complaint log the gates?

Without contacts tagged by reason, nobody can tell which questions drive demand, so every judgement about channels, help articles and saved replies is a guess. Without one log that every channel feeds, complaints that arrive by phone, in reviews or on social media never reach the count, the remedies cannot be reviewed and the same failures recur unseen. Either weakness makes the other scores provisional, which is why both are scored first.

Does a small business with one person answering email need this audit?

Yes, in a lighter form. Most rows ask whether a decision has been made and written down, not whether a large team exists. One person can keep a short reason list, a complaint log, a handful of saved replies with review dates, a remedy table and a habit of hearing about promotions before they launch, and score solid on most rows. The rows about routing and calibrated reviewers matter more as the team grows.

Terms used on this page

Frameworks

Where this page is used

Also related

Sources

  1. Competition and Markets Authority — GOV.UK
  2. Advertising Standards Authority — ASA
  3. Direct marketing guidance — Information Commissioner's Office (UK)
  4. Regulation (EU) 2016/679 (GDPR) — EUR-Lex
  5. Web Content Accessibility Guidelines (WCAG) — W3C
  6. Nielsen Norman Group articles — Nielsen Norman Group

Related