Connect the systems your dealership already runs.
LotLight ACC coordinates work across your dealership technology stack through the access and integration endpoints each system makes available.
No rip and replace. Your existing systems remain the systems of record.
Connection depth depends on the interfaces, access, permissions, and deployment requirements available from each system.
One operating layer across the systems involved in the work.
Examples are shown for dealership technology-stack context. Integration availability and depth depend on each platform's available interfaces, access, permissions, and deployment requirements.
- DMS
Deal and vehicle records, repair orders, customer information, operational status.
CDK Global · Reynolds & Reynolds · Dealertrack · Tekion
- CRM + Sales
Leads, activities, assignments, customer records, appointments, and follow-up data.
VinSolutions · elead · DealerSocket
- Service
Repair orders, service activity, declined work, and service workflow data.
Xtime · Service platforms
- Parts
Parts availability, inventory, orders, exceptions, and operational status.
Parts platforms · Inventory systems
- Recon + Inventory
Recon tasks, vehicle status, inventory activity, and related workflow information.
RapidRecon · vAuto · Inventory platforms
- Communications
Email, SMS, approved messaging channels, and notification systems.
Email · SMS · Messaging platforms
- Productivity
Calendars, documents, spreadsheets, collaboration, and internal productivity tools.
Microsoft 365 · Google Workspace
- Internal Systems
Dealer-built applications, databases, internal APIs, and custom operational systems where approved access exists.
Not every system exposes the same level of access.
READ
Retrieve available information where exposed by the system.
WRITE
Perform approved supported actions where write access exists and is permitted.
EVENT
Respond to available events, webhooks, or triggers where supported.
VERIFICATION CHECKLIST
- API availability
- Authentication
- Permissions
- Read scope
- Write scope
- Event scope
Integration scope is confirmed during discovery based on the interfaces, permissions, and deployment requirements available for each system. Machine access can be scoped to the permissions and integration requirements of the approved workflow.
The value is coordinating the work between systems.
MORNING OPERATIONS BRIEF
- Scheduled trigger
- ACC reviews approved systems
- Exceptions identified
- Summary generated
- Delivered through Chat
More workflow examples — see the workflow library.
Map the workflow first. Then map the systems.
DEFINE THE WORKFLOW
What outcome should ACC coordinate?
VERIFY SYSTEMS + ACCESS
Which systems are involved and what interfaces are available?
CONTROLLED PILOT
Connect only what the workflow needs, validate, then expand.
A single store may begin with one workflow. Dealer groups can accommodate shared systems and rooftop-specific stacks as the rollout expands. Dealer Group Deployment.
Show us the systems involved in the workflow.
We will map what needs to connect, what access is available, and how LotLight ACC could coordinate the process.