Skip to content

Lesson 5 of 5

Measure results and improve every week

You set up a weekly scorecard with a handful of key figures, hold a fifteen-minute improvement meeting every week and write down your way of working in a service standard. That keeps the system from the previous lessons working.

16 min readUpdated October 16, 2026

Putting it into practice: About 45 minutes to set up the scorecard and the definitions, then about 15 minutes each week to fill it out and a 15-minute meeting. Writing the service standard is a one-time job of an hour or so, plus about 20 minutes to discuss it.

All lessons and your progress

The problem

Every new way of working fades after a few weeks if nobody checks whether it still works. Without fixed figures you cannot tell whether fewer requests are being left sitting, and the team talks about feelings instead of facts.

What you have at the end

You have a scorecard with your baseline, fixed definitions for every figure, a weekly 15-minute meeting with roles, a written service standard and a plan for the next 30 days.

Useful to have beforehand: A baseline from [Lesson 1](/en/academy/customer-service-system/lesson-1-customer-contact-audit), or at least one week of counts of your requests · Preferably the callback list from [Lesson 2](/en/academy/customer-service-system/lesson-2-phone-process) and the appointments and follow-up list from [Lesson 4](/en/academy/customer-service-system/lesson-4-appointments-follow-up). If you do not have those yet, count by hand for now. · Google Sheets or Excel

Why you measure every week

In the previous lessons you took a baseline, introduced a callback process, set up WhatsApp Business and made an appointments and follow-up list. The biggest risk now is that all this slowly fades: the callback list is not updated for a few days, a new employee does not know the labels, and after a busy week everyone falls back into old habits.

Measuring every week prevents that. Not to hold staff accountable, but to see whether the system does what it should: every request gets an answer, everyone who asks for a callback is called back, and nothing stays open unnoticed. In this lesson you:

  1. choose a handful of key figures and write down how you count them;
  2. fill out a simple scorecard every week, with your baseline for comparison;
  3. hold a 15-minute improvement meeting every week in which you choose one improvement;
  4. write down your way of working in a service standard, so it does not depend on one person.

The key figures that matter

A small business does not need twenty figures. These nine together tell you enough. They are also called KPIs; in this lesson we call them key figures.

Nine key figures for your customer contact and where you count them
Key figureWhat it tells youWhere you count it
Unique new requestsHow many customers wanted something from you this weekAudit or follow-up list
% resolvedWhat share of those requests was actually completedResolved or status column
% first response within target timeWhether customers get a first answer quickly enoughTime of the request and of the first response
Callback rateWhether missed calls and callback requests are picked upCallback list (Lesson 2)
Booking rateWhat share of appointment requests becomes an appointmentAppointments and follow-up list (Lesson 4)
OutcomesWhat requests lead to: appointment, information, not interestedOutcome or status column
Open follow-upWhat is still open at the end of the weekStatus and follow-up date
Channel mixWhich channel requests come in throughChannel or source column
Escalations and errorsHow often something has to go to the owner or goes wrong in the contactEscalations, complaints, notes

Count unique requests, not messages

The biggest pitfall is double counting. A customer who calls twice and then sends a WhatsApp message about the same question is one request, not three. If you double count, you see more activity and worse percentages than there really are.

  • One customer, one question, one request. Repeat messages about the same question do not count again.
  • A new question does count again, even if it comes from a customer you already know.
  • Spam and wrong numbers do not count.

Avoid figures that only feel good

Some figures rise with activity or effort without the customer gaining anything. They feel good, but they steer you in the wrong direction.

Vanity metrics and what to measure instead
Instead ofWhy it misleadsMeasure instead
Number of WhatsApp messages sentAlso rises when customers have to ask three times% resolved
Number of phone callsSays nothing about missed calls or about the outcomeCallback rate and outcomes
Followers or likes on social mediaA follower is not yet a requestUnique requests per channel
Only the average response timeUnanswered requests fall outside the average% within target time
Only the number of appointmentsAlso rises when there are simply more requestsBooking rate alongside the number

Write down how you count: numerator and denominator

A percentage is only useful if everyone calculates it the same way. For each figure, write down what goes above the line (the numerator) and what goes below it (the denominator), and stick to that definition every week. If you do change one, note it in the scorecard.

Percentage resolved

% resolved = resolved requests ÷ unique new requests × 100%

Resolved means: nothing more needs to happen on your side. The question has been answered, the appointment has been recorded or the customer does not want to go any further. “We'll get back to you” is not resolved.

Percentage first response within target time

% within target time = requests with a first response within the target time ÷ unique new requests × 100%

Requests that never got a response are included in the denominator, so they count as not on time. An automatic greeting or away message does not count as a first response.

Callback rate

Callback rate = requests called back ÷ (callback requests + missed calls with no later contact) × 100%

A number that called three times counts once. Agree on when a request counts as called back, for example: you spoke to the customer, or you left a message after two attempts.

Booking rate

Booking rate = appointments booked ÷ appointment requests × 100%

An appointment request counts even if there was no slot available. If you work with orders or quotes, read that word instead of appointment.

Escalation rate

Escalation rate = escalations ÷ unique new requests × 100%

An escalation is a request that had to go to the owner or a specialist under your rules from Lesson 2. With small numbers, look at the cases themselves, not at the percentage.

Two key figures are a count, not a percentage:

  • Open follow-up: what has not been resolved by the end of the week, even if it comes from earlier weeks. Always count at the same time, for example Monday morning before opening.
  • Errors and complaints about contact: wrong information given, an appointment double-booked, a customer who was not called back. Complaints about the product or the treatment itself do not belong here.

The channel mix is optional. Calculate it once a month: unique requests through one channel ÷ all unique new requests × 100%.

Filling out your weekly scorecard

The scorecard is one row per week: ten counts and a note. The file works out the percentages itself. With up-to-date lists, filling it out takes about fifteen minutes.

Weekly customer service scorecard (spreadsheet)

Fill in a few counts each week; the percentages work themselves out. With the definition of every KPI, so everyone counts the same way.

  1. Choose a fixed week and a fixed time

    Let a week run from Monday through Sunday. Fill it out at a fixed time, for example Monday morning before opening, and have the same person do it every time.

  2. Add your baseline

    Take the week from your customer contact audit (Lesson 1) as the first row, with “Baseline” as the note. If you counted differently then from the definitions above, count again. Otherwise you will end up comparing apples and oranges.

  3. Take the counts from your lists

    Requests, resolved and first response from the audit or follow-up list, callbacks from the callback list, appointments from the appointments and follow-up list. Filter by the dates of the week.

  4. Count the open follow-up

    At the fixed time, including items from earlier weeks. This number is a snapshot of the end of the week.

  5. Write a note

    A holiday, a promotion or advertisement, an employee out sick, a broken phone, a new way of working. Without a note, two months from now you will no longer know why a week was different.

  6. Look at the trend, not at one week

    Compare with the baseline and with the previous three weeks. Only after four to six weeks can you see whether something is really changing.

Baseline versus now: comparing fairly

After a few weeks you will want to know whether it works. Compare the baseline with the weeks after the changes, and be honest about what the figures do and do not tell you.

What you can conclude

Process figures such as % resolved, callback rate and open follow-up depend mainly on what you do yourself. If they improve right after you introduce a callback list or fixed follow-up, and stay that way, it is reasonable to assume the new way of working helps.

Why more appointments are not automatically due to your approach

The number of appointments or orders depends on much more than your customer contact. Go through these causes before you credit a rise to your way of working:

Other causes of a difference in appointments
CauseExampleWhat you do
SeasonThe rush before the holidays, quiet vacation weeksCompare with the same period last year, if you have those figures
Promotions and advertisingA promotion on Facebook, an advertisement, flyersNote every promotion in the scorecard
HolidaysA week with a day off has fewer business daysCompare with an ordinary week instead
CapacityAn extra employee, a colleague out sick, a full calendarCheck whether there was room, not just the number
Chance with small numbers4 out of 5 is 80%, 3 out of 5 is 60%Look at the counts and at several weeks
  • Always look at both the count and the percentage.
  • Change as little as possible at once, so you can tell better what helps.
  • Compare three to four weeks after the change with the baseline, not one good week.

Worked example

Example: a hair salon in Zorg en Hoop (fictional)

Example data, fictional. A hair salon with a staff of three took a baseline in Lesson 1. The salon then introduced a callback list, quick replies and labels in WhatsApp Business, and an appointments and follow-up list. This is how the third week after the changes compares with the baseline:

Counts: baseline and week 3 (fictional)
CountBaselineWeek 3
Unique new requests6070
Resolved3960
First response within target time2449
Callback requests and missed calls1615
Called back613
Appointment requests2832
Appointments booked1624
Open follow-up (end of week)146
Escalations23
Errors and complaints about contact41
Calculated, rounded to whole percentages (fictional)
Key figureBaselineWeek 3
% resolved39 ÷ 60 = 65%60 ÷ 70 = 86%
% within target time24 ÷ 60 = 40%49 ÷ 70 = 70%
Callback rate6 ÷ 16 = 38%13 ÷ 15 = 87%
Booking rate16 ÷ 28 = 57%24 ÷ 32 = 75%
Escalation rate2 ÷ 60 = 3%3 ÷ 70 = 4%

A fair reading of these figures:

  • The process is clearly better. Resolved, within target time, callback rate and open follow-up improved exactly where the salon changed something. One week is short, though; the salon is watching whether it holds.
  • The 8 extra appointments are not only due to the new system. 10 more requests came in, a promotion ran on Facebook in week 3, and an extra staff member worked on Saturday.
  • The higher booking rate (from 57% to 75%) is not only the work of the new list either. Fewer requests were probably lost, but the extra staff member also freed up more slots.
  • Escalations did not really rise. From 2 to 3 is one case. The salon looks at the three cases in the meeting instead of drawing conclusions from the percentage.
  • Conclusion: the new way of working seems to clearly improve how customers are followed up. How many extra appointments it brings cannot be told from these two weeks. The salon keeps up the scorecard and will later also compare weeks without a promotion and without extra staff.

The 15-minute improvement meeting

Figures alone change nothing. So hold a short, fixed meeting every week, ideally right after the scorecard has been filled out. Standing behind the counter or on a video call: what matters is the fixed structure, not the place.

The weekly improvement rhythm

  1. Step 1: Measure

    Fill in this week's scorecard

  2. Step 2: Discuss

    Fifteen minutes with the team

  3. Step 3: Pick one improvement

    The biggest bottleneck, not everything at once

  4. Step 4: Put it in place

    With an owner and a date

  5. Step 5: Measure again

    Next week: did it help?

And then back to the start, every week.

The weekly rhythm: measure, discuss, choose one improvement, put it in place and measure again.

Roles

Roles in the meeting (in a small team, one person sometimes has two roles)
RoleWhoTask
ChairOwner or managerKeeps time and makes sure there is one decision
ScorekeeperWhoever fills out the scorecardPrepares the figures and three to five cases
ImplementerChanges with each improvementCarries out the improvement before the agreed date
Note-takerChair or scorekeeperWrites the decision in the improvement log

The agenda, minute by minute

  1. Review the figures (3 minutes)

    The scorekeeper gives this week's figures next to last week's and the baseline. Only discuss notable differences, not every number.

  2. Sample of cases (5 minutes)

    Look at three to five real requests from the lists, for example an escalation, a late response and an item that is still open. For each case, ask: what happened, and where did it get stuck?

  3. Choose one bottleneck (3 minutes)

    Choose the bottleneck that comes up most often or affects customers most. One, even if you see five. Note the rest for another time.

  4. Assign an improvement (3 minutes)

    Small, concrete and with one owner. Not “pay more attention,” but “make a quick reply for the question about prices and show it to everyone on Friday.”

  5. Set a review date (1 minute)

    Usually the meeting one or two weeks later. Write the decision in the improvement log. If a topic needs more time, schedule a separate time for it: the weekly meeting stays at fifteen minutes, otherwise it gets skipped after a few weeks.

Improvement log

Keep one block per decision, in a notebook or in an extra tab next to your scorecard.

Meeting date: [date]

Bottleneck: [what went wrong, and how often]

Improvement: [what exactly we will do differently]

Owner: [name or role]

Done by: [date]

Review date: [date of the meeting where we look back]

Result at the review: [works / partly works / does not work, and what we do now]

Worked example

Example: a decision from the meeting (fictional)

In the hair salon's sample, it turns out that two of the three customers who did not show up had not received a confirmation of their appointment. Whether a confirmation went out depended on who was behind the counter.

  • Bottleneck: appointments are not always confirmed.
  • Improvement: every afternoon at 4:00 PM, a confirmation via WhatsApp for all of the next day's appointments, to customers who have agreed to this.
  • Owner: the receptionist; when she is absent, the owner.
  • Review: in two weeks, using the number of appointments with the status No-show in the appointments and follow-up list.

Write down your way of working in a service standard

Everything you introduced in this course only works as long as people know about it. A service standard is a one- or two-page document that sets out how your business handles customer contact: who answers, how quickly you respond, what happens to a missed call, when something goes to the owner. You give it to every new employee and every backup.

  • Short: the details are in your scripts, quick replies and lists; the standard refers to them.
  • Concrete: times and roles, not “as soon as possible,” because you cannot measure that.
  • Made together: discuss the draft with the team. What nobody thinks is achievable will not happen in practice anyway.
  • Dated: with a version date and a date when you will look at it again, for example every quarter.

Internal service standard (template to fill out)

Copy this into a document, fill in everything between [brackets] and delete whatever does not fit your business.

Service standard [Business name], version [date], next review [date]

1. Availability: we can be reached on [days] from [time] to [time] via [phone / WhatsApp Business / email / at the front desk].

2. First response: during business hours we reply on WhatsApp within [number] minutes and answer the phone within [number] rings. Outside business hours we reply [the next business day before …].

3. Missed calls: every missed call goes on the callback list and is called back [the same day / within … hours] by [role]. After [number] attempts we send a message.

4. Who does what: phone [role], WhatsApp Business [role], appointments and follow-up list [role], cover during absence [role].

5. Recording: every request that is not resolved right away goes into [name of the list], with an owner and a follow-up date.

6. Appointments: we confirm every appointment [via WhatsApp / by phone] and send a reminder [a day in advance] to customers who have agreed to this.

7. Escalation: complaints, [emergencies / large amounts / other situations] and questions we do not know the answer to go to [role] within [time]. In an emergency we refer the customer straight to [emergency services / the right authority].

8. Handoff: at the end of a shift or during absence, [role] hands over open items via [list / handoff message].

9. Privacy: we only record what is needed to help the customer, and no [payment details / medical details] in lists or chats. Access to the lists: [roles].

10. Measuring and improving: [role] fills out the scorecard every [day]. The improvement meeting is every [day] at [time] and lasts 15 minutes. Decisions are recorded in the improvement log.

Target times and definitions: see the KPI definitions tab in the scorecard.

Keeping it going yourself: the next 30 days

You now know all the parts: a baseline, a phone and callback process, WhatsApp Business, an appointments and follow-up list, a scorecard and a fixed meeting. Not everything in place yet? The 30-day plan turns the whole course into four weeks, with the tasks for each week, who does them, how long they take and how you can tell it works.

30-day plan for your customer service

Week by week: what you introduce, who does it and how you can tell it works.

If everything is already running, the next 30 days are about keeping it going:

Maintenance plan for the next 30 days
WeekFocusDone when
Week 1Fill out the scorecard at the fixed time; hold the first meetingThe baseline and week 1 are in; one improvement has been assigned
Week 2Sample of cases; draft the service standardThe draft has been discussed with the team
Week 3Review the first improvement; finalize the service standardThe core is up by the phone or counter; the log is up to date
Week 4Put four weeks next to the baselineYou know what stays, what needs to change and what the next bottleneck is

Warning signs

  • The scorecard has not been filled out for two weeks in a row.
  • Open follow-up grows three weeks in a row.
  • The same bottleneck keeps coming back in the meeting, without the improvement being carried out.
  • The meeting is skipped more often than it is held.

If you see one of these signs, make the system smaller rather than giving up on it: fewer figures and a shorter meeting, but every week.

If you later want to automate repetitive work, with whatever tool, only start once the way of working is written down and works. Your service standard then describes what needs to happen, and your scorecard shows whether the tool really helps.

Have you worked through all five lessons? Complete the course and keep the customer service playbook, with all the lessons, scripts and checklists on one page.

Checklist for this lesson

Checklist

Saved on this device only

Downloads for this lesson

Weekly customer service scorecard (spreadsheet)

Fill in a few counts each week; the percentages work themselves out. With the definition of every KPI, so everyone counts the same way.

30-day plan for your customer service

Week by week: what you introduce, who does it and how you can tell it works.

Test your knowledge

  1. 1. A customer calls twice without anyone answering and then sends a WhatsApp message about the same appointment. How many unique new requests do you count?
  2. 2. Why do requests that never got a response count in the denominator of “% first response within target time”?
  3. 3. In the week after you introduce your follow-up list, the number of appointments rises from 16 to 24. A promotion on Facebook also ran that week. What do you conclude?
  4. 4. In the weekly meeting the team sees four bottlenecks. What is the idea?
  5. 5. Which figure says the least about the quality of your customer service?
  6. 6. What belongs in a good internal service standard?

This quiz is for testing yourself. You don't have to pass it to complete the lesson.

What to do now

  • Fill out the scorecard today with your baseline from Lesson 1, and put the first improvement meeting on the calendar.
  • Write a draft of your service standard this week and discuss it with the team.
  • Follow the 30-day plan week by week.
  • Complete the course once you have worked through all the lessons.