Lead routing works when every new opportunity gets an owner, a reason for the assignment, and a dated next action. The goal is not to create a complex scoring model; it is to make the first decision visible and reviewable.
Outcome and scope
This workflow is for a 5-to-50-person sales team handling inbound or referred opportunities. It covers intake, qualification, assignment, and first follow-up. It does not decide whether a lead will buy or guarantee a response from a prospect.
Workflow map
- Capture: record source, contact, company, request, and received time.
- Check: remove duplicates and confirm that the request fits the team’s scope.
- Assign: choose an owner using a documented rule such as territory, segment, or round robin.
- Accept: the owner confirms the record and sets the first next action.
- Review: inspect unowned, overdue, and rejected records each week.
Setup steps
- Define what counts as a new lead and what evidence is required before assignment.
- Choose one primary routing rule and write the exceptions separately.
- Make owner, received date, source, qualification status, and next action visible.
- Set a service target as an internal operating measure, not a promise to every prospect.
- Create a queue for unassigned or rejected records with a named reviewer.
The Pipedrive sales workflow guide is a product-specific reference; adapt the workflow to the team’s actual ownership and evidence rules.
Example fields or pipeline table
| Field | Example | Review question |
|---|---|---|
| Received time | 2026-08-14 09:20 | Is the queue ordered by a known fact? |
| Routing rule | West region, round 2 | Can another person reproduce the assignment? |
| Owner | Named teammate | Has someone accepted responsibility? |
| Next action | Read request and send two clarifying questions | Is the action concrete and dated? |
| Reject reason | Duplicate or outside scope | Can the team review the rule later? |
Failure modes
- Sending every lead to the most available person without recording the rule.
- Leaving a record assigned but not accepted.
- Using a score as a substitute for reading the request.
- Deleting rejected or duplicate records instead of preserving the reason.
- Measuring speed while ignoring ownership and response quality.
Metrics to review
Review unassigned lead count, time to assignment, time to acceptance, overdue first actions, duplicate rate, rejection reasons, and distribution by owner or source. Keep these process measures separate from revenue outcomes so the dashboard does not imply that routing creates a sale.
FAQ
Should round robin be the only routing rule?
It can be a useful default, but territory, language, product knowledge, or account ownership may justify a documented exception.
How long should a lead stay unassigned?
Set a team-specific review target based on volume and coverage. Escalate the queue when the target is missed rather than silently changing ownership.
Should rejected leads be deleted?
No. Keep a factual reject reason and retain the record according to the team’s data policy so the rule can be reviewed.
Leave a Reply