The short answer
Use stages that describe real customer decisions and give each active lead an owner and a next action. Start with New inquiry, Contacting, Estimate or consultation, Job booked and Closed. Add stages only when they change what the team does. Keep sales status, appointment status and job completion distinct.
What should each pipeline stage mean?
Write a one-sentence entry rule for each stage. If two team members disagree about whether a lead is booked, the stage needs a clearer definition. A board becomes useful when the labels tell someone what has happened and what needs to happen next.
Contact attempts can be tracked as a count or a small set of stages. Avoid adding a lane for every possible note. Keep the layout readable enough to spot untouched inquiries and estimates waiting on a decision.
| Stage | Entry rule | Next action |
|---|---|---|
| New inquiry | A customer submitted a request | Check fit and assign contact |
| Contacting | An owner is trying to reach the customer | Record the next attempt |
| Estimate sent | A real scope or price was delivered | Answer questions and follow up |
| Job booked | The customer and team confirmed the work | Send appointment details |
| Job complete | Completion is verified | Thank the customer and request feedback |
What belongs on the lead record?
Keep the information the next person needs: requested service, source, contact history, assigned owner and next action date. Custom fields should answer practical questions. For a detailing lead, vehicle size may matter; for a landscaping inquiry, property details may matter.
Do not collect a field merely because the software supports it. Every required question adds work for customers or staff. Start with the smallest useful set and add fields when a repeated decision genuinely needs them.
Can a lead move backward?
Yes. People correct accidental moves and customers reopen decisions. Record the transition and update the current stage rather than preventing a legitimate correction. If an inquiry moves from Contacting back to New inquiry, the current-stage totals should reflect that move.
Keep activity history separate from the current board. A historical contact attempt still happened even if the current status changes. For conversion reporting, define whether you mean leads currently in a stage, leads that ever reached it, or confirmed outcomes. Those are different measures.
- Preserve the timeline of stage changes.
- Update current-stage counts immediately.
- Re-evaluate queued automations against the corrected state.
- Avoid replaying a one-time acknowledgment just because someone corrected a lane.
How do you keep the pipeline useful after setup?
Review leads with no owner, no next action or an overdue task. Ask why estimates are waiting. Close records that have a known outcome, and capture a reason when practical. A board full of forgotten leads can make every stage count look impressive without helping the team.
Connect automation to stable business events. Use a confirmed booking for appointment messages and verified completion for thank-you messages. If the stage changes before a queued email sends, check it again instead of blindly sending an outdated message.
Common questions
Do all industries need the same pipeline?
No. The underlying decisions are similar, but a detailing booking, a landscape estimate and a repair inspection have different entry rules. Configure the labels and triggers around those differences.
Should a sales pipeline replace job scheduling?
Only where the software and your actual process support that scope. A clear handoff to an existing operational system is often better than pretending a sales lane manages the whole job.
About this guide
Written for service-business owners by WellRun. The workflows and examples are practical recommendations; example messages are illustrative, not client results. Actual setup depends on your services, team and connected tools.
Spotted something that needs correcting? Email WellRun.