Operations guide
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.
- Written by
- VehicleDesk Product and Engineering
- Content updated
- September 17, 2026
Check freshness
Confirm the latest successful import, scheduled-job state, webhook processing, and any provider quota or authentication error before relying on a queue or report.
Check record usability
Review contactability, vehicle identifiers and mileage, service and financial history, customer, vehicle, and order linkage, duplicate candidates, malformed values, and the provenance of the fields behind a decision.
Check workflow coverage
Prior-period comparisons, opportunity reasoning, and customer value depend on the imported records behind them. Sync health shows how much history each question rests on.
Inspect the correction
VehicleDesk identifies duplicate and merge candidates and shows the proposed correction with a confidence score. The team applies it with the source in view.
Keep the trail
Record warnings, repair actions, owner, date, source, and verification result so every confidence score stays explainable.
Worked example: deciding whether to trust a report
An owner opens a revenue report and checks the freshness line first: the last successful import and the current job state.
The report covers a period that was fully imported, and the fields behind the figure trace to source records.
One duplicate candidate appears among the customers behind the number. The team resolves it before the figure is used in a decision.
Checklist: trust checklist for any report
Apply this before a number changes a decision.
- Freshness is current and no import job is failing
- The reporting period is fully imported
- Fields trace to a source record
- Duplicate and linkage findings affecting the number are resolved
Common questions
What does import confidence mean?
It describes how completely and cleanly a record came through the import: whether required fields are present, whether related records are linked, and whether the mapping succeeded.
Can findings be fixed in VehicleDesk?
Yes. Each finding shows a proposed correction with a confidence score, and the team applies it with the source in view. The correction and its verification are recorded.
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.
- 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.
- 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.