Outcomes
An outcome is the record of something real: a drive completed, a customer who did not turn up, a deposit taken, a bank's answer. Outcomes are how the pipeline moves, and they are the difference between a system that knows what happened and one that knows what somebody typed.
How it works
- 01
Pick the outcome that is true
The list you see is your dealership's own vocabulary, not a generic activity log. “Test drive completed” and “test drive booked” are different outcomes because they mean different things.
- 02
Let the interpreter decide the consequence
One place decides what each outcome means for the stage. That is why the same outcome always has the same effect, whoever records it and wherever they record it from.
- 03
Understand which outcomes are cautions
A no-show and a declined finance application are recorded as caution, never as loss. People whose week went wrong still buy cars, and a bank saying no is not a customer walking away.
- 04
Read the history for the reason, not just the move
Every stage change records who moved it and why. The history distinguishes a sales executive's own words from an outcome code from a note the system wrote — three different things, kept apart.
Worth knowing
A no-show deliberately does not reset the contact clock. Nobody spoke to anybody, and recording it as contact would make a silent customer look freshly worked.
Some things raise no outcome at all. A trade-in appraisal asserts nothing about the sale — plenty of people are simply finding out what their car is worth.