Imported records
Supported customer, vehicle, service, invoice, payment, appointment, estimate, and repair-order context is imported according to current API coverage.
Shopmonkey integration
VehicleDesk uses the official Shopmonkey API origin, truthful call budgets, native webhook verification, and visible local data-quality evidence. Shopmonkey remains authoritative for source repair records.
Connection detail
These are product and implementation behaviors, not a generic integration logo claim.
Supported customer, vehicle, service, invoice, payment, appointment, estimate, and repair-order context is imported according to current API coverage.
Shopmonkey remains authoritative for source repair records and financial finalization.
Notes, tasks, reminders, opportunity/deferred state, workflow outcomes, safety evidence, and data-quality findings may be stored locally.
Scheduled and manual jobs use explicit call budgets, retry accounting, quota snapshots, and safe full-sync controls.
Signed provider events enter a queued, replay-aware intake path before processing.
Provider writes remain disabled unless a separately reviewed workflow explicitly enables a narrow operation.
Budget exhaustion, rate limits, provider errors, stale data, and failed jobs remain distinct visible states.
Credentials stay server-side, encrypted, destination-bound, and can be rotated or disconnected without exposing their value.
A VehicleDesk implementation owner and a shop-side owner confirm access, scope, initial sync, and data-quality evidence.
Sync Health records last success, warnings, quota state, and support evidence for investigation.

Practical workflow review
Bring one real workflow. We will show what VehicleDesk can support today, what remains controlled, and what setup would require.