Operations guide
Resolve data-quality findings that change the day
Work from import confidence and provenance into contact, duplicate, linkage, and merge findings, and apply the inspected correction.
- Written by
- VehicleDesk Product and Engineering
- Content updated
- September 17, 2026
Prioritize by decision impact
A missing vehicle link, a malformed contact point, a duplicate candidate, and a stale source each change different workflows. Review starts with the queues and reports that rely on the affected record.
Trace the provenance
Source, import run, mapping, timestamp, and related records show whether a finding is workflow data, imported provider data, or a derived observation.
Inspect and apply the correction
Duplicate and merge candidates show the proposed result with a confidence score. The team applies the fix with the source in view.
Verify the result
Record the owner, change, source, date, and validation result, then confirm the downstream customer, vehicle, queue, or report shows the expected state.
Worked example: a merge that changes a queue
A duplicate customer candidate appears because the same person was entered twice over time.
The proposed merge shows the combined record and a confidence score. The team inspects the source records before applying it.
After the merge, the follow-up queue shows one customer with combined history, and the change and its verification are recorded.
Checklist: resolving a finding
Resolve findings by their effect on real work.
- Start with the queues or reports the finding affects
- Trace the field to its source before changing it
- Apply the correction with the source in view
- Verify the downstream screen shows the expected state, then record the result
Common questions
Will VehicleDesk merge duplicates automatically?
No. It identifies duplicate and merge candidates and shows a proposed result with a confidence score. A person applies the correction with the source in view.
What is provenance?
The trail behind a value: its source, the import run, the mapping, the timestamp, and the related records, so the team can judge whether to trust it.
More guides
Other operations guides
- Plan an advisor follow-up day from the timeline: A repeatable process for reading scheduled follow-ups, triaging the unscheduled tray, placing work on open time, and recording the next action.
- Check CRM data quality before you trust a report: A practical checklist for import freshness, customer contactability, vehicle completeness, record linkage, errors, and decision confidence.
- Turn appointment requests into confirmed bookings: A practical guide to appointment requests, scheduling, customer and vehicle matching, capacity context, reminders, and handoffs.
- Keep parts and vendor costs accountable: Enter every vendor invoice, link parts to the repair order, and keep returns, cores, credits, and aged open costs visible until they close.