Garages and car dealerships
Car listings: answer equipment questions without guessing
An equipment answer must trace back to the exact vehicle’s approved listing. General model-series specifications do not prove an individual car’s equipment. Unknown details should become salesperson questions rather than convincing guesses.
Understand the task
Product descriptions, images and earlier advertisements may describe different variants. An assistant can combine them into a car that does not exist. Keep reference, variant and approved source together. Photos may support staff review, but a model’s image guess must not replace verified facts.
Prepare these inputs
- One approved specification with a unique vehicle reference.
- A list of equipment not yet checked.
- A salesperson responsible for changes and enquiries.
A practical workflow
- Match the question to the exact car. Preserve the distinction between standard equipment, options and unknown.
- Answer confirmed details and show the listing reference. Do not transfer facts from another variant.
- Collect unknowns into one clarification task. Check corrections in both the listing and subsequent answers.
Worked example, not a customer case
An illustrative example
Illustrative example: a customer asks about a heat pump and tow bar. The listing confirms only the tow bar. The answer distinguishes them and asks the salesperson to confirm the heat pump. A general article about the model does not fill the gap.
Test failures and exceptions
| Test input | Expected outcome |
|---|---|
| Another variant has the requested equipment. | Do not use that variant as evidence. |
| The listing has just been corrected. | Check that new answers use the correction. |
Evaluate whether it helps
Review equipment claims without evidence and salesperson corrections. Keep fictional reference examples for retesting. Evaluate accuracy per vehicle rather than fluency alone.
Next step: Test a question containing one confirmed and one unknown equipment detail. They require different treatment.
Sources and scope
Examples are editorial exercises using fictional information. They do not describe completed customer tests or activated integrations. The authority source below provides AI and data background rather than approval of the exercise.
Want to clarify your own workflow?
Bring one task and a non-sensitive example. Scope, price and timing are agreed individually before work. Reading a guide activates no customer messages or system actions.
Describe your task