Free document · Claudia Academy
30-day plan for your customer service
This plan turns the whole course into four weeks of work and a check on day 30: from the baseline to a fixed phone and callback process, a properly set-up WhatsApp Business, an appointments and follow-up list and a weekly measurement. For each week it shows what you do, who does it, roughly how long it takes and how you can tell it has worked. Print it or save it as a PDF and check off what is done. The times are estimates; take more time if you need it and skip what you already have.
Version 1.0 · reviewed 2026-10-16 · goes with lesson 5
How to use this plan
Appoint one coordinator
Usually the owner or manager. The coordinator schedules the tasks, keeps this plan up to date and chairs the weekly meeting.
Divide the roles
Fill in below who has which role. In a small business one person often has several roles; that is fine, as long as it is clear.
Put the fixed times on the calendar now
Every week, a time to fill out the scorecard (about 15 minutes) and a 15-minute improvement meeting. On day 30, a check of about 45 minutes. How the scorecard and the meeting work is explained in Lesson 5.
Work week by week
Only start a new week once the main points under “Done when” for the previous week have been met. Letting a week run over is better than introducing everything halfway.
| Role | Does | Often |
|---|---|---|
| Coordinator | Schedules, keeps track of this plan and chairs the weekly meeting | Owner or manager |
| Phone handler | Answers calls and keeps the callback list up to date | Reception or front desk |
| WhatsApp handler | Answers messages and keeps the labels up to date | Reception, front desk or owner |
| Appointments manager | Manages the calendar and follow-up list, confirms appointments | Reception or scheduler |
| Scorekeeper | Fills out the scorecard and prepares cases for the meeting | Coordinator or a regular employee |
Role allocation (fill in)
Coordinator: [name]
Phone handler: [name], backup: [name]
WhatsApp handler: [name], backup: [name]
Appointments manager: [name], backup: [name]
Scorekeeper: [name]
Fill out the scorecard on: [day and time]
Weekly meeting on: [day and time], 15 minutes
Start date: [date], check on day 30: [date]
Week 1: baseline and basic agreements
Goal: know how your customer contact works now, before you change anything. The explanation is in Lesson 1; you work with the customer contact audit.
| Task | Who | Time |
|---|---|---|
| Set up the audit spreadsheet and explain to the team what a unique request is | Coordinator | About 30 minutes |
| Log every request for seven days, across all channels | Everyone who deals with customers | About 5 minutes per day per person |
| Copy missed calls from the phone's call log every day | Phone handler | About 5 minutes per day |
| Analyze the audit: unique requests, how many went unanswered, response time, busy times | Coordinator | About 45 minutes |
| Choose target times for the first response on each channel | Coordinator with the team | About 20 minutes |
| Put fixed times for the scorecard and weekly meeting on the calendar | Coordinator | About 10 minutes |
Done when
- Seven days of requests are in the audit, including those from busy times and from outside business hours.
- You know how many unique requests you received and what share went unanswered.
- Target times have been agreed that the team thinks are achievable.
- The baseline is the first row in the scorecard.
Week 2: phone and callbacks
Goal: every call is answered or called back according to a fixed process. The explanation is in Lesson 2; the scripts are in Phone scripts and callback process.
| Task | Who | Time |
|---|---|---|
| Adapt the greeting and question script to your business | Coordinator | About 45 minutes |
| Set up the callback list (on paper or in a spreadsheet) and choose fixed callback times | Phone handler | About 30 minutes |
| Write down escalation rules: what goes to whom, and how quickly | Coordinator | About 30 minutes |
| Record the voicemail greeting, and arrange call forwarding if your phone provider supports it (ask them) | Phone handler | About 30 minutes |
| Brief the team and practice the script a few times | Coordinator and team | About 30 minutes |
| Fill out the scorecard for week 2 and hold the first weekly meeting | Scorekeeper and coordinator | About 30 minutes |
Done when
- Everyone who answers the phone uses the same greeting and asks the same basic questions.
- Every missed call goes on the callback list the same day, with an owner.
- There is a written escalation rule that the team knows.
- The callback rate is in the scorecard for the first time.
Week 3: setting up WhatsApp Business
Goal: messages are followed up quickly, consistently and visibly. You use the free WhatsApp Business app on a phone. The explanation is in Lesson 3; the texts are in WhatsApp Business: quick replies and labels.
| Task | Who | Time |
|---|---|---|
| Fill out the business profile completely: name, category, description, address, business hours and contact details | WhatsApp handler | About 30 minutes |
| Set up a greeting message, and an away message for outside business hours | WhatsApp handler | About 20 minutes |
| Create five to ten quick replies for the questions that came up most often in your audit | WhatsApp handler with the coordinator | About 45 minutes |
| Set up labels and agree when each label is used | WhatsApp handler | About 20 minutes |
| Agree on who keeps an eye on WhatsApp, including during breaks and outside business hours | Coordinator | About 15 minutes |
| Fill out the scorecard and hold the weekly meeting | Scorekeeper and coordinator | About 30 minutes |
Done when
- The business profile is complete and the business hours are correct.
- Anyone who sends a message outside business hours is automatically told when you will reply.
- The team uses the quick replies, and every chat that is still open has a label.
- For WhatsApp requests, you can count how many got a first response within the target time.
Week 4: appointments, follow-up and the weekly rhythm
Goal: every appointment and every open question has an owner and a date, and you discuss the figures every week. The explanation is in Lesson 4 and Lesson 5; you work with the appointments and follow-up list and the scorecard.
| Task | Who | Time |
|---|---|---|
| Set up the appointments and follow-up list and copy over the open items from the audit and the callback list | Appointments manager | About 1 hour |
| Agree on a fixed process for confirmations and reminders, only for customers who have agreed to them | Appointments manager with the coordinator | About 20 minutes |
| Go through the follow-up list every day: what needs doing today, or should have been done earlier? | Appointments manager | About 10 minutes per day |
| Write a draft of the internal service standard | Coordinator | About 1 hour |
| Hold the weekly meeting using the fixed agenda and choose one improvement | Coordinator and team | 15 minutes |
| Fill out the scorecard for week 4 | Scorekeeper | About 15 minutes |
Done when
- Every open request is in one list, with status, owner and follow-up date.
- Someone checks every day which follow-ups were due today or earlier.
- There is an improvement log with at least one decision, with an owner and a review date.
- The draft service standard is with the team for discussion.
Weekly meeting agenda (15 minutes)
1. Review the figures, this week next to last week and the baseline (3 minutes)
2. Sample: three to five real cases, for example an escalation, a late response and an open item (5 minutes)
3. Choose one bottleneck; note the rest for later (3 minutes)
4. Agree on one concrete improvement with one owner (3 minutes)
5. Set a review date and record the decision in the improvement log (1 minute)
Day 30: the check
On day 30, take forty-five minutes to look back, with the whole team or at least with the regular staff.
Put the figures side by side
Put the baseline next to weeks 2, 3 and 4 in the scorecard. Look at the counts and at the percentages.
Read the notes
Which weeks had a holiday, a promotion, illness or an outage? Take that into account before you draw conclusions.
Assess the improvements
Go through the improvement log: what worked, what did not, and what was never carried out?
Finalize the service standard
Work in what the team said, add a version date and put up the core of it by the phone or the counter.
Choose the focus for next month
One or two bottlenecks, no more. Write them in the improvement log.
| Key figure | Baseline | Week 4 | What stands out? |
|---|---|---|---|
| % resolved | ______ | ______ | ______ |
| % first response within target time | ______ | ______ | ______ |
| Callback rate | ______ | ______ | ______ |
| Booking rate | ______ | ______ | ______ |
| Open follow-up (count) | ______ | ______ | ______ |
| Escalations (count) | ______ | ______ | ______ |
| Errors and complaints about contact (count) | ______ | ______ | ______ |
Done when
- Besides the baseline, the scorecard has at least three completed weeks.
- For each key figure you can say whether it is better, the same or worse, and which other causes may play a part.
- The service standard has been finalized and the team knows it.
- The weekly meeting is on the calendar for the coming months.
After day 30: the regular rhythm
| How often | What | Who |
|---|---|---|
| Every day | Go through the callback list and follow-up list; update the WhatsApp labels | Phone and WhatsApp handlers, appointments manager |
| Every week | Fill out the scorecard (about 15 minutes) and hold the improvement meeting (15 minutes) | Scorekeeper and coordinator |
| Every month | Look at the channel mix; update quick replies and scripts | Coordinator |
| Every quarter | Review the service standard and target times | Coordinator with the team |
| With every new employee | Go through the service standard, scripts and lists together in their first week | Coordinator |
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, without the improvement being carried out.
- The weekly 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. You can find all the lessons in the course Build a customer service system that never forgets a request.
Made for free by Claudia Academy (Bits Please) · claudia.bitsplease.org/en/academy