Free guide · Claudia Academy
All-in-one customer service playbook
Learn step by step how to organize phone calls, WhatsApp messages, appointments and follow-up professionally, even without paid software.
Version 1.0 · reviewed 2026-10-16 · goes with lesson 1, lesson 2, lesson 3, lesson 4, lesson 5
Lesson 1
Map your customer contact
For seven days you record every customer contact, count how many unique requests you receive and how many are left waiting, and carefully work out what that might be worth. You finish with a worksheet listing your three biggest communication bottlenecks.
Why you measure first
“We miss a lot of calls” and “nothing slips through here”: you hear both often, and usually neither is quite right. Five missed calls may come from two customers who keep trying. And a WhatsApp message that arrives in the evening and is only seen two days later does not feel missed to you. To the customer, it does.
That is why you measure first, before you change anything. For one week you record every customer contact in a simple spreadsheet. Afterward you know how many unique requests you receive, how many of them got a response, how quickly, and where requests are left waiting. That is your baseline: the starting point for the next lessons, and the yardstick you use in Lesson 5 to see whether things are improving.
How a request moves through your business
From request to outcome
Step 1: Customer gets in touch
Phone, WhatsApp, website or at the counter
Step 2: Record it
Time, channel and the question, without unnecessary details
Step 3: Respond
Within the time you agreed on yourself
Step 4: Follow up
One owner and a date
Step 5: Note the outcome
Appointment, information given, not interested
A request can get lost at every step: a call is not answered (respond), nobody writes down that the customer wants a quote (record), or the promised quote is never sent (follow up). The audit shows where things go wrong in your business.
Step 1: list all your channels
Customers choose for themselves how they get in touch. So list every place where a question can come in, including the “unofficial” ones, such as the owner’s private number that regular customers know, or messages via Facebook.
| Channel | Where does it come in? | Who sees it? | Where do you see what was missed? |
|---|---|---|---|
| Phone (landline) | Phone at the front desk | Owner | On the display, if it shows missed calls; otherwise a tally sheet |
| WhatsApp messages and calls | WhatsApp Business on the business phone | Owner and a mechanic | Unread chats and missed calls in WhatsApp |
| Website and email | Email inbox | Owner | Unread and unanswered emails |
| Walk-in | Front desk | Whoever is at the front desk | Nowhere, unless someone writes it down |
| Other | Facebook, the owner’s private number | Owner | Messages and calls on the private phone |
Write down every channel
Note every channel through which customers reached you in the past month. Ask your team as well: they often know better where customers come knocking.
Note who checks the channel
If it says “everyone” or “nobody in particular,” you already have a first clue to a bottleneck.
Find out where you can see missed contacts
For example in the list of missed calls, the unread chats or the inbox. If you cannot see it anywhere, put a tally sheet next to the phone.
Decide what you measure
Include every channel on which customers expect an answer. Record walk-ins only if they have a question, not every customer who comes in to pay or pick something up. If you leave a channel out, write that down as a limitation of your measurement.
Step 2: agree on what counts as a request
Agree with your team beforehand on what you record and how, otherwise you will end up comparing apples to oranges. A request is any question or wish from a customer that requires your business to do something: answer, give a price, make an appointment. The spreadsheet has four contact types.
| Type | What it is | Example (fictional) | Counts as a unique request? |
|---|---|---|---|
| New request | First contact about a new question: price, appointment, quote | “How much is a minor service?” | Yes |
| Existing customer | First contact about something already under way: a job, order or appointment | “Is my car ready yet?” | Yes |
| Repeat message | Same person, same question, not yet resolved | The same caller calls again ten minutes later | No, but do record it |
| Spam/irrelevant | Not a customer question | Sales caller, wrong number | No |
The difference between unique requests and contact attempts is the heart of an honest measurement. If a customer calls three times without getting through and then sends a WhatsApp message, that is four contact attempts but one request. You record all four, so you can see how often customers have to try: the first as a “New request” row, the rest as “Repeat message” rows. If you count all four as requests, the problem looks four times as big.
Missed calls from unknown numbers
If you cannot reach the caller when you call back, record the call as a “New request” with the subject “unknown (missed call)” and the outcome “Unknown” in the log. Count this group separately in the analysis. It may have been a customer, but it may also have been a wrong number. That is why the opportunity estimate works with an assumption about what share really was a customer.
Step 3: measure for seven days
A week is short enough to keep up and long enough to see busy and quiet days. Choose an ordinary week, without a holiday or a big promotion. Measure for seven days in a row, including days when you are closed: messages and calls still come in.
Customer contact audit (spreadsheet)
Record every customer request for seven days. The Summary tab automatically counts your unique requests, the response rate and the average response time.
Preparation: half an hour
Choose a target time per channel
How quickly do you want to give a first response? You choose that yourself; it is not a standard. For example: answer the phone or call back within 2 hours, WhatsApp within 1 hour, email the same business day, and outside business hours before 10:00 AM the next business day. That way everyone judges “late” in the same way.
Assign one person per channel to do the recording
That prevents duplicate rows and gaps. In a small team, one person can do everything.
Set up the spreadsheet
Download the template, delete the fictional example rows and share the file only with the colleagues who are recording. Prefer paper? Use a notebook with the same columns and transfer it at the end of the week.
Explain to the team how you record
Use the team instructions below and agree on who updates the log and when.
Team instructions: how we record every request this week
Send this to the team’s group chat or put it up by the phone. Fill in the parts in brackets yourself.
From [start date] through [end date], we are keeping track of how customers reach us. This is not about who does something wrong, but about where requests are left waiting.
Make one row per contact: every call (including missed ones), every new WhatsApp chat or WhatsApp call, every email or website question and every walk-in with a question.
Choose the type: New request, Existing customer, Repeat message (same person, same question) or Spam/irrelevant.
Subject: short and general, for example “price minor service.” No names, phone numbers, license plates, addresses, health or payment details.
Note how many minutes it took before one of us actually responded. Picked up right away counts as 0. An automatic message or a callback that nobody answers does not count.
Our target times: phone [target time], WhatsApp [target time], email [target time], outside business hours [target time]. Later than that counts as “Answered late” in the Status column.
Has something been promised, such as a callback or a quote? Then fill in owner, next action and follow-up date.
[Name] updates the log every day at [time], with the missed calls and unread chats alongside.
What you record per contact
| Column | What you fill in | Example (fictional) |
|---|---|---|
| Date and time | When the contact came in | 10/7/2026, 7:40 PM |
| Channel | How it came in | WhatsApp message |
| Contact type | One of the four types above | New request |
| Subject (general) | Briefly what it is about, without personal details | Dead battery, wants to come by tomorrow |
| During business hours? | Yes or No | No |
| Status | Answered (within target time), Answered late or Unanswered | Answered |
| First response (minutes) | Minutes until the first real response; empty if it never came | 790 (the next morning at 8:50 AM) |
| Resolved? | Has the question been resolved? Yes, Partly or No | Yes |
| Owner | Who moves the request forward (job title or first name) | Front desk |
| Next action and follow-up date | What still needs to happen, and when | Send the quote, 10/8/2026 |
| Outcome | Appointment/order, Information given, Not interested, Referred, Open or Unknown | Appointment/order |
Fill in the columns from Status onward only on the first row of a request, and leave them empty for repeat messages and spam. That way each request counts once in the Summary.
During the measurement week
- Update the log at a fixed time every day, with the missed calls, the unread chats and the inbox alongside.
- If a response comes later, still fill in the status and response time on that request’s row.
- If a question has not been resolved by the end of the week, leave “Open” as the outcome. That is exactly what you want to see.
- Try not to suddenly do everything differently this week: you are measuring how things go now. Improving comes in the next lessons.
Step 4: count and calculate
After seven days, first update the open rows. The Summary tab then works out most of it by itself. This is what each figure means, so you can also work it out on paper:
Unique requests
Unique requests = rows with type “New request” + rows with type “Existing customer”
Repeat messages and spam are not counted. All rows except spam together are your contact attempts.
Answered and unanswered
Answered = “Answered” + “Answered late” requests; unanswered = unique requests − answered
Count only the first row of each request.
Response rate
Response rate = answered requests ÷ unique requests × 100%
Also look at the share within your target time: requests with status “Answered” ÷ unique requests × 100%.
Average first response
Average first response = sum of all response minutes filled in ÷ number of requests with a response time
Unanswered requests have no response time and are not counted here. So always look at this figure together with the response rate.
Follow-up completed
Follow-up completed = requests with a follow-up date that are now resolved ÷ all requests with a follow-up date × 100%
Open follow-up is the number of requests with a follow-up date that are not (fully) resolved yet.
Average or median?
One message from Friday evening that is not answered until Monday pushes your average up considerably. The median is less affected by that: it is the middle value when you put all response times in order from smallest to largest (with an even number, the average of the two middle values).
Example (fictional): five WhatsApp responses after 5, 10, 20, 35 and 2,880 minutes. The average is (5 + 10 + 20 + 35 + 2,880) ÷ 5 = 590 minutes, almost ten hours. The median is 20 minutes. Both are correct: most customers got a quick answer, but one customer waited two days. So note both, and look separately at contact during and outside business hours.
Break down your figures
- By channel: where are the most requests left waiting?
- During and outside business hours: how much comes in when you are closed, and how long does it wait?
- By time of day: are there regular busy times, such as around noon or just before closing time?
- By owner: are there requests without an owner, or does everything end up with one person?
A filter on the columns in Google Sheets or Excel is enough for this.
Step 5: keep facts and assumptions apart
Your audit produces facts: things you have counted. As soon as you explain what those facts mean, you are making assumptions. That is fine, as long as you label them as assumptions. The danger lies in an assumption that gets passed on as a fact, such as “we are losing SRD 36,000 every week.”
| Statement | Fact or assumption? | Why |
|---|---|---|
| 12 of the 60 unique requests got no response | Fact | Counted in the audit |
| 7 of those 12 came in between noon and 2:00 PM | Fact | Can be read from the date and time |
| Half of the unanswered requests genuinely wanted a job done | Assumption | With a missed call and no message, you do not know why someone called |
| Anyone who got no answer went to another garage | Assumption | Perhaps the customer called back later or came by after all |
| An average job brings in SRD 3,000 | Fact if it comes from your invoices | An estimate from memory is an assumption |
Put two headings under your figures: Measured and Assumed. Write each assumption underneath, with the figure you use. Then someone else, or you yourself a month from now, can see what the calculation rests on.
Step 6: carefully estimate what you may be missing
What do those unanswered requests cost you? The honest answer: you do not know exactly. But you can make a hypothetical calculation, with assumptions you choose and write down yourself.
Hypothetical gross revenue per week
Missed unique requests × % genuinely qualified × % reachable with timely follow-up × % that becomes a customer × average order value
The result is hypothetical gross revenue: not profit and no guarantee of extra revenue.
- Missed unique requests (measured): new requests without a response, or answered so late that the customer had reasonably already gone elsewhere. No repeat messages, spam or questions from existing customers.
- % genuinely qualified (assumption): what share was really looking for something you provide?
- % reachable (assumption): what share would you still have spoken to if you had responded in time?
- % that becomes a customer (assumption): look at how many answered new requests in your audit ended with “Appointment/order” as the outcome. For the missed group it remains an assumption, but a well-founded one.
- Average order value: from your invoices or sales records, not from memory.
Worked example
Example: the garage on Indira Gandhiweg (fictional)
In seven days the garage records 83 rows: 8 spam, 15 repeat messages and 60 unique requests. That is 75 contact attempts for 60 requests. Of those 60, 48 got a response and 12 remained unanswered, all of them new requests.
The owner writes down these assumptions. They are estimates, not measurements:
- Suppose 50% genuinely wanted a job done. Four of the twelve were missed calls without a message; nobody knows what those callers wanted.
- Suppose 60% of those could have been reached with a timely callback.
- Suppose 40% of those would book. As a check: of the answered new requests, about 4 in 10 led to an appointment this week.
- Suppose an average job brings in SRD 3,000, rounded from the invoices of the past three months.
| Step | Calculation | Result |
|---|---|---|
| 1. Missed unique requests (measured) | Counted in the audit | 12 |
| 2. Genuinely wanted a job done (assumption 50%) | 12 × 0.50 | 6 |
| 3. Reachable with timely follow-up (assumption 60%) | 6 × 0.60 | 3.6 |
| 4. Would book (assumption 40%) | 3.6 × 0.40 | 1.44 |
| 5. Hypothetical gross revenue per week | 1.44 × SRD 3,000 | SRD 4,320 |
1.44 jobs is not a real customer but an expectation: with these assumptions, on average about one and a half extra jobs a week, or roughly SRD 4,320 in hypothetical gross revenue. So not SRD 36,000 (12 × SRD 3,000): that would mean every unanswered request was a paying customer, and that is almost never the case.
And if the assumptions turn out lower?
Always work through a cautious scenario as well. Suppose only 30% genuinely wanted a job done, 50% were reachable and 25% would book:
| Step | Calculation | Result |
|---|---|---|
| 1. Missed unique requests (measured) | Counted in the audit | 12 |
| 2. Genuinely wanted a job done (assumption 30%) | 12 × 0.30 | 3.6 |
| 3. Reachable (assumption 50%) | 3.6 × 0.50 | 1.8 |
| 4. Would book (assumption 25%) | 1.8 × 0.25 | 0.45 |
| 5. Hypothetical gross revenue per week | 0.45 × SRD 3,000 | SRD 1,350 |
Then it comes to about one extra job every two weeks. So the same fact, 12 unanswered requests, yields anything between SRD 1,350 and SRD 4,320 a week, depending on the assumptions. That range is more honest than a single figure.
If the garage keeps about 35% after parts and other direct costs (also an assumption), the hypothetical gross margin in the first scenario is SRD 4,320 × 0.35 = SRD 1,512 a week. That is not net profit either: wages, rent and the extra time for those jobs have not been deducted yet.
Why the result is not profit and not a promise
Even with honest assumptions, the calculation remains a model. Keep four things in mind:
- Repeat callers. People who keep trying are often helped in the end. Someone who was answered after three attempts is a service problem (the customer had to make an effort), but not a missed request. So count only requests that really got no response.
- Capacity. If your calendar or your shop is already full, you may not even be able to take on extra work. Then it is more about answering customers properly, referring them elsewhere or offering a later time.
- Differences between types of business. A restaurant gets many requests with a low order value, a hotel few with a high booking value, and regular customers of a salon often simply call back later. For a practice or clinic, a missed call is mainly about being reachable and about care; it is better not to think in terms of revenue there. Do not copy percentages from another business, not even from this example.
- Unknown attribution. You do not know whether a customer you called back would have come anyway without that call. And if your revenue rises after you have improved something, that may also be due to the season, prices or the competition.
Use the result to decide whether a bottleneck is worth tackling, and roughly what a solution may cost. Not as a promise to yourself, your team or the bank.
Calculate with your own figures
Enter your own numbers and assumptions in the calculator; the formulas are shown alongside and nothing is stored. Among the requests answered late, count only those where the customer had reasonably already gone elsewhere. The calculator has one field for the share that was a real opportunity and one for the share that would become a customer with timely follow-up. If you want to include reachability separately, as in the example, multiply first: 60% reachable × 40% book = 24%. Enter that 24% as the share that would become a customer.
The calculator also has its own page, which is handy when you calculate again later with new figures:
Missed requests calculator
Work out with your own assumptions what unanswered requests could hypothetically be worth. Every formula is shown; nothing is stored.
Worksheet: your top 3 communication bottlenecks
Finish the audit with the three bottlenecks that leave the most requests waiting or keep customers waiting longest. Three is enough: if you tackle everything at once, you finish nothing.
Gather the problem cases
Filter by the statuses “Unanswered” and “Answered late” first, then by requests with a follow-up date that have not been resolved. Promises that are not kept often weigh more heavily than missed calls.
Look for patterns
One channel? Fixed times? Outside business hours? No owner? Whatever recurs across several requests is a bottleneck; a single chance outlier is not.
Choose the three biggest
Weigh how many requests it affects and how annoying it is for the customer. A quote that never arrives weighs more than a price question answered an hour later.
Fill in the worksheet
For each bottleneck, write down the evidence from your audit (a figure, not a feeling), the effect on the customer, a first small measure, and who carries it out from when.
| Bottleneck | Evidence from the audit | Effect on the customer | First measure | Who and when |
|---|---|---|---|---|
| Phone not answered between noon and 2:00 PM | 7 of the 12 unanswered requests | Cannot reach anyone and hears nothing back | A fixed backup during lunch; call back missed calls at 2:00 PM | Front desk staff member, starting Monday |
| WhatsApp messages sent after closing time are left waiting | Median first response outside business hours: over 14 hours | Waits until well into the next day | At 8:00 AM, first answer all messages from the evening and night | Owner, starting Monday |
| Quotes without a follow-up date | 3 of the 5 quote requests still open at the end of the week | Waits for a price that never comes | Every quote gets an owner and a follow-up date in the log | Owner, this week |
Worksheet to copy: top 3 communication bottlenecks
Copy this into a document or notebook and fill it in for each bottleneck. Use figures from your audit as evidence.
Measurement week: [start date] through [end date]. Unique requests: [number]. Unanswered: [number]. Response rate: [percentage]. Median first response: [minutes]. Open follow-up: [number].
Bottleneck 1: [what goes wrong, in one sentence]
Evidence: [figure from the audit, for example “7 of the 12 unanswered requests came in between noon and 2:00 PM”]
Effect on the customer: [what the customer notices]
First measure: [one small, concrete change]
Who and starting when: [owner], [date]
Bottleneck 2: [description]. Evidence: [figure]. Effect: [on the customer]. Measure: [change]. Who and when: [owner, date]
Bottleneck 3: [description]. Evidence: [figure]. Effect: [on the customer]. Measure: [change]. Who and when: [owner, date]
Measure again on: [date, for example in four weeks]
Where to go next
- Phone not answered at busy times, or nobody calling back? Continue with Lesson 2: phone and callback system.
- WhatsApp messages left waiting, everything on one phone, the same questions over and over? Then Lesson 3 on WhatsApp Business will help.
- Promised quotes and callbacks without an owner or a date? You tackle that in Lesson 4 on appointments and follow-up.
- Keep the totals from the Summary: in Lesson 5 you use them as a point of comparison.
Checklist
- ☐ I have written down all my channels, with who checks them and where missed contacts can be seen.
- ☐ I have chosen my own target time for the first response for each channel and shared it with the team.
- ☐ I have downloaded the spreadsheet, deleted the example rows and explained to the team how we record.
- ☐ I have recorded every contact for seven days, including missed calls and repeat messages.
- ☐ The log contains no names, phone numbers, license plates, addresses, health or payment details.
- ☐ I have calculated unique requests, answered, unanswered, response rate, average and median response time, and open follow-up.
- ☐ I have written down facts and assumptions separately and labeled my opportunity estimate as hypothetical gross revenue, with a cautious scenario alongside it.
- ☐ I have filled in my top 3 communication bottlenecks, each with evidence, a first measure, an owner and a date.
- ☐ I have scheduled a date to delete the detail rows and remove shared access after the analysis.
Lesson 2
Build a professional phone and callback system
You lay out how your team answers the phone, who returns missed calls and who takes over difficult calls. You create scripts, a callback list, an escalation plan and a short training session for your team.
Why the phone needs a fixed way of working
In many small businesses, whoever is closest to the phone picks up. That works as long as it is quiet. At busy times the phone keeps ringing, nobody writes the number down, and an hour later nobody knows who called.
A caller who cannot reach anyone may just as well call the next business. You never see that anywhere: a customer simply does not come. That is why the phone deserves fixed arrangements, just like the cash register.
In this lesson you create four things:
- A call structure in six steps, with scripts for the whole team.
- A callback process: who keeps track of missed calls, how soon you call back and when you stop.
- An escalation plan: what everyone handles themselves and what goes to the specialist, the owner or emergency services.
- A 15-minute exercise to practice it with your team.
Worked example
Example: the lunchtime rush at a garage (fictional)
Garage Amrit (fictional) on the Indira Gandhiweg has four mechanics and one front desk employee, Shanti. Between noon and 1:00 PM, customers call during their own lunch break: is my car ready, can I make an appointment? That is exactly when Shanti is on her break, or at the counter helping a customer who is paying.
The phone also rings in the shop, but the mechanics have greasy hands and a car on the lift. One Tuesday, five calls go unanswered in that hour. At 1:15 PM Shanti sees them on her phone, but she does not know which ones are important. She calls two numbers back; the rest get buried.
Later in this lesson you will see how the same garage handles this with a lunch arrangement, a callback list and an escalation plan.
The incoming call in six steps
A good phone call almost always follows the same order. If everyone on your team knows that order, your business sounds the same no matter who picks up.
Greet
Pick up before the phone has rung for long. Say good morning or good afternoon, the business name and your first name, so the caller knows they have the right number and who they are talking to.
Find out what the call is about
Let the caller finish. Then ask follow-up questions until you know what kind of request it is: an appointment, information, a job in progress, a complaint or something urgent.
Ask only what you need
Ask only what you need to handle it or pass it on. Usually that is the name, the best number to call them back at and a short description.
Confirm
Briefly repeat what you have written down and what will happen, and let the caller confirm it. This is where you still catch a wrong digit or a wrong time.
Deal with it or pass it on
Answer the question if you can. Otherwise transfer the call or set up a callback at a time you can keep. No caller hangs up without knowing what the next step is.
Close properly
Sum up what was agreed, thank the caller by name and hang up without rushing.
| Type of request | What you write down as a minimum | Example question |
|---|---|---|
| New appointment | Name, number, service, preferred day and time of day | Which day works best for you, and do you prefer morning or afternoon? |
| Information (price, business hours, address) | Nothing, unless you need to call back | Is this about [service] or about something else? |
| Status of a job in progress | Name and what it is about, for example the make and model of the car or the appointment date | What name is the appointment under? |
| Complaint | Name, number, what is wrong and what the customer expects | What would be a good solution for you? |
| Urgent or dangerous | First act according to the escalation plan, then write it down | Are you somewhere safe right now? |
Reception script: answering the phone
For everyone who answers the phone. Adjust the wording so it sounds natural in your business, but keep the order.
[Good morning/Good afternoon], [Business name], this is [First name]. How can I help you?
(Listen. Let the caller finish.)
Just so I can help you best, is this about a new appointment, a [job/order] that’s already in progress, or something else?
May I have your name? I want to make sure I write it down correctly.
Is the number you’re calling from the best one to reach you at?
Let me read that back to you: your name is [name], you’re calling about [question], and we’ll [next step] on [day and time]. Is that correct?
Is there anything else I can help you with?
Thank you for calling, [Mr./Ms. + last name]. Have a great day.
Putting a caller on hold or calling back when it is busy
When you are in the middle of something else. An honest promise is better than a caller left on hold for a long time.
[Good morning/Good afternoon], [Business name], this is [First name]. I’m helping a customer right now. May I put you on hold for just a moment?
(Come back within a minute. If you can’t:) I’m sorry, this is taking longer than I expected. Would it be OK if I called you back? That way I can give you my full attention.
May I have your name and the best number to reach you at? And could you tell me briefly what it’s about?
Great, I’ll call you back [before 2:00 PM / within the hour]. Talk to you soon.
The process for missed calls
No matter how well your team answers the phone, calls will always be missed. The problem only starts when nobody is responsible for what happens next. A callback process spells out who checks, who calls, in what order and when you stop.
The callback process
Step 1: Missed call
Someone called and couldn't reach anyone
Step 2: Write it down
On the callback list: time, number, reason if known
Step 3: Prioritize
Urgent first, then new customers, then the rest
Step 4: Call back
By the owner of the list
- Reached: Handle the question and note the outcome
- Not reached: One more try later, then one WhatsApp message
Step 5: Close or stop
After the agreed attempts: don't keep calling
Who keeps track of missed calls?
Assign one person to handle callbacks on each shift. That does not have to be the owner, but it does have to be someone who can get to the phone and is given the time to call back. Put the name on the schedule, so there is no doubt.
Agree on fixed check times, for example every hour on the hour, right after lunch and fifteen minutes before closing time. Every missed call then goes on the callback list: a sheet of paper next to the phone or a tab in your spreadsheet.
In what order do you call back?
| Priority | Type of call | Example |
|---|---|---|
| 1 – immediately | A customer with an appointment or job for today, or a voicemail that suggests it is urgent | The customer whose car was due to be ready at 1:00 PM |
| 2 – within the target time | All other calls during business hours, including unknown numbers | An unknown number at 12:20 PM, possibly a new customer |
| 3 – when you open | Calls that came in outside business hours | Two missed calls on Sunday: call back on Monday when you open |
Before you call back, check whether the same number has sent a WhatsApp message in the meantime or has already been called back by a colleague. That way nobody gets called twice about the same thing.
Choose your own target time
How quickly you call back is up to you. Choose a time that fits your business, your staffing and your customers, and that you can also meet on a busy day. Nobody takes a target that is never met seriously. For example:
- A salon or garage with someone at the front desk: within an hour during business hours.
- A small business where the owner does everything: the same day, before closing time.
- Calls after closing time or on the weekend: the next business day before 10:00 AM.
No answer? Two attempts and one message
First attempt
Call back within your target time. If you get voicemail, leave a short message saying who you are and when you will try again. Write the time and the result on the list.
Second attempt
Try again a few hours later, at a different time of day, for example late in the afternoon. Write this attempt down too.
One WhatsApp message
If that does not work either and the number uses WhatsApp, send one short message. A landline usually has no WhatsApp; in that case you stop at the two attempts.
Stop and close
After that you stop and write “not reached, closed” on the list. The customer knows you tried to help; the next move is theirs.
The callback scripts
Callback script: missed call
When you call a number back and do not know why the person called.
[Good morning/Good afternoon], this is [First name] with [Business name]. You called us today around [time], and we weren’t able to pick up. I’m sorry we missed your call.
How can I help you?
(Then follow the six steps: find out what it’s about, ask what you need, confirm, deal with it or pass it on, close.)
(If it’s already been taken care of, or the person called by mistake:) No problem at all. Thank you, and have a great day.
Voicemail on the first attempt
[Good morning/Good afternoon], this is [First name] with [Business name], returning your call from earlier today.
I’ll try you again [this afternoon around 4:00 PM]. You can also reach us at [phone number]. Thank you.
WhatsApp message after two attempts
One message, only if the number uses WhatsApp. After that you close the call.
[Good morning/Good afternoon], this is [First name] with [Business name].
You called us today. We tried to call you back twice but couldn’t reach you.
How can we help you? You can reply here or call us at [phone number], [business hours].
If you called by mistake, you don’t need to do anything.
Worked example
Example: Garage Amrit’s callback list (fictional)
Even with a lunch arrangement, calls get missed on a busy day. This is an excerpt from Shanti’s list on a Tuesday; the numbers and details are made up.
| Missed | Number and subject | Priority | Attempts | Outcome |
|---|---|---|---|---|
| 12:08 PM | 8xx-xx31, regular customer, car was due to be ready at 1:00 PM | 1 | 1:05 PM reached | Car ready at 3:00 PM, customer agrees |
| 12:14 PM | 7xx-xx56, unknown | 2 | 1:10 PM reached | Appointment for a service on Thursday at 8:00 AM |
| 12:31 PM | 8xx-xx02, unknown | 2 | 1:15 PM voicemail; 4:10 PM no answer; 4:15 PM WhatsApp message | Not reached, closed |
| 12:40 PM | 7xx-xx77, voicemail: “brakes are making a lot of noise” | 1 | 1:00 PM reached | Passed on to the shop manager, customer is coming in today |
| 12:52 PM | 8xx-xx19, unknown | 2 | 1:20 PM reached | Asked about tire prices, information given |
The call about the brakes was handled first, because it could be a safety issue. And the number that did not respond after two attempts and one message is marked as closed. Nobody has to wonder whether it is still open.
An escalation plan: who takes over what?
Not every request belongs with the person who picks up. An escalation plan sets out what everyone handles themselves and what goes to a colleague, the owner or emergency services. That way nobody has to hesitate in the moment.
| Type of request | Example | Who handles it | How quickly |
|---|---|---|---|
| Standard question | Business hours, address, fixed prices, what you do and do not do | Anyone who picks up | Right away, during the call |
| Appointment or booking | Booking a service, rescheduling an appointment | Anyone with access to the calendar | Right away, or call back within the target time |
| Complex request | A quote, a diagnosis, an exception to the price | Specialist or owner | Callback scheduled for a set time |
| Complaint | Work not done properly, a long wait, a bill that is not right | Manager or owner | Call back the same day |
| Urgent or safety | A car with brake problems, a leak, a skin reaction after a treatment at the salon | A person right away: [name], or otherwise [name] | Immediately, never through the callback list |
| Emergency | An accident, someone is injured or ill, fire | Emergency services | The caller calls the emergency number directly |
Three examples from the garage (fictional)
- Standard. “How late are you open on Saturday?” Shanti answers right away. Nothing needs to be written down.
- Complex. “My air conditioning is blowing warm air. What will that cost?” Shanti cannot estimate that. She writes down the name, number and the make and model of the car, and says, “Our mechanic will call you back before 4:00 PM to go over it with you.”
- Safety. “My brake pedal is going all the way to the floor.” Shanti says, “Please don’t drive any farther. Are you somewhere safe? I’ll put you right through to our shop manager.” She transfers the call or walks the phone over to the shop.
Complaint script
The goal is not to be proven right, but to listen, write things down and agree on a clear next step.
Thank you for letting us know. Take your time and tell me what happened.
(Listen without interrupting. Write down the main points.)
I understand how frustrating this is for you. Let me read back what I’ve written down: [summary]. Did I get that right?
What would be a good solution for you?
I want to make sure this gets resolved properly, so I’m passing it right along to [name/role]. They’ll call you back [today before 5:00 PM]. Is [number] the best number to reach you at?
Thank you again for letting us know.
Transferring a call
Tell your colleague first what it is about, so the caller does not have to tell their story again.
To the caller: I’m going to transfer you to [name], our [role]. One moment, please.
To the colleague: I have [caller’s name] on the line about [question in one sentence]. I’ve already told them [what you said or promised]. Can you help them now?
If the colleague is not free: [Name] isn’t available right now. Would you like me to have [him/her] call you back [before time]?
Lunch, busy times, closing time and weekends
Calls usually go unanswered at predictable moments. Your audit from Lesson 1 shows which moments those are for you. For each of them, you can set something up with simple means.
| Moment | What goes wrong | What you can arrange |
|---|---|---|
| Lunch | The person who normally picks up is on a break | Stagger the breaks, so there is always someone by the phone. Put on the schedule, for each day, who covers the phone during lunch. |
| Busy hours | Everyone is busy with customers | Pick up briefly using the script for busy times and put the call on the callback list. A short promise is better than not picking up. |
| Closing time | Missed calls from the afternoon are forgotten | Go through the list fifteen minutes before closing. Anything still open carries over to the next morning with the handoff. |
| Weekends and holidays | The business is closed, but customers call anyway | A voicemail greeting with your business hours, and a designated person who works through the list first thing when you open. |
Forwarding calls to another phone
Some phone providers offer the option of forwarding calls to another number, for example the cell phone of the colleague on duty. Whether that is possible for you, how to set it up and what it costs varies by provider and by plan. So do not assume it; check with your phone provider.
If you forward calls, agree on who has the phone the calls go to, until what time, and that this person also puts missed calls on the callback list. Otherwise you only move the problem to another phone.
Voicemail or away message
If your phone or line has voicemail. Keep it short: the caller mainly wants to know when they can reach you.
Hello, you’ve reached [Business name]. We can’t take your call right now.
Our business hours are [days and times].
Please leave your name and number, and we’ll call you back [the next business day before 10:00 AM].
You can also send us a WhatsApp message at [number].
(If your business may involve health or safety:) In an emergency, please call [emergency number] right away.
Privacy and recording calls
The callback list contains names and phone numbers. That is personal data. Handle it with care, even if it is only a sheet of paper.
- Write down only what you need to call back: name, number and a few words about the request.
- Do not write medical details, payment details or other sensitive information on the list.
- Do not leave the list lying open on the counter where customers can read it. Share a spreadsheet only with colleagues who make callbacks.
- Shred or delete old lists after a fixed period, for example after a month. Choose a period yourself and stick to it.
How to put it in place, step by step
You now have all the parts. In this order, the process is in place within a week, without extra software.
See when calls go unanswered
Look in your audit from Lesson 1 to see at which times most calls go unanswered. Haven’t done an audit? Then for one week, count the missed calls on your phone every evening, by time of day.
Fill in the basic details
Download the document below. At the top, fill in your business hours and target times, and who calls back on each shift, who handles complaints and who decides in urgent cases. Look up the correct emergency number.
Adapt the scripts
Read each script aloud and replace words that do not fit your business. Keep the order: greeting, question, details, confirm, next step, close.
Set up the callback list
Print the list, or create a tab in your spreadsheet with the same columns. Keep it in a fixed place next to the phone, out of sight of customers.
Arrange lunch, busy times and closing time
Put on the schedule who covers the phone during lunch and who goes through the list before closing time. If you want to forward calls, ask your phone provider whether that is possible.
Train the team
Do the 15-minute exercise from the next section with everyone who answers the phone.
Work with it for a week and look back
After a week, go through the callback list together: did you meet the target time, which questions kept coming up, where did things get stuck? Adjust the scripts or the schedule accordingly.
Phone scripts and callback process
Greeting, asking questions, calling back, complaints and transferring: ready-made scripts, a decision tree for escalations, a callback list and a handoff checklist.
Worked example
Example: a one-page instruction sheet (fictional)
This is what the instruction sheet of Garage Amrit (fictional) could look like after Shanti and the owner have gone through the steps above. Replace the names and times with your own.
| Topic | What we agreed |
|---|---|
| Goal | Every caller gets an answer or a clear next step. No missed call is left without an owner. |
| Who picks up | Shanti at the front desk. During her lunch (noon to 12:45 PM), Ravi covers the phone; then Ravi goes to lunch (12:45 PM to 1:30 PM). |
| Responsible for callbacks | Whoever has the phone. Check times: every hour on the hour, after lunch and at 4:15 PM. |
| Target time | Missed during business hours: call back within an hour. Missed after closing time: the next business day before 9:00 AM. |
| Not reached | Two attempts at different times, then one WhatsApp message. Then close it on the list. |
| Escalation | Brakes, steering problems or smoke: straight to shop manager Dennis. Complaints: to the owner, call back the same day. Injuries or fire: have the caller call the emergency number right away. |
| Closing time (4:30 PM) | Go through the list at 4:15 PM. Open items carry over to the next morning with the handoff. |
| Privacy | The list is kept in the front desk drawer. Old lists are shredded after a month. |
Team training: a 15-minute role-play
A script only works once the team has said it out loud a few times. Plan a short exercise, for example before opening or during a quiet hour. You need: the printed document, two chairs back to back (so you cannot see each other, just like on the phone) and three people: a caller, a staff member and an observer.
| Time | What |
|---|---|
| 2 minutes | Explanation: the six steps of the call and the escalation plan |
| 3 × 3 minutes | Play three scenarios, each with a minute of feedback from the observer. Switch roles after each scenario. |
| 3 minutes | Debrief: what went well, what do we change in the scripts? |
| 1 minute | Next steps: who changes what, and when do we practice again? |
The three scenarios
An appointment at a busy moment
A customer calls a salon (fictional) in Zorg en Hoop for an appointment while the staff member has someone in the chair. Goal: use the script for busy times, write down the name and number and give a callback time you can keep.
An angry customer
A customer calls the garage: his car was supposed to be ready yesterday and nobody called him. Goal: let him finish, sum up, do not get into an argument and pass it on to the owner with a specific callback time.
Safety
A caller is on the road and says his brake pedal is sinking a long way down. Goal: recognize that this does not belong on the callback list, ask the caller not to drive any farther and to find a safe place, and get a specialist involved right away. Variation: there has been a collision and someone is injured. Then the only right answer is: call the emergency number right away.
What the observer watches for
- Did the staff member say the business name and their own name?
- Did the staff member let the caller finish?
- Were the name and number written down and repeated back?
- Was the next step clear, with a time attached?
- Was the right route from the escalation plan chosen?
- Did the tone stay friendly and calm, even with the angry customer?
Checklist
- ☐ I have assigned one person to handle callbacks on each shift and put that name on the schedule.
- ☐ We have agreed on fixed check times for missed calls.
- ☐ I have chosen our own target time for callbacks, one we can also meet on busy days.
- ☐ The scripts have been adapted to our business and read aloud.
- ☐ The escalation plan has been filled in with names, phone numbers and the correct emergency number.
- ☐ The callback list is kept in a fixed place next to the phone, or in a shared spreadsheet.
- ☐ I have arranged who has the phone during lunch, during busy hours and at closing time.
- ☐ If I want to forward calls: I have asked my phone provider whether and how that is possible.
- ☐ The team has done the 15-minute exercise.
- ☐ A time to go through the callback list together after one week is on the calendar.
Lesson 3
Set up WhatsApp Business professionally
You set up the free WhatsApp Business app so that customers see a complete profile, get an honest automatic message and then quickly reach a person. You create quick replies for the questions that keep coming back, five labels that show what is still open, and clear agreements on who answers when.
Why WhatsApp messages get left unanswered
Customers message your business with questions like: how much is this, are you open today, is it still available, can I book? Because a messaging app feels informal, replying often happens in between other work, without clear agreements. What goes wrong then is almost always the same:
- Messages arrive on the owner’s personal phone or on a single phone behind the counter, in between personal chats.
- Someone opens a chat but doesn’t reply right away. An hour later the conversation is twenty chats further down.
- Two colleagues give the same customer a different answer about a price or a delivery time.
- At the end of the day nobody knows for sure which customers are still waiting for a reply.
In this lesson you use the free WhatsApp Business app to build a way of working that prevents this, in five steps: profile, automatic messages, quick replies, labels and clear agreements on who answers. After that you read what is and isn’t allowed, and when working by hand starts to fall short.
Worked example
Example: Lunchroom ’t Erf (fictional)
Lunchroom ’t Erf in the center of Paramaribo sells lunch, sandwiches and small-scale catering. Owner Rachel answers WhatsApp on her own phone. The questions are mostly about prices, whether something is still available today, whether there is room for a group, and where an order is. Between 11:30 AM and 1:30 PM Rachel has no time to message. Some customers only get a reply in the evening, others never.
We follow ’t Erf through this lesson. All names, times and amounts are fictional example data.
Step 1: Complete your business profile
Your profile is the first thing a customer sees when they tap your name. A complete profile already answers the simplest questions: where you are, when you are open and what you do. The app also uses those details for a few standard quick replies, such as your business hours and address.
Open your business profile
Via Settings → your business name, or via Business tools → Business profile. You edit each field with the pencil icon.
Use your real business name
The name on your storefront or receipt, without advertising or search words such as “Cheapest lunch in Paramaribo.” WhatsApp’s policy prohibits misleading customers or passing yourself off as another business.
Add a recognizable profile photo
Your logo or a clear photo of your building, so the customer can see right away that they have reached the right business.
Choose a category and write a description
Pick the category from the list that fits best, for example Restaurant. Write two or three sentences: what you do, who you serve, and how customers order or book.
Fill in your address and business hours
Put your address on the map and choose set hours for each day, always open, or by appointment only. Enter what is actually true: the away message can use those hours later.
Fill in email and website only if someone keeps them up to date
An email address that nobody reads is worse than no email address.
Consider a catalog
You can put standard products or services in the catalog with a photo, a description and, if you like, a price. If you do, keep it up to date.
| Field | Lunchroom ’t Erf (fictional) |
|---|---|
| Name | Lunchroom ’t Erf |
| Category | Restaurant |
| Description | Lunch, sandwiches and small-scale catering in the center of Paramaribo. You can order and book at this number. Pickup at the counter. |
| Address | [Street and number], Paramaribo |
| Business hours | Monday through Saturday 7:30 AM to 4:00 PM, closed Sunday |
| Email and website | Left blank: nobody keeps them up to date |
Step 2: Set up a greeting message and an away message
The app can send two messages automatically. They only help if they are honest about what happens next.
| Message | When it is sent | What it is for |
|---|---|---|
| Greeting message | With a new customer’s first message, or when someone has not sent anything for 14 days | Letting the customer know the message has arrived and what happens now |
| Away message | On a schedule you choose: always, at times you set, or outside your business hours | Letting the customer know you are not available right now and when they can expect a reply |
For both, you choose who gets them: everyone, only people not in your address book, or everyone except contacts you exclude. They only work when the phone is connected to the internet: if the phone is off at night, nothing goes out.
An automatic reply is not the same as help
An automatic message confirms receipt; it is not an answer. So always say that it is automatic, when a staff member will reply (with times you can stick to), what the customer can send in the meantime, and how they can reach you for urgent matters, for example by calling during business hours.
Greeting message
Set up under Business tools → Greeting message. Replace everything in brackets.
Welcome to [Business name]! This is an automated message: we’ve received your message.
During business hours ([days and times]), a team member will reply within [your target time].
Would you like to order or book? Please send us your name, the date and the number of people or items now.
Away message
Set up under Business tools → Away message, with “Outside of business hours” as the schedule.
Thanks for messaging [Business name]. This is an automated message: we’re closed right now.
Our hours are [days and times]. We answer messages sent after closing time before [time] on the next business day.
Would you like to order something? Send us what you’d like and when you need it. Your order is final only once a team member has confirmed it.
At ’t Erf (fictional), the away message promises a reply before 9:00 AM on the next business day. That is doable: staff member Kevin starts at 7:30 AM and goes through the evening’s messages first.
Step 3: Create quick replies for the questions that keep coming back
Quick replies (you find them in the app under that same name) are messages you save once and then send with a few taps. Each reply gets a short shortcut. If you type a forward slash / in a chat, you see your saved replies; if you keep typing, for example /prices, you quickly find the right one. You can save up to 50.
Which quick replies you need
Choose them based on the questions you actually get. If you did the customer contact audit from Lesson 1, take the five to ten topics that come up most often. Didn’t do an audit? Scroll through the chats from the last two weeks and tally which questions keep coming up.
How to write a good quick reply
- Short: three to five lines. The customer is reading on a phone.
- End with a question, so the conversation doesn’t stall.
- Put what differs per customer in [brackets] and always fill it in before you send.
- Don’t write prices that change into the text; fill them in each time.
- Adjust the tone, so it sounds the way your team talks.
Open Quick replies
Go to Business tools (or the Tools tab) → Quick replies and tap the plus button.
Paste the text and choose a shortcut
Leave the [brackets] in as a reminder. As the shortcut, choose one short word that everyone remembers, such as prices or complaint.
Test and share
Send the reply to a colleague first to see how it comes across. Post the list of shortcuts at the front desk.
Eight quick replies to start with
These are examples for a business like ’t Erf; adapt them to your own business. The download has more, and also comes as a text file to copy from.
/prices — a question about a price
When someone asks what something costs.
Thanks for your question! [Product or service] costs SRD [amount].
[What is or isn’t included, for example delivery or a drink.]
Would you like me to get it ready or reserve it for you?
/hours — business hours
When someone asks when you are open.
We’re open [days] from [time] to [time].
Our hours may be different on holidays; we’ll let you know ahead of time.
Is there anything we can help you with?
/available — availability or stock
When someone asks whether something is still available or when there is room.
Thanks for checking with us. [Product or service] is [still available today / sold out right now / available again on date].
We can hold it for you until [time].
Would you like me to put it under your name?
/book — request a reservation or appointment
When someone wants to make a reservation or an appointment.
We’d be glad to set up a reservation for you! Could I get a few details?
1. Your name
2. The date and time
3. The number of people [or: which service it is for]
Then I’ll let you know if we can fit you in. The reservation isn’t final until you get our confirmation.
/order — a question about an order
When someone asks where an order is or wants to change something.
Thanks for your message. I’ll look up your order for you.
Could I get your name and the day you placed the order?
I’ll get back to you within [time] with an update.
/complaint — complaint received
When someone is unhappy. The chat then goes to whoever handles complaints.
Thank you for letting us know. We’re sorry it didn’t go well.
I’ve passed your message on to [name or role], who will handle this personally.
You’ll hear from us by [day and time] at the latest. Would you prefer a call, or should we continue here on WhatsApp?
/closed — message outside business hours
When you or a colleague sees a message after closing time and can’t handle it right away.
Thanks for your message! We’re closed right now.
We’ll get back to you [tomorrow] starting at [time]; we’ve made a note of your question.
Would you like to send [details needed] in the meantime? That way we can get started right away.
/followup — following up on an open question
When a customer hasn’t responded to your question or proposal.
Hi [name], I’m following up on your question from [day] about [subject].
[The proposal or open question in one sentence.]
Should we go ahead and confirm, or do you have another question? And just let us know if you no longer need it.
WhatsApp Business: quick replies and labels
Ready-to-copy quick replies, a set of labels, agreements on who answers what and an escalation policy for messages.
Step 4: Use labels to see what is still open
With labels you give a chat a colored tag, and you can view all chats with the same label in one list. That turns your chat list into a to-do list: you can see at a glance which customers still need something from you.
Use these five labels. Every chat with an open customer question has exactly one.
| Label | Means | Whose turn it is | When it comes off |
|---|---|---|---|
| New request | A question has come in that nobody has answered yet | The person on message duty | As soon as someone picks up the question and replies |
| Waiting for information | You have asked the customer something and are waiting for a reply | The customer; you follow up if it takes too long | When the customer replies, or after your follow-up |
| Action needed | You need to do something: find out a price, check something, call back | The colleague who picks it up | When it is done and the customer has an answer |
| Appointment confirmed | A reservation, appointment or order is set and still has to happen | Nobody until the day itself; it is also in the calendar | After the appointment or delivery |
| Resolved | The customer has what they needed | Nobody | Stays on; clean up the list now and then |
Five labels for WhatsApp chats
Step 1: New request
Not answered yet
Step 2: Waiting for information
The customer still has to let you know something
Step 3: Action needed
Someone on the team has to do something
Step 4: Appointment confirmed
Date and time are fixed
Step 5: Resolved
Question answered, nothing left open
Create the five labels
Via Business tools (or Tools) → Labels or Lists. Rename or delete default labels you don’t use. Give each label a fixed color, for example red for Action needed.
Label every new question right away
Press and hold the chat and choose the label as soon as you open the chat, even if you can’t reply yet.
Change the label when the status changes
Remove the old label and add the new one. Two status labels at once make the list unreliable.
Work from the label lists
Start every shift with New request and Action needed, not with the top of your chat list.
Want to remember something about a regular customer, such as “always picks up at noon”? Use the notes on the contact; customers can’t see them. Don’t put health or payment details in them.
Worked example
Example: one reservation at ’t Erf (fictional)
- Tuesday, 10:12 AM. A customer messages: “Do you have room for eight people on Saturday?” Kevin labels the chat New request and sends
/book. - 10:15 AM. Kevin changes the label to Waiting for information: he is waiting for the time and a name.
- 10:40 AM. The customer replies: Saturday at 12:30 PM, under the name Anand (example). The label becomes Action needed: Kevin asks Rachel whether the big table is free.
- 11:05 AM. Rachel says yes. Kevin sends the confirmation, puts the reservation in the calendar and labels the chat Appointment confirmed.
- Saturday, 2:00 PM. The group has come and gone. The label becomes Resolved.
Everyone could see at any moment where this conversation stood, without reading the chat.
Step 5: Agree on who answers and how quickly, and close out the day
Labels and quick replies only work if someone is responsible. Without an agreement, everyone thinks someone else is already doing it.
One person responsible for each part of the day
For each part of the day, appoint one person to be on message duty. They don’t have to solve everything themselves, but they make sure every new question gets a label and a first reply, and that chats marked Action needed reach the right colleague. Also appoint a backup for breaks and busy times.
| Part of the day | Message duty | Backup | Note |
|---|---|---|---|
| 7:30 AM to 11:30 AM | Kevin | Rachel | Answer the evening’s messages before 9:00 AM; confirm lunch orders |
| 11:30 AM to 1:30 PM | Sharda | Kevin | Busiest hours: only a label and a first reply, details after 1:30 PM |
| 1:30 PM to 4:00 PM | Kevin | Sharda | Follow up on Waiting for information; catering for tomorrow |
| 4:00 PM | Rachel | Kevin | End-of-day check (see below) |
Your own target time
Agree on how quickly a customer gets a first real reply. You choose this yourself, based on what you and your team can keep up with; there is no fixed standard. For example, a business could agree on this:
- During business hours: a first reply within 30 minutes, or within an hour at the busiest times.
- Messages sent after closing time: answered before 9:00 AM on the next business day.
- Complaints: a response from the owner or manager the same day.
Put the time you choose in your greeting message and away message. Then the customer knows what to expect, and your team knows where the bar is. In Lesson 5 you measure whether you meet that time.
Several devices, one account
You can also use the account on linked devices, such as a computer with WhatsApp Web or a colleague’s phone; at the time of writing, WhatsApp mentions up to four in addition to the main phone. Keep using the main phone, or the linked devices will be logged out after a while. Everyone sees the same chats, and don’t count on being able to see which colleague sent a message. So agree on the following:
- Whoever picks up a chat finishes it or explicitly hands it over. Others stay out of it.
- End every message with your first name, for example “Best, Kevin.” That way the customer sees that a person is replying, and colleagues see who is handling the conversation.
- When an employee leaves, unlink their device the same day.
The end-of-day check: ten minutes
At the end of every business day, one designated person goes through the messages:
Open the New request list
Every chat here gets a first reply now, if necessary
/closedwith the time you will get back to them.Look for chats without a label
Go through today’s chats and unread messages. Every customer question without a label still gets one.
Go through Action needed
For each chat: who is doing it, and when? Whatever can’t be done today, write down for tomorrow morning, with a name next to it.
Look at Waiting for information
Have you been waiting longer than agreed, for example two days? Send
/followup, or move the chat to Resolved if the conversation is finished.Check tomorrow and tonight
Are tomorrow’s confirmed appointments in the calendar? Will the away message turn on, and is the phone charged and connected?
Write a one-line handoff
In a designated notebook or shared note: what needs to happen first tomorrow, and by whom?
Consent, privacy and WhatsApp’s rules
WhatsApp is personal. Customers only appreciate messages from a business if they are relevant and if they asked for them. WhatsApp’s Business Policy, which also applies to the app, is clear about this. The main points, in plain language:
- Only with consent. Only message someone on your own initiative if they have given you their number and have also said they want to receive messages from you. You can of course reply to anyone who asks you a question. A number on a receipt is not consent for advertising.
- No unsolicited mass messages. Don’t send offers to your whole address book, don’t buy lists of numbers and don’t add customers to a group without asking: everyone in it can see each other’s numbers.
- Stop means stop. If someone asks for no more messages, respect that immediately and note it down, even if they say it on the phone or at the counter.
- No card numbers. Never ask for a full debit card or credit card number over WhatsApp; WhatsApp’s policy prohibits it. If a customer sends one anyway, have the message deleted on both sides and offer another way to pay.
- Go easy on sensitive data. Don’t ask for copies of ID, medical details or passwords unless it is really necessary.
- Always a way to a person. If you use automatic messages, the policy says the customer must be able to reach a person quickly: in the chat, by phone or in person.
- Not everything is allowed on WhatsApp. For some products, such as alcohol, tobacco and medicines, the policy sets restrictions. If you sell something like that, read what is allowed first.
Secure the phone too: a screen lock, two-step verification in WhatsApp (under Settings → Account) and regular backups.
When working by hand starts to fall short
With this way of working, a small business can go a long way. Still, at some point it can become difficult. Watch for these signs:
- Several colleagues reply from linked devices and, despite the labels, don’t know who is doing what.
- At busy times more messages come in than the person on message duty can keep up with, and the New request list grows.
- Many messages come in during the evening or on the weekend, and every morning starts with a backlog.
- The team sends the same quick replies to the same questions all day long.
- The labels are no longer updated, so the end-of-day check no longer tells you anything.
What you can do then, from simple to far-reaching:
- Divide the work more clearly. More hours of message duty in the busy parts of the day, or one colleague who only handles WhatsApp during the peak.
- Answer questions before they are asked. Make prices, business hours and what is available today clearer in your profile, catalog, status or on your Facebook page.
- Look at software. There are services that work with the WhatsApp Business Platform, for example with a shared inbox in which you assign chats to colleagues, or with an assistant that answers routine questions. These have different terms and costs from the free app. Take your time comparing them, and keep your labels, target time and end-of-day check if you switch.
Your own numbers show best which step suits you. In Lesson 5 you count each week how many requests come in and how many are answered within your target time.
Checklist
- ☐ Business profile fully completed: name, photo, category, description, address and business hours
- ☐ Greeting message set up that says it is automatic and when a person will reply
- ☐ Away message set up for outside business hours, without promising round-the-clock service
- ☐ At least eight quick replies saved, with shortcuts the whole team knows
- ☐ The five labels (or lists) created and all open customer chats labeled
- ☐ Message schedule made: one person responsible and one backup for each part of the day
- ☐ Your own target time for a first reply chosen and discussed with the team
- ☐ Ten-minute end-of-day check scheduled, with a designated person
- ☐ Agreements on consent, mass messages and sensitive data discussed with the team
- ☐ Screen lock and two-step verification turned on for the business phone
Lesson 4
Build an appointments and follow-up system
You set up one shared list that holds every appointment request, with its status, the person responsible and a follow-up date. You get messages for confirming, rescheduling, canceling, reminding and following up, and a daily routine of ten minutes.
Where appointments fall through the cracks
On Monday a customer sends a WhatsApp message: “Can I bring my car in for service on Thursday?” A colleague replies, “Let me check,” and then nothing happens. Or two colleagues book the same time slot: one on the phone, the other at the front desk. On Thursday there are two cars waiting for one lift.
This is rarely due to unwillingness. It comes from having no single place where everything is recorded, and no fixed agreements about who does what. In this lesson you build a simple system with three parts:
- One place where every appointment request ends up: a shared spreadsheet, a shared calendar, or both with a clear division of tasks.
- Fixed steps for every request: check availability, confirm, send a reminder if the customer wants one, and follow up.
- Fixed people responsible: every open request shows who is handling it and when it will be looked at again.
From message to booked appointment
Step 1: Request
What, when and for whom
Step 2: Check availability
In the shared calendar or list
Step 3: Confirm
Date, time and place in writing
Step 4: Remind
Only with permission, once
Step 5: Follow up
After the appointment or if there is no reply
In lesson 2 you created a callback process and in lesson 3 you set up WhatsApp Business. Appointment requests from those channels now go into one list, as do those from customers who walk in. You do not need to buy anything: a spreadsheet and the calendar you already use are enough.
Choose one place and record only what you need
The most important decision in this lesson: where does the truth live? If an appointment can be in two places, sooner or later it goes wrong. So choose one fixed place for each kind of information, and tell the whole team which one it is.
| Your situation | Calendar | Spreadsheet |
|---|---|---|
| You already use a calendar (paper planner, Google Calendar, Outlook or booking software) | The only place for confirmed times | Requests that are not settled yet, and follow-up |
| You do not have a fixed calendar yet | Not needed to start with | One list for everything, including confirmed appointments |
| Several staff members, chairs, lifts or tables | One calendar per staff member or place, shared | What is still open and who picks it up |
A workable combination: the calendar shows when something is scheduled, the list shows what still needs to happen. A confirmed time always goes into the calendar first and only then into the list. If you work with the list alone, the Confirmed time column is your calendar.
What to record for each request, at a minimum
For each request, record no more than you need to make the appointment and keep it. This is enough:
| Detail | Why | Example |
|---|---|---|
| Name | So you recognize the customer when they arrive | Rina |
| Contact, only if needed | To confirm or reschedule; not needed if the customer at the front desk is taken care of right away | +597 7xx xxxx |
| Service requested | Determines how long it takes and who does it | Cut and blow-dry |
| Requested time | What the customer wanted, even if it was not possible | Friday around 4:00 PM |
| Confirmed time | What you agreed to | Saturday at 10:00 AM |
| Status | Where the request stands now | Confirmed |
| Responsible | Who handles it | Priya |
| Follow-up date | When someone looks at it again | 10/16/2026 |
| Consent to contact | Whether you may send a reminder or follow-up message | Yes |
Setting up the list in Google Sheets or Excel
You can download the ready-made list; the columns, drop-down lists and the count are already in it. If you would rather build it yourself, or want to understand how it works, follow the steps below.
Appointments and follow-up list (spreadsheet)
Every request, appointment and follow-up in one place, with status, person responsible and follow-up date. The overview counts what needs following up today or earlier.
Open or create the list
Google Sheets: on sheets.google.com choose a blank spreadsheet, or upload the downloaded .xlsx file to Google Drive and open it with Google Sheets. Excel: open the file or create a new workbook. Give it a clear name, such as “Appointments and follow-up [Business name].”
Put the columns in row 1
In row 1, from column A to M, type: Request date, Source, Customer, Contact, Service / question, Requested time, Confirmed time, Status, Responsible, Follow-up date, Consent to contact?, Next action, Notes.
Freeze the header row
That keeps the headings visible when you scroll. Google Sheets: View → Freeze → 1 row. Excel: View → Freeze Panes → Freeze Top Row.
Create a drop-down list for Status
Select column H from row 2 down. Google Sheets: Data → Data validation → Add rule → Dropdown. Excel: Data → Data Validation → Allow: List, with the options separated by commas (or semicolons, depending on your settings). The options: New, Waiting for customer, Confirmed, Rescheduled, Canceled, No-show, Completed.
Create drop-down lists for Source and Consent to contact
Source (column B): Phone, WhatsApp, Website/email, Walk-in, Other. Consent to contact (column K): Yes, No. Then nobody types “whatsap” or “yeah sure,” and filters and counts stay correct.
Make sure dates are real dates
Always type dates in columns A and J the same way: month, day, year, as in 10/16/2026 for October 16. A date the program recognizes is right-aligned in the cell by default. Only then do sorting and counting by date work.
Turn on a filter
Google Sheets: Data → Create a filter. Excel: Data → Filter. Sort the Follow-up date column in ascending order, so the oldest date is at the top. Under Status, uncheck Completed and Canceled, and you see only what is still open.
Count what needs following up today
On a second tab (for example, Overview), enter the formula below. It counts the open rows with a follow-up date of today or earlier. In the download this count is already set up.
Share the list only with those who need it
Google Sheets: Share → add your colleagues' email addresses → Editor for those who update the list, Viewer for those who only look. Leave General access set to Restricted, not “Anyone with the link.” Excel: save the file in OneDrive or SharePoint and share it with specific people. Remove someone's access as soon as they leave.
Follow-ups due today or earlier
=COUNTIFS(J2:J1000,"<="&TODAY(),H2:H1000,"<>Completed",H2:H1000,"<>Canceled")
This is the version for Google Sheets and English-language Excel. In Dutch-language Excel the names are AANTALLEN.ALS and VANDAAG(). If your program uses semicolons between the parts, replace each comma with a semicolon. If the formula is on a different tab from the list, put the tab name in front, for example Appointments!J2:J1000.
What each status means
| Status | Meaning | What happens next |
|---|---|---|
| New | Request received, not answered yet | Check availability and respond, preferably the same day |
| Waiting for customer | You have proposed a time or asked something; the customer needs to respond | Set a follow-up date; check back once if that was agreed |
| Confirmed | The time is in the calendar and the customer has a confirmation | Send a reminder, but only if Consent to contact is set to Yes |
| Rescheduled | The appointment needs to move to another time, but that time is not settled yet | Release the old time; as soon as there is a new time: Confirmed, with the new time |
| Canceled | The appointment is not going ahead | Acknowledge the message, release the time, clear the follow-up date |
| No-show | The customer did not come and did not let you know | One friendly message, in line with your own policy |
| Completed | The appointment has taken place, or the request is closed | Nothing more; clear the follow-up date |
Booking and confirming without double bookings
Double bookings nearly always happen the same way: someone says yes before checking, or checks an overview that has not been updated. Three habits prevent most of them:
- Check first, then commit. Never confirm a time from memory. Look in the calendar, even if you think the slot is free.
- Record first, then confirm. Put the appointment in the calendar before you send the customer the confirmation. Then a colleague can no longer give that time away.
- Know your capacity. A time slot is not just a time, but also a table, a mechanic with a lift or a chair with a staff member. Allow for the length of the service, plus some slack in between.
“Let me check” is a perfectly good answer, as long as there is a follow-up. Set the request to New with a follow-up date of today, and tell the customer when they will get an answer.
| Business | What determines whether it fits | Ask this when the request comes in |
|---|---|---|
| Restaurant: reservation | Number of people, table layout, how busy the kitchen is | How many people? Which day and time? Inside or outside? Anything special, such as a high chair? |
| Garage: scheduling a service appointment | Type of job and how long it takes, a free mechanic and lift, parts in stock | Make, model and year? What is the problem? Does the car need to stay all day? |
| Salon: appointment | Treatment and how long it takes, which staff member | Which treatment? A preference for a staff member? First time with us? |
| Clinic or practice: appointment | Type of appointment and how long it takes, which doctor or practitioner | Only the type of appointment (for example, consultation or checkup) and whether it is a new patient |
Checklist: booking and confirming
- The service and how long it takes are clear, and you know who will do it.
- The time has been checked in the calendar, including the table, lift, chair or practitioner.
- The appointment is in the calendar before the customer gets the confirmation.
- The row in the list is updated: confirmed time, status Confirmed, person responsible.
- The confirmation states the day, date, time and address, what the customer needs to bring and how they can reschedule or cancel.
- You have asked whether you may send one reminder, and the answer is recorded under Consent to contact.
- When in doubt (a large group, an unknown duration, a special request), consult first and only then confirm.
Confirming an appointment
Send this right after the appointment is in the calendar. In WhatsApp Business you can save it as a quick reply.
[Good morning/Good afternoon] [Name], we are confirming your appointment at [Business name].
What: [service]
When: [day], [date] at [time]
Where: [address, with a landmark if helpful]
Bring: [what the customer needs to bring, or leave this line out]
Can't make it after all? Let us know as early as possible at this number and we will find another time together.
May we send you one reminder the day before? If so, reply YES.
See you on [day]! [Your name], [Business name]
Rescheduling, canceling and no-shows
Appointments change, and that is normal. Above all, the system must make sure that a freed-up time really does become available, and that the customer knows where they stand.
Rescheduling
- Set the status to Rescheduled and note the old time under Notes.
- Release the old time in the calendar right away.
- Suggest two specific times instead of asking “What time works for you?” That saves messages going back and forth.
- If the customer chooses one: new time in the calendar, status Confirmed, fill in the new confirmed time and send a new confirmation.
- No response: set a follow-up date and check back once. If you still hear nothing, close the row as Completed with a “no response” note.
Rescheduling at the customer's request
[Good morning/Good afternoon] [Name], you would like to move your appointment on [day] at [time]. No problem.
We still have space on [day] at [time] or on [day] at [time]. Which works better for you?
As soon as you choose, we will send a new confirmation. The old appointment no longer applies.
When you have to reschedule yourself
For example, when a part has not arrived or a staff member is sick. Let the customer know as early as possible.
[Good morning/Good afternoon] [Name], we are sorry, but we have to move your appointment on [day] at [time] because [short reason].
We can see you on [day] at [time] or on [day] at [time]. Which works for you?
We apologize for the inconvenience. [Your name], [Business name]
Canceling
With a cancellation, three things matter: the customer gets confirmation that their message has arrived, the time becomes free in the calendar, and the row is closed with status Canceled and an empty follow-up date. Do not press for the reason if the customer does not give it themselves.
Confirming a cancellation
Thank you for letting us know, [Name]. Your appointment on [day], [date] at [time] has been canceled.
Would you like to make a new appointment later? Feel free to send us a message or call [phone number].
Have a nice day! [Business name]
No-shows
A customer who does not show up costs you a time slot. Even so, an angry response rarely helps: often something came up, or the appointment was not clear enough. Start in a friendly way and offer a new appointment.
Decide your own policy in advance and mention it when booking, not afterward. What fits depends on your business. Examples of choices businesses make:
- After the first time: only a friendly message offering a new appointment.
- After a second time: ask the customer to confirm the day before that they are coming.
- For long treatments or jobs: ask for a deposit in advance, in a safe way and without payment details in the list.
- At a restaurant: release a table after a fixed waiting time, if you said so when taking the reservation.
Under Notes, record factually how often it has happened (for example, “first no-show”), worded so that you could let the customer read it.
Message after a no-show
Send this the same day or the next morning. One message is enough.
[Good afternoon] [Name], we were expecting you today at [time] for [service]. Sorry it did not work out; we hope all is well with you.
Would you like to make a new appointment? We have space on [day] at [time] or on [day] at [time].
[Only if this is your policy:] If you cannot come next time, please let us know [number] hours in advance. Then we can give the time to another customer.
Best regards, [Your name], [Business name]
Reminding and following up, only with consent
A reminder helps a customer who is busy. Three reminders feel pushy. So work with three rules:
- Only with consent. When confirming, ask whether you may send a reminder and record the answer under Consent to contact. If it says No or nothing at all, you do not send a reminder.
- One reminder. Usually the day before, or on the last business day before if you are closed on the weekend. Not again every day.
- An easy way out. In every follow-up message, say how the customer can let you know they do not want any more messages, and stick to it. Then set Consent to contact to No right away.
Reminder (only with consent)
[Good morning/Good afternoon] [Name], a quick reminder of your appointment at [Business name] tomorrow, [day] at [time], for [service].
If it no longer works for you, just let us know and we will find another time.
Would you rather not receive any more reminders from us? Then reply STOP.
Following up after a request
Not every request turns into an appointment right away. Someone asks about the price, wants to talk it over at home or first needs to see their schedule. Without follow-up you often hear nothing more. With one short, agreed follow-up you usually get an answer, or at least you know it is not going to happen.
Worked example
Example: following up within 24 to 48 hours (fictional)
On Monday afternoon Natasha asks a salon in Zorg en Hoop on WhatsApp what a color treatment costs and how long it takes. Priya sends the price and the duration. Natasha replies, “I need to check when I'm free.”
Priya writes back, “Sounds good. May I send you a quick message on Wednesday to see whether it works out?” Natasha replies with a thumbs-up.
- In the list: status Waiting for customer, follow-up date Wednesday, Consent to contact Yes and “check back once” as the next action.
- On Wednesday the row is at the top of the filter. Priya sends one message with two possible times.
- If Natasha picks a time: status Confirmed. If she does not respond: on Friday, status Completed with a “no response” note. No second or third message.
If Natasha had not given consent, Priya would have left it at the price quote. The customer knows where to find you.
Follow-up after a request (only if agreed)
[Good morning/Good afternoon] [Name], as agreed, I am sending you a quick message about [subject, for example the color treatment].
Do you have any questions, or should I book a time for you? We have space on [day] at [time] or on [day] at [time].
Would you rather not receive any more messages from us? Just let us know and we will stop.
When a request is unusual: pass it to a person
A standard way of working works for ordinary appointments. Some requests do not fit it. Decide in advance which ones those are and who decides in that case, so nobody has to guess. Examples:
- A large group, a private party or a reservation outside business hours.
- A job nobody knows the length of, such as a fault that first needs to be investigated.
- A special request: a treatment you rarely do, or a question about a price agreement.
- A complaint, or a customer who is angry about an earlier appointment.
- Any question about health, medication or an urgent situation. Front desk staff do not give advice on that; the question goes to the doctor or practitioner. In an emergency, refer the person to the emergency room or the emergency number.
The approach is always the same: say honestly that you will check, say when the customer will get an answer, and put the request in the list with the decision-maker as the person responsible and a follow-up date of today or tomorrow.
When you do not know the answer
I want to check that properly for you, so I don't tell you anything wrong.
[Name of colleague or owner] deals with this. He or she will let you know what is possible before [time or day].
May I call you or send you a message at this number about it?
The daily routine and who does what
A list only works if someone looks at it every day. Plan a fixed ten-minute slot for it, for example right after opening or at the end of the afternoon. The time matters less than the regularity.
Look at the count (1 minute)
How many follow-ups are due today or earlier? At the end of the routine that number is zero, or every open row has been given a new follow-up date.
Handle new requests (3 minutes)
Filter by status New. Check availability, propose a time or confirm, and update the row.
Send reminders for tomorrow (2 minutes)
Find tomorrow's confirmed appointments with Consent to contact set to Yes. Send each customer one reminder and note under Next action that it has been done.
Wrap up yesterday (2 minutes)
Set yesterday's appointments to Completed or No-show and clear the follow-up date where nothing more needs to happen. For a no-show, send the friendly message.
Check the open rows (2 minutes)
Does every open row have a person responsible and a follow-up date? Fill in what is missing. Anything you cannot solve yourself goes to the decision-maker.
Mini work instruction: who does what
| Role | Tasks | Who |
|---|---|---|
| Everyone who takes a request | Puts the request in the list the same day, with name, service, requested time, person responsible and follow-up date. Only confirms after checking the calendar. | All staff |
| Calendar manager | Keeps the calendar as the only place for confirmed times and releases freed-up times right away. | [Name] |
| Daily coordinator | Does the ten-minute daily routine and sends reminders and messages after no-shows. | [Name], backup: [Name] |
| Decision-maker | Assesses unusual bookings and complaints, sets the no-show policy and checks every week whether the list is being kept up to date. | [Owner or manager] |
In a small team one person sometimes has several roles, as long as each role has a name and a backup. Also agree on the following with the whole team:
- A request you take is yours until you assign it to someone else in the list.
- Nobody confirms a time without checking the calendar.
- An open row always has a follow-up date.
- No health or payment details in the list, the calendar or WhatsApp labels.
Example: a week in a garage's list
Worked example
Example: a garage on Indira Gandhiweg (fictional)
A garage with three mechanics and two lifts receives requests by phone, on WhatsApp and at the front desk. Until now, appointments were kept in a notebook, and WhatsApp requests sometimes stayed on the owner's phone.
From now on the owner puts confirmed times in a shared Google Calendar, with one calendar per lift; everything that is still open goes into the spreadsheet. Ricardo from the front desk becomes the daily coordinator, and the owner is the decision-maker.
| Customer | Service | Status | Follow-up date | Next action |
|---|---|---|---|---|
| Dennis (example) | Price of four new tires | Waiting for customer | Wed, Oct 14 | Check back once (agreed) |
| Joyce (example) | Air conditioning not working properly | New | Thu, Oct 15 | Ask the mechanic how long the diagnosis takes |
| Anand (example) | Full service and brake check | Confirmed | Mon, Oct 19 | Send reminder (consent Yes) |
| Wendy (example) | Oil change | Completed | empty | None |
On Thursday morning the Overview tab counts two follow-ups. Dennis is included because Wednesday was busy and his follow-up was left undone; because the count also includes overdue rows, he does not drop off. Ricardo sends him the agreed message and sets the follow-up date to Monday. If there is no response by then, he closes the row.
Ricardo does not know how long it will take to investigate Joyce's air conditioning. He does not guess, but asks the mechanic: an hour. He offers Joyce two times, sets the status to Waiting for customer and the follow-up date to Friday.
Then the reminders for Friday: two customers with consent each get one message; a third gave no consent and gets nothing. After ten minutes every open row has a person responsible and a follow-up date in the future. On Friday the owner spends five minutes looking over it: have there been rows without a follow-up date, double bookings or unusual requests?
In lesson 5 you turn that weekly look into a regular measurement: how many appointment requests became an appointment and how much follow-up was still open at the end of the week.
Checklist
- ☐ Decided where confirmed appointments are kept (calendar or list) and told the team
- ☐ Downloaded the appointments and follow-up list or set it up yourself, with a frozen header row and a filter
- ☐ Set up drop-down lists for Status, Source and Consent to contact
- ☐ Tested the count of follow-ups due today or earlier with a test row
- ☐ Shared the list only with colleagues who need it, with General access set to Restricted
- ☐ Adapted the messages for confirming, rescheduling, canceling, reminding, following up and no-shows, and saved them as quick replies
- ☐ Wrote down your own no-show policy and included it in the confirmation
- ☐ Decided which requests count as unusual and who decides on them
- ☐ Filled in names and backups in the mini work instruction
- ☐ Scheduled a fixed time for the ten-minute daily routine
Lesson 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.
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:
- choose a handful of key figures and write down how you count them;
- fill out a simple scorecard every week, with your baseline for comparison;
- hold a 15-minute improvement meeting every week in which you choose one improvement;
- 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.
| Key figure | What it tells you | Where you count it |
|---|---|---|
| Unique new requests | How many customers wanted something from you this week | Audit or follow-up list |
| % resolved | What share of those requests was actually completed | Resolved or status column |
| % first response within target time | Whether customers get a first answer quickly enough | Time of the request and of the first response |
| Callback rate | Whether missed calls and callback requests are picked up | Callback list (Lesson 2) |
| Booking rate | What share of appointment requests becomes an appointment | Appointments and follow-up list (Lesson 4) |
| Outcomes | What requests lead to: appointment, information, not interested | Outcome or status column |
| Open follow-up | What is still open at the end of the week | Status and follow-up date |
| Channel mix | Which channel requests come in through | Channel or source column |
| Escalations and errors | How often something has to go to the owner or goes wrong in the contact | Escalations, 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.
| Instead of | Why it misleads | Measure instead |
|---|---|---|
| Number of WhatsApp messages sent | Also rises when customers have to ask three times | % resolved |
| Number of phone calls | Says nothing about missed calls or about the outcome | Callback rate and outcomes |
| Followers or likes on social media | A follower is not yet a request | Unique requests per channel |
| Only the average response time | Unanswered requests fall outside the average | % within target time |
| Only the number of appointments | Also rises when there are simply more requests | Booking 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.
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.
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.
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.
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.
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.
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:
| Cause | Example | What you do |
|---|---|---|
| Season | The rush before the holidays, quiet vacation weeks | Compare with the same period last year, if you have those figures |
| Promotions and advertising | A promotion on Facebook, an advertisement, flyers | Note every promotion in the scorecard |
| Holidays | A week with a day off has fewer business days | Compare with an ordinary week instead |
| Capacity | An extra employee, a colleague out sick, a full calendar | Check whether there was room, not just the number |
| Chance with small numbers | 4 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:
| Count | Baseline | Week 3 |
|---|---|---|
| Unique new requests | 60 | 70 |
| Resolved | 39 | 60 |
| First response within target time | 24 | 49 |
| Callback requests and missed calls | 16 | 15 |
| Called back | 6 | 13 |
| Appointment requests | 28 | 32 |
| Appointments booked | 16 | 24 |
| Open follow-up (end of week) | 14 | 6 |
| Escalations | 2 | 3 |
| Errors and complaints about contact | 4 | 1 |
| Key figure | Baseline | Week 3 |
|---|---|---|
| % resolved | 39 ÷ 60 = 65% | 60 ÷ 70 = 86% |
| % within target time | 24 ÷ 60 = 40% | 49 ÷ 70 = 70% |
| Callback rate | 6 ÷ 16 = 38% | 13 ÷ 15 = 87% |
| Booking rate | 16 ÷ 28 = 57% | 24 ÷ 32 = 75% |
| Escalation rate | 2 ÷ 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
Step 1: Measure
Fill in this week's scorecard
Step 2: Discuss
Fifteen minutes with the team
Step 3: Pick one improvement
The biggest bottleneck, not everything at once
Step 4: Put it in place
With an owner and a date
Step 5: Measure again
Next week: did it help?
And then back to the start, every week.
Roles
| Role | Who | Task |
|---|---|---|
| Chair | Owner or manager | Keeps time and makes sure there is one decision |
| Scorekeeper | Whoever fills out the scorecard | Prepares the figures and three to five cases |
| Implementer | Changes with each improvement | Carries out the improvement before the agreed date |
| Note-taker | Chair or scorekeeper | Writes the decision in the improvement log |
The agenda, minute by minute
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.
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?
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.
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.”
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:
| Week | Focus | Done when |
|---|---|---|
| Week 1 | Fill out the scorecard at the fixed time; hold the first meeting | The baseline and week 1 are in; one improvement has been assigned |
| Week 2 | Sample of cases; draft the service standard | The draft has been discussed with the team |
| Week 3 | Review the first improvement; finalize the service standard | The core is up by the phone or counter; the log is up to date |
| Week 4 | Put four weeks next to the baseline | You 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
- ☐ I have written down what counts as a unique request for us and when something is resolved.
- ☐ I have chosen target times for the first response that the team thinks are achievable.
- ☐ I have downloaded the scorecard and entered my baseline from Lesson 1 as the first row.
- ☐ There is a fixed person and a fixed time to fill out the scorecard every week.
- ☐ The 15-minute improvement meeting is on the calendar every week, with a chair and a scorekeeper.
- ☐ In the first meeting one bottleneck was chosen, with an owner and a review date in the improvement log.
- ☐ The service standard has been filled out, discussed with the team and given a review date.
- ☐ I have saved or printed the 30-day plan and scheduled the tasks for the first week.
Made for free by Claudia Academy (Bits Please) · claudia.bitsplease.org/en/academy