Your website can send a thank-you message while the service appointment diary has no entry. A receptionist can answer a call without anyone agreeing when the vehicle should arrive. A booking audit should follow each request until the customer has a confirmed visit that your service team can find.
Decide what counts as a confirmed visit
A confirmed appointment needs an agreed arrival time and a corresponding record available to the service team. That record must identify the vehicle and requested work well enough for the adviser to prepare for the visit.
An acknowledgement proves only that a request reached someone or something. An email reference number does not establish that the workshop has accepted the appointment. Your website can legitimately collect requests for staff to review, but the customer must understand that the visit remains pending.
Use that distinction as the audit’s pass condition. Do not mark a test successful because the phone was answered promptly or the form displayed a success message.
Choose one routine job and log the handoffs
Choose scheduled maintenance that your workshop normally handles. Keep the vehicle details, requested work and preferred arrival period consistent across the tests, so differences in the job do not explain differences in the booking experience.
Use an authorised test record and contact details you control. Have a manager coordinate the audit and remove test appointments after you have checked them. Clear each case before starting the next so duplicate-request handling does not distort the result or leave reservations occupying real capacity.
Start a simple log when each attempt begins. Note when the request reaches a definite outcome, rather than stopping the clock when someone answers or the website accepts the form.
- Record unanswered questions, especially whether the requested time has been accepted.
- Note every transfer and whether the next person knows why the customer is calling.
- Write down details the customer must provide again, including information already entered online.
- Capture the final booking status and any follow-up the dealership says will happen.
Give uncertainty about appointment status more weight than inconvenience. A transfer can be necessary; a completed conversation that leaves the customer unsure whether to turn up is a failed handoff.
Follow the phone and mobile routes beyond the first response
Call the number a customer would find on your public website. Ask for the chosen service and an arrival time, then follow the normal route through reception, a booking team or a service adviser. Do not use an internal extension that bypasses the process you want to test.
If someone promises a callback, leave the case open until that callback produces an agreement or the promised response window passes. Note whether the caller must repeat the whole request. The important distinction is between transferring responsibility and simply transferring the call.
For the website test, use a phone without a staff login and begin on the dealership’s public homepage. Find the service booking route and complete it as a customer would. This tests whether the route is usable, not merely whether a direct link supplied by your website provider works.
Read the final screen carefully and save its wording alongside any email or text that follows. A selectable time can look like an appointment even when the final message describes it as a preference awaiting approval.
Include a closed-hours attempt on each channel
Repeat both routes while the service booking team is unavailable. Listen to the full phone message and follow its instructions. If voicemail is offered, leave enough information for staff to act, then check what happens when the team returns.
On the website, establish whether the customer receives an appointment or enters a queue for review. Either arrangement needs a clear explanation. A pending request should tell the customer what happens next and when to expect a response.
Check whether follow-up arrives within the stated window. If no window is given, record that uncertainty. The problem is not that a closed dealership fails to answer immediately; it is that the customer cannot tell whether to wait, call again or arrive at the requested time.
Match the customer’s confirmation to the workshop diary
Once a test produces a confirmation, ask the adviser who would receive the vehicle to locate the booking through their normal working process. Do not let the test coordinator supply a hidden reference or retrieve it from a separate inbox. You need to know whether the service team can find it without help.
Compare the customer’s message with the appointment record. Check the location, vehicle and requested service, then verify the date and arrival time. If your booking tool and workshop diary are separate, inspect the handoff between them rather than assuming that a confirmation means the record transferred.
Pay particular attention to whether the customer plans to wait or leave the vehicle. That choice affects the discussion about timing, and it should not disappear between the booking conversation and the adviser’s view.
Treat drop-off as an arrival commitment, not as a promise that work starts immediately or finishes at a particular hour. If your team agrees to a completion time, that commitment needs to appear wherever staff prepare for the visit.
Suppose your test asks for a morning drop-off and collection before lunch. If the customer’s confirmation promises collection before lunch but the workshop record contains only the arrival time, the two sides have different commitments. Correcting that difference at the service desk leaves the adviser negotiating a promise the customer believes the dealership already made.
Assign the failed step, then repeat the whole route
Fix missing bookings and conflicting commitments before polishing wording or removing an extra click. Those failures affect whether the workshop expects the vehicle and what the customer believes will happen. Friction still matters, but it belongs behind failures that change the appointment itself.
Give each issue a named dealership owner and a specific acceptance test. The service manager might own a callback queue, while the person responsible for the website owns a form that describes a pending request as confirmed. If a supplier must change something, a dealership manager should still own the issue through to verification.
Make the required change concrete. Instead of asking someone to improve online booking, specify that the final screen must describe the request as pending and state the response window. For a lost handoff, specify where the request must appear and which role must act on it.
After the change, repeat the original customer route from the beginning. Testing only the edited screen will not reveal whether its new wording conflicts with the email, or whether a repaired transfer still ends in an unattended queue.
Keep the failed case open until the retest reaches an agreed appointment and a matching workshop entry. That gives you a clear basis for closing the issue: evidence from the customer’s route, rather than an assurance that someone changed a setting.