Dealer-system connections
Map and test every dealership system connection.
Showroom InSite connects approved website inputs and shopper inquiries with dealership workflows only through supported, verified configurations.
Connection lifecycle
Map the direction, prove the handoff, and keep ownership visible.
Each connection records the provider, data direction, purpose, permissions, destination, test result, and operating owner.
Map
Source, destination, data direction, purpose, permissions, authority, and owner.
Configure
Supported transport, credentials, field mapping, validation, and fallback behavior.
Test end to end
Safe submission or data refresh through acknowledgement, receipt, and exception handling.
Monitor and change
Health checks, schema or permission drift, incidents, escalation, and offboarding.
Published connections name the provider, direction, and behavior tested.
Connection map
Separate website inputs from lead destinations.
Inventory, pricing, incentives, media, analytics, communications, and lead delivery serve different purposes and may rely on different providers, permissions, refresh behavior, and owners.
- Source, destination, data direction, purpose, and authority for each connection
- Read, write, and acknowledgement behavior documented separately
- Provider names tied to a documented, working data path
Website inputs
Validate the data that shapes customer-facing pages.
Approved vehicle, price, incentive, media, research, location, and content inputs require field mapping, rights, refresh timing, exception handling, and dealership authority.
- Authoritative source and field-level ownership
- Normalization, validation, and conflict handling
- Customer-facing fallback behavior when a provider is delayed or unavailable
Lead delivery
Treat every inquiry pathway as an end-to-end handoff.
The handoff contract identifies source, context, routing, approved destination, supported transport, acknowledgement, reliability behavior, and governance.
- Safe test submission through dealership receipt and disposition
- Idempotency or duplicate control, bounded retries, logging, and failure alerting
- Documented fallback when the destination cannot accept the inquiry
Verification and change control
Keep integration claims current after launch.
Provider changes, credentials, permissions, schemas, destinations, and operating ownership can drift, so each material connection needs ongoing health checks and a named escalation path.
- Current configuration and last verified behavior
- Credential, permission, incident, and offboarding ownership
- Named integrations published only with current evidence and public-use authority
Map the dealership’s actual systems before naming an integration.
We’ll review your current website, search visibility, inventory experience, promotions, lead pathways, and dealer-system workflow.