Call outcome, lead stage and queue state are three different things
Most CRMs have one status field doing three jobs. That is where reporting goes to die.
If you take one idea from the whole tutorial library, take this one, because it is the reason pipeline reports in most CRMs cannot be trusted.
Three different questions get asked about a contact. How did that phone call go? Where is this person in their relationship with us? Should we be calling them right now? Most systems answer all three with one status field, and the moment you do that, none of the answers is reliable.
Here they are three separate things, and only one of them is something you type.
Reference
Call outcome describes one attempt
Set by whoever made the call, at the end of it. Eight values. It is about the phone call, not about the person — "no answer" says nothing whatsoever about whether they want to buy.
Lead stage describes the person's lifetime
New, Contacted, Qualified, Won, Lost, DND, Wrong number. Editable on the record and from the call logger. Terminal values really are terminal.
Queue state is derived and read-only
Never offered for hand entry, anywhere. It is a consequence of stage and activity — the calling list is computed from them, not maintained.
See why conflating them breaks reporting
If "no answer" were a stage, somebody you failed to reach three times would look like a different kind of person from somebody you reached once. They are not. One of those facts is about your dialling; the other is about them.
Use the right one when you report
Outcomes answer "how is our calling going". Stages answer "what does our pipeline look like". Ask a stage question of outcome data and you get an answer that is confidently wrong.
Notice how the three interact
An outcome can move a stage. A stage determines queue state. But it never runs the other way — you cannot set queue state, and a stage change is not an outcome.
Put it to use
Ask your team what "contacted" means. If some people mean "I dialled them" and others mean "I spoke to them", you have the conflation this whole distinction exists to prevent — and it is worth ten minutes to fix.
The parts people get wrong
- The three attempt-only outcomes — no answer, busy, voicemail — deliberately leave the stage alone. That is this distinction working.
- Because queue state is derived, there is no list to maintain and nothing to go stale.