Integrations
Shopmonkey is the verified source-data integration. Communication, reputation, and assistive-AI foundations are shown separately at their controlled or provider-dependent status instead of being presented as generally available integrations.
Source-data connection
The Shopmonkey record boundary covers customers, vehicles, services, estimates, invoices, payments, appointments, and repair orders, with freshness and failure evidence kept visible.
1 verified data connection
Source boundaries includedVehicleDesk imports supported shop records through a guarded, rate-aware connection while Shopmonkey remains authoritative for source repair data.
Supported records are imported into VehicleDesk. Provider writes remain disabled unless a separately approved workflow explicitly enables them.
Provider credentials stay server-side, encrypted, destination-bound, and absent from browser bundles.
Sync health, quota guards, freshness, missing links, and provider errors are shown as distinct states.
Adjacent provider foundations
These boundaries explain the provider-facing code paths already present in VehicleDesk. They do not mean live delivery, provider approval, or production availability has been established.
VehicleDesk models provider setup, eligibility, approval, acceptance, and delivery evidence as separate states. Live customer delivery is disabled by default and is not represented as generally available.
Review communication controlsOAuth, review-sync, and reply foundations exist, but production behavior depends on Google access, shop authorization, account and location selection, and observed provider readiness.
Review reputation availabilityServer-side assistance can prepare bounded guidance from minimized context. It cannot determine eligibility, change source records, launch campaigns, or contact customers.
Review the AI boundaryPractical workflow review
Preview the workflow-review agenda, current product scope, safety boundaries, and implementation questions before public requests open.