Your booking page can look clear to you and leave a new customer unsure. Does choosing a time book the repair, or only the drop-off? Will someone call to confirm it?
Your staff already know the answers, so they can miss the gaps. Ask someone who has never used your service department to follow the booking process instead. Watch where they stop and what they think will happen next.
The goal is a short list of changes you can assign and check. A broad comment such as “booking was confusing” is not enough to work from.
Set up a test that leaves real bookings alone
Choose someone who does not work in your service department and does not know its booking steps. They do not need to know cars. They need to be willing to say when something makes no sense.
Give them a simple task, such as asking to book an oil change. Agree on the car and contact details they can use. Keep those details the same for the website and phone tests.
Before they start, find out which website button sends a request or holds a slot. Stop before that point unless your team has a safe test route that cannot affect real bookings. Do not assume you can book a slot and cancel it without affecting anyone.
Arrange the phone test with the service manager. Tell the employee it is a practice booking before they hold a time or create a live record. Ask them to use their normal questions.
If you cannot safely test the final step, review it separately with staff. Mark that step as reviewed, rather than tested by the outsider.
Let the tester work without help
Start on the page a new customer would reach, not a booking link you have sent them. Ask them to find service booking on their own. Sit beside them or watch their shared screen, but do not point to the right button.
Have them say what they are looking for as they go. Note the page and field where they pause. Copy the wording that caused trouble rather than writing a broad note about the website.
On the phone, have the tester use the same service request. Let them ask the questions a customer would ask. Do not coach them to use terms your team prefers.
After each route, ask them to explain what they believe they have arranged. Can they describe when to arrive and when they expect the car back? Ask what they would do if no further message arrived.
Write their answers before staff explain what they meant. The difference between those answers is part of the test.
Record the gaps in useful detail
Use a simple shared note or spreadsheet. Give each issue its own line, with the page or phone step where it happened. Keep the tester's experience separate from your proposed fix.
Look for these problems:
- Missing details: Could the tester find where to arrive and whether they should leave the car?
- Repeated questions: Did the employee ask for something the tester had already entered? Note whether the employee explained why.
- Unclear next steps: Did the tester know whether they had a confirmed visit or were waiting for a reply?
- Promises about time: Did the tester think the chosen time meant arrival, the start of work, or collection?
Not every repeated question is a fault. Staff may need to check a detail before agreeing to the work. The issue is whether the earlier answer was missing or the reason for asking again was unclear.
Be exact about timing. A promise to call with an update is different from a promise to finish the car. Record which one the tester heard.
Check what reaches the service advisor
Your service advisor, who checks in the car and discusses the work with the customer, needs the booking details. Ask them to show the screen or record they would use when this customer arrives.
Use a clearly marked test record if you can create one without affecting real work. Otherwise, walk through where each answer would go. Keep real customer details out of the test notes.
Put the tester's notes beside the information the advisor would receive. Check whether both show the same work request and the same plan for timing. Look for a promise about waiting or collection that appears in only one place.
Ask the advisor to explain the planned visit using that record alone. Do not let the person who took the booking fill in the gaps from memory. Note anything the advisor would need to ask the customer again.
Also check who sees a request before it becomes a confirmed booking. If someone must call the customer, name that role. Check what happens when that person is away.
Give each fix one owner
Start with gaps that change what the customer expects. A mistaken belief that a booking is confirmed deserves attention before a small wording change elsewhere.
Write each fix as a task someone can finish. “Improve booking” gives no clear direction. “Change the message beside the final button to explain that staff must confirm the request” does.
Give the task to one person, even when several people need to help. Agree on a due date and write down how you will check the change.
Choose the owner based on where the gap starts. The person who edits the website can change its text. The service manager should check whether staff can meet the promise that text makes.
For a missing note, trace where the detail was first collected. Decide where the advisor should see it, then check that path. Do not add another question to the arrival process before checking what happened to the original answer.
Repeat the same task after the changes
Run the same request through the website and phone again. Keep the car details and questions unchanged. You need to see what changed in the booking process, not how staff handled a different request.
Where possible, use another person who has not seen the first test. The first tester now knows what your booking steps mean. Someone new can show whether the revised wording stands on its own.
Return to each issue in your notes. Check what the tester understood and what reached the advisor. Close a task only when the test shows the specific gap has been addressed.
Repeat the review when you change booking pages or the way staff pass requests to each other. Keep the notes from earlier tests. At your next service meeting, use them to discuss the exact step that needs work, rather than a general call for better service.