CRM and contacts

Designing Pipeline Stages for Phone Sales That Reps Will Use

How to design a short, clear pipeline for phone sales: define each stage by what has happened, set exit rules, track stale deals and learn from lost ones.

Call editorial team · Published · 6 min read

A pipeline is a map of how a person goes from first contact to a decision. For a phone team it also works as a to-do list: whoever sits in a stage needs a particular next call. A pipeline with too many stages becomes a place where deals go to be forgotten; one with vague stages makes forecasts unreliable. This guide shows how to design stages that are short, clear and useful for people who sell by phone.

A sales team member moving cards across a pipeline board on a screen
Illustrative image

It is part of a series on CRM for phone teams. If you are choosing a system, start with What a Phone Team Needs from a CRM. For the wider sales process, see Building a Phone Sales Pipeline and Writing a Sales Call Script.

How many stages, and what they mean

Most phone sales processes need between five and seven stages, including the end states. Fewer than five hides information; more than seven makes people guess. Each stage should answer one question: what has just become true about this person?

A simple phone-sales pipeline

  1. NewA lead exists but nobody has spoken to them.
  2. ContactedA real conversation has happened.
  3. QualifiedThey have a need, a budget range and a decision path.
  4. ProposalA specific offer or quote has been sent.
  5. WonThey said yes.
  6. LostThey said no, or the chance has gone.

Your own stages will differ. A business selling a simple service by phone may skip proposal. One with long evaluations may add a stage for a trial or a demo. What matters is that each stage describes a fact, not a hope.

Write the entry and exit rule for each stage

Vague stages are the usual reason pipelines fail. If one rep puts a person in Qualified after a friendly chat and another waits for a confirmed budget, the totals mean nothing. For each stage, write what must be true to enter, and what must be true to leave.

Vague versus clear stage definitions

VagueClear
ContactedWe have tried to reach themWe have spoken to them and know who decides
QualifiedThey seem interestedThey have a stated need, a rough timeline and the authority or access to decide
ProposalTalking about pricesA written offer has been sent and a date set to follow up
LostWent quietThey declined, or three follow-ups over an agreed period got no answer

Keep the list of rules short enough to fit on one page and put it where reps can see it. Review it after the first month, since the real world will show you where the definitions fail.

Probabilities and expected age

Two numbers per stage turn a pipeline into something you can plan with. The first is a probability: roughly how often a deal in this stage ends up won, based on your own history. The second is an expected age: how long deals normally sit there before moving on. Together they give a weighted forecast and a list of stale deals.

Start with honest estimates, then replace them with your actual numbers as history builds. A forecast built on stage probabilities is an estimate of your own process, not a promise of income, and it will be wrong when the mix of deals changes. Use it to compare weeks and spot trouble, not to commit to exact figures.

Rules for moving deals

Movement should follow what happened on calls. After each call the agent decides whether the situation changed. If yes, they move the stage and set a next step. If not, they leave the stage alone and record the next attempt. Avoid moves made only to look busy.

Record why deals are lost

A loss reason is the most valuable field in a pipeline. Offer a short list such as price, timing, chose a competitor, no budget, no response and not a fit, with an optional competitor name. Over a few months, ranking reasons by deal value shows where to improve the script, the offer or the lead source. Make the reason required when closing a deal as lost, and keep the list short.

What is different for phone sales

Phone sales moves faster and in smaller steps than a long enterprise cycle, so stages should reflect call outcomes. A call that ends with a promised callback is a next step inside a stage, not a new stage. Record callback times precisely, because a callback missed by a day has a lower chance of a sale than one made on time. Speed to first call matters too: a new lead that waits a day has usually cooled, so monitor how long leads take to get their first call.

See Routing New Leads to the Right Person for who should call first and Quotes and Follow-Up Calls for the proposal stage.

A hypothetical example: a small team selling service contracts by phone starts with nine stages, and reps cannot agree where a person who asked for a price belongs. They cut to six, write one sentence of entry and exit rule for each, and the arguments stop. Their forecast is not suddenly perfect, but it is now comparable from week to week, which is what lets them improve it.

Pipeline health check

  • Every stage has an entry and an exit rule
  • Every open stage has a probability and an expected age
  • Every active deal has an owner and a next step
  • Stale deals reviewed weekly
  • Lost deals have a reason
  • Stage names are used the same way by every rep

Using pipeline stages in Call

In Call, the Prospects page under Campaigns shows your contacts as a table or as a pipeline board. The stages are New, Contacted, Qualified, Proposal, Won, Lost and Do not call. On the board, drag a card to another column; each column shows its count and total deal value. In the table, change a stage from the pill in each row. On a contact page, Mark won and Mark lost ask for a reason and, for a loss, an optional competitor.

The Revenue page under Campaigns turns this into numbers: a weighted forecast that multiplies open deal values by each stage probability, a count of renewals due in the next sixty days, speed to lead over the last thirty days, stale deals that have stayed in a stage longer than its expected age, and a ranking of loss reasons by value. Stage probabilities and expected ages come from your pipeline stages in CRM setup. These figures show only what your team records, so a contact with no deal value adds nothing to the forecast.

Frequently asked questions

How many pipeline stages should we have?

Usually five to seven including won and lost. Each stage should mark a clear change in what you know about the person.

Should a promised callback be its own stage?

Usually not. A callback is a next step within a stage. Track it as a dated task so it is not forgotten.

How do I set stage probabilities?

Start with estimates, then use your own history of how many deals from each stage were won. Update them regularly.

What counts as a stale deal?

One that has stayed in a stage longer than that stage's expected age. Set the expected age from how long healthy deals normally take.

Should reps be able to skip stages?

Allow it when the situation really jumped, such as a ready buyer, but require the next step to be recorded. Frequent skipping may mean the stages need redesign.

Why record lost reasons?

They show where deals leak. After a few months you can rank reasons by value and fix the biggest one, in script, offer or lead source.

Move contacts through pipeline stages and read the forecast in Call

In the demo console you can try incoming calls in a simulation.

Related guides