Owner visibility
Dashboard, customer activity, synchronization health, data quality, and launch-readiness evidence help an owner inspect both shop activity and the quality of the inputs behind it.
Pricing and access
VehicleDesk access is currently managed.
There is no public self-serve price or trial promise. A fit review defines the shop, data, workflow, safety, provider, support, and implementation scope before a commercial offer is made.
Explore the fit review No public trial
Initial implementation
What an initial scope evaluates and prepares
The scope is practical: what data exists, which workflows matter, what is already supported, which controls apply, and what evidence is required before launch.
- Owner, Admin Advisor, and read-only workflow review
- Shopmonkey access, supported-object, history, and freshness assessment
- Initial import validation, record linkage, provenance, and data-quality review
- Role access plus messaging, AI, portal, and provider safety configuration
- Staff walkthrough, launch-readiness checklist, gaps, and acceptance evidence
What affects pricing
The offer follows the real implementation.
Price, limits, and ongoing support are not published until these variables are understood and an offer is approved for the shop.
- Number of locations, workspace users, and operating roles
- Available source history, record volume, linkage, and cleanup needs
- Workflows selected for owner review and daily staff use
- Provider access, messaging, AI, portal, and usage boundaries
- Implementation ownership, training, support, rollout, and offboarding scope
Potential scope
Evaluate the operating system as a connected set of responsibilities.
A managed review can cover the full implemented product without implying that every workflow, provider, or control is enabled for every shop.
Daily staff work
Today, appointments, repair orders, deferred service, opportunities, customer and vehicle history, and communication context turn supported records into reviewable staff actions.
Governed access
Owner, Admin Advisor, and read-only capabilities separate management work from review-only access. Privileged support diagnostics use a distinct, time-bounded grant model.
Customer-safe sharing
Authorized Owner or Admin Advisor users can issue scoped, expiring, revocable read-only portal links. Portal access does not authorize customer messaging or provider writes.
Access process
Define the implementation before deciding what it should cost.
The process avoids a low-context self-serve promise and makes commercial, data, safety, cancellation, export, and offboarding expectations visible before launch.
- 1
Fit review
Choose one owner or staff workflow, confirm Shopmonkey and source-history fit, and identify material gaps.
- 2
Implementation scope
Name the data, role, provider, communication, portal, training, and launch-readiness work required.
- 3
Commercial offer
State the approved billing basis, implementation, users or locations, usage limits, support, add-ons, cancellation, and export expectations.
- 4
Launch decision
Proceed only when product fit, operational owners, safety gates, acceptance evidence, and unresolved dependencies are visible.
Questions buyers should ask
Access and commercial boundaries in plain language.
These answers describe the current managed-access posture; an approved offer remains the authority for a specific shop.
Is a self-serve trial available?
No public trial is promised. Registration remains disabled unless an approved environment explicitly enables it.
Does VehicleDesk replace the shop management system?
No. The current implemented connection imports supported Shopmonkey records while Shopmonkey remains authoritative for source repair and financial records.
What should an offer state?
The offer should identify billing basis, implementation, locations and users, enabled providers and workflows, messaging or AI usage, support, taxes or add-ons, cancellation, export, and offboarding expectations.
What happens when the review finds a gap?
The gap should be recorded as unsupported, controlled, provider-dependent, or additional implementation work. A review is useful even when the responsible decision is not to proceed.
Practical workflow review
Define the implementation before deciding what it should cost.
Preview the workflow-review agenda, current product scope, safety boundaries, and implementation questions before public requests open.