Listed
A vehicle or service is presented with current source data.
Next: Compare / choose action.
Automotive & Mobility
Automotive journeys often lose the exact configuration, availability snapshot or service need when the visitor moves from comparison to a dealer, fleet team or booking workflow.
Context handoff
Inventory / service state
A vehicle enquiry, test drive and service appointment each require different authoritative context.
A vehicle or service is presented with current source data.
Next: Compare / choose action.
The public layer cannot confirm current stock or slot.
Next: Request confirmation rather than imply certainty.
The customer has asked for a viewing, test drive or service slot.
Next: Route to the owning dealer/service workflow.
The authorized team or scheduling system has accepted the request.
Next: Send practical next-step details.
Handoff payload
The receiving team should know what the customer already selected.
Availability change
A robust flow preserves trust and context.
The team can see which vehicle caused the enquiry even if its state changes.
Do not continue showing availability that the source no longer supports.
Use the configuration context to suggest comparable stock or a useful follow-up.
What this proves
The conversation starts from the customer’s actual selection rather than a blank lead record.
Next step
Start with the customer action, the system that owns availability and the information the receiving team currently has to rediscover.