When missed service updates put a dealer management system (DMS) replacement on your agenda, audit the repair orders (ROs) behind those failures before committing to a change. Compare the work record with the customer contact history. You need to establish whether staff lacked a usable way to communicate or whether the next update had no clear owner.
Put approval waits and delays first
Give approval waits and changed completion times the closest attention. A missing authorisation can stop work; an uncommunicated delay can leave a customer expecting a vehicle that is not ready. Routine arrival acknowledgements deserve less attention unless they expose incorrect contact details or an unclear update commitment.
Pull recent closed ROs that generated complaints or repeated customer calls, alongside routine orders that went through without a problem. Include work that crossed an adviser’s absence or shift change. Comparing those records helps you distinguish a workflow that anyone can follow from one that depends on a particular employee keeping everything in their head.
Reconstruct the sequence from check-in to collection
For each RO, record when the department learned something that required customer contact. Then compare that time with the promised update and the evidence of actual contact.
- Check-in: Find the agreed contact channel and any commitment about the next update. Check whether those details were available to the person covering the order, rather than sitting on a paper note at the original adviser’s desk.
- Estimate approval: Identify the version of the estimate the customer received and the record of their decision. A message marked as sent does not establish authorisation, and a reply about earlier work may not cover a later addition.
- Delays: Establish when the department learned that a part or unfinished work would affect completion. Check when that information reached the adviser, then find the customer update or the recorded reason contact did not happen.
- Pickup: Compare the notification with the point when the vehicle was genuinely ready for collection. Check whether the covering adviser could confirm the release arrangements without chasing the person who sent the message.
Do not fill missing timestamps with estimates from memory. Mark them as missing: the inability to reconstruct a handoff is itself a finding, even when the customer eventually collected the vehicle without complaining.
Check what another adviser can actually see
Open the RO detail screen beside whichever record holds the outgoing messages. For each update, note its location and sender, then check whether the record shows what the customer was told. The history might sit in RO comments, a shared inbox, a separate messaging application or a phone log.
Ask a covering adviser to find the latest customer commitment using their own authorised login. Do not let the original adviser supply the explanation. If the covering adviser needs that person’s memory or private inbox, you have located a dependency that deserves investigation.
For calls, look for a dated note that records the outcome and any further commitment. A blank history establishes a documentation gap, but it does not prove that nobody called.
Classify the break before choosing the remedy
Check ownership first because you can test it directly against the work record. Verify access and configuration before declaring a function absent; neither a missing note nor an unfamiliar screen proves that you need another DMS.
- Unassigned responsibility: The information was available, but nobody had explicit responsibility for contacting the customer. A parts update sent to a shared queue can still sit untouched if everyone assumes an adviser has picked it up.
- Missing upstream information: The adviser could send an update but did not know that the completion estimate had changed. Fixing this gap starts with the person who learns about the delay, not with a different customer message template.
- Access or setup: The history exists, but an authorised covering adviser cannot reach it through the current workflow. Ask your system administrator or supplier to check permissions and supported configuration before treating the gap as a product limitation.
- Capability limit: The required handoff cannot be completed through a supported workflow or approved connection. Describe the task that fails, such as retrieving the customer’s latest decision against the correct estimate, rather than writing a broad requirement for better communication.
Manual copying also needs scrutiny. A workflow may be technically possible yet depend on staff repeatedly transferring the same information between records. Document those steps rather than accepting either a claim that the function exists or an assumption that replacement is the answer.
Test ownership changes in the current setup
For gaps your team can address, write down the event that triggers contact and assign a responsible role. Include cover for breaks and absences. An instruction to keep customers informed leaves the original ambiguity in place.
If changed parts availability affects completion, specify where the parts employee records that change and how the assigned adviser receives it. The adviser should record the customer contact outcome in a location that authorised cover staff can use. Set the next contact commitment according to the job, rather than making every order follow an arbitrary message schedule.
Agree on a review period, then repeat the trace on comparable ROs. Look for customer commitments that passed without a recorded update, and separate those cases from unsuccessful contact attempts that staff documented.
Watch for work that moves out of sight. If the correction depends on a manager maintaining a separate spreadsheet or repeatedly chasing updates, record that effort as part of the workflow you are evaluating.
Turn unresolved gaps into working supplier tests
An acceptance test is a scenario with an observable pass or fail. Build yours from the unresolved ROs, with customer-identifying information removed. Give the same scenarios to your current supplier and any prospective replacement supplier so each must address the same operational requirement.
Start with a delay scenario that includes adviser cover. Require the person demonstrating the system to record the changed completion expectation, hand responsibility to the covering adviser and show the customer contact history from that adviser’s authorised view. The test passes when the covering adviser can identify the outstanding commitment without help from the original adviser.
Next, test a revised estimate while approval remains outstanding. Require the demonstration to distinguish the earlier customer decision from the new work awaiting authorisation. Ask where the covering adviser finds the next action and how the record shows who is responsible for it.
Require a working demonstration rather than a slide or a description of planned functionality. Treat polished message wording as a presentation check; shared visibility of the correct customer decision matters more. Ask the supplier to identify any additional application or manual transfer required to complete the scenario.
An unresolved gap may point to a connected communication tool rather than a whole-system replacement. Make the purchasing requirement the handoff your department must complete, and judge each proposed setup against that work.