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.
DMS DMS workflow
LightSpeed DMS integration for prospect writeback from TECOBI conversations.
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.
LightSpeed DMSAddProspectWritebackNotes
DMS writeback
LightSpeed DMS writeback keeps TECOBI conversation activity visible beyond messaging.
When a store needs prospect activity in the DMS, contact details, vehicle interest, preferred contact method, and notes have to move cleanly.
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.
Prospect visibility
A TECOBI-worked prospect should not disappear from the DMS view.
TECOBI can support LightSpeed AddProspect XML payloads, workflow triggers, submission logging, response status, and returned identifiers.
- Lead or chat activity can trigger prospect writeback when the store needs it.
- Vehicle interest and notes help the DMS record describe the actual conversation.
- Submission logs make troubleshooting and audit review easier.
Integration architecture
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.
01
Prepare
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
02
Submit
Create the Lightspeed prospect
The dealership-specific record is sent through the Lightspeed AddProspect workflow.
- Dealer routing
- Prospect creation
- Success or error response
03
Confirm
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
What this integration can carry through the workflow.
- 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
LightSpeed path
Write useful prospect context back into DMS operations.
The workflow should keep customer communication and store visibility aligned without asking teams to duplicate entry.
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.
Apply TECOBI coverage
LightSpeed AddProspect XML payload support. Contact data, preferred contact method, vehicle interest, and notes.
Route, inspect, and improve the outcome
Lead or chat workflow trigger support. Submission logging with response status and identifiers.
TECOBI fit
Where TECOBI supports this workflow.
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.
Proof path
Show DMS writeback through operational visibility.
Payload support, identifiers, response status, and notes give the store better accountability around prospect writeback.
Next pages
Continue through the related TECOBI pages.
FAQ
Common questions about this workflow.
Is the LightSpeed DMS integration available?
Available prospect push. Implemented as a TECOBI lead-to-prospect handoff for configured LightspeedDMS dealerships.
What data can the LightSpeed DMS integration carry?
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.
Does TECOBI replace the dealership's existing CRM or DMS?
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.
Google reviews
Customer teams describe the response and follow-up experience.
Synced Google reviews add public customer voice around TECOBI support, follow-up coverage, handoffs, and day-to-day impact.
Highest-rated automotive vendor on Google
Pulling the latest Google review signal from TECOBI’s Google Business Profile.