# LightSpeed DMS integration for prospect writeback from TECOBI conversations.

Canonical page: https://www.tecobi.com/integrations/lightspeed-dms/
Primary topic: LightSpeed DMS integration

LightSpeed DMS support gives dealerships a way to push TECOBI-managed prospect activity into the DMS when the store needs stronger operational visibility than messaging alone provides.

## What TECOBI supports
- LightSpeed AddProspect XML payload support.
- Contact data, preferred contact method, vehicle interest, and notes.
- Lead or chat workflow trigger support.
- Submission logging with response status and identifiers.

## Dealership workflow
### Prospect activity should be visible beyond the message thread.
When TECOBI creates or works a prospect, the DMS can need contact details, vehicle interest, and notes for operational visibility.

### Writeback needs clear status.
Submission logging helps teams see response status and returned identifiers for audit and troubleshooting.

### DMS workflow supports accountability.
The goal is to keep customer communication and store reporting aligned instead of splitting them into separate systems.

## Integration status and scope
- Status: Available prospect push
- Scope: One-way prospect creation
- Availability: Implemented as a TECOBI lead-to-prospect handoff for configured LightspeedDMS dealerships.

## Move a worked TECOBI lead into LightspeedDMS as a prospect.
The integration packages useful customer and vehicle context, creates the Lightspeed prospect, and records the returned identifier for store visibility.

### Build the prospect record
TECOBI assembles customer contact details, address, vehicle interest, preferred contact method, and conversation context.
- Customer and contact
- Vehicle interest
- Source and assignment notes

### Create the Lightspeed prospect
The dealership-specific record is sent through the Lightspeed AddProspect workflow.
- Dealer routing
- Prospect creation
- Success or error response

### Keep the handoff traceable
TECOBI records the submission result and returned PCH ID on the lead timeline when the push succeeds.
- Submission log
- Returned PCH ID
- Timeline confirmation

## Connected data
- Customer name and contact details
- Address and preferred contact method
- Vehicle year, make, model, and condition
- Lead source and assignment notes
- Submission response and errors
- Returned Lightspeed PCH ID

## Scope boundary
This is a one-way prospect push, not a full two-way CRM synchronization. It creates a LightspeedDMS prospect from a TECOBI lead and records the submission result.

## Related TECOBI pages
- [DealerVault integration](https://www.tecobi.com/integrations/dealervault/): Review DMS feed ingestion and reporting support.
- [CRM automation](https://www.tecobi.com/automotive-ai/automotive-crm-automation/): Connect DMS writeback to automation.
- [Integrations](https://www.tecobi.com/integrations/): Explore the full integration hub.