What lead statuses can hide

Open your CRM and look at the pipeline. Some number of records sit in working, some in contacted, and some were closed out as lost last month. Now open twenty of them and read what actually happened. On most teams, the gap between the status and the conversation is wider than anyone expects, and it is not because anybody set out to lie.

A status is a claim about a customer, written by the person it grades

That is the whole problem in one sentence. The rep who owns the record chooses the status, and the status feeds the report their manager reads on Monday. Nobody has to be dishonest for that arrangement to produce optimistic data. It is enough that the categories are vague and the person filling them in is busy and would rather not explain a pile of dead records.

Three statuses carry most of the damage.

Working

Working is the most comfortable word in the system. It sounds like activity and it commits to nothing. A record can sit in working for six weeks while the only thing that happened was one unanswered call in week one.

The harm is not the label. It is what the label does to your read of the team. A manager looking at a healthy count of records in working believes there is a pipeline. What is actually there may be a queue of customers nobody has spoken to since the first attempt, and every week that passes makes them colder.

The test is a date. If a record is genuinely being worked, something is scheduled to happen to it, and that something has a date and a name attached. A record in working with an empty next step field is parked, and it should be treated as parked: either somebody schedules the next contact today, or it moves out of the pipeline. One rule, easy to check, and it will shrink your working count right away. That is the point.

Contacted

Contacted is where an attempt gets promoted into a conversation. The rep called, it rang out, they left a voicemail and sent a text, and the record gets marked contacted. In plain English the customer has not been contacted. Somebody tried to contact them.

The distinction matters because contacted usually ends the response clock. A lead that arrives at 9:10 and is marked contacted at 9:14 looks like a fast response. If nobody ever spoke to that customer, the speed is a measurement of dialing, not of reaching anyone.

Split it. Attempted covers calls with no answer, voicemails and texts with no reply. Contacted means a two-way exchange: the customer spoke, replied to a text, or answered an email. Reps will push back, and the honest answer is that attempted is not a failure. It is the normal outcome of many first attempts, and it should be visible as such.

Then watch what happens to your counts. Teams that make this split often find leads that were marked contacted on day one, never reached at all, and quietly dropped by day three.

Lost

Lost is the word that closes the file, and it gets used for two completely different things. Sometimes the customer bought elsewhere, told you no, or stopped shopping. Sometimes the rep ran out of ideas and the record was tidied away. The second case is written down exactly like the first.

Look at the reasons in your own system. If most closures come back as “not interested,” “stopped answering” or “no response,” you are not reading customer behavior. You are reading rep behavior. A customer who stops answering has not told you anything except that the last three messages did not work, which is a very different fact from “bought elsewhere.”

Make the rep choose a reason from a short list, and keep the list honest: bought elsewhere, bought from us, timing changed, not a fit, budget, and unreachable after a defined effort. That last one makes the effort visible. Unreachable after six attempts across two channels over fourteen days is a real closure. Unreachable after two calls on the same afternoon is a rep who gave up, and the record should go back into the pipeline or to somebody else.

This matters in money terms because a mismarked lost record is a customer who may still be shopping, sitting in a folder nobody opens. Synthetic example: Renee, who runs a team of eight setters at an appointment-setting agency, pulled sixty records closed as unreachable in the previous quarter and found a handful of customers who had replied to a text days after their record was closed. Nobody saw the replies, because the records were already out of the queue.

Define every status by an event the customer took part in

That is the rule that fixes all three at once. A status should describe something the customer did, not something the company did.

• New: the lead exists and nobody has attempted it yet.
• Attempted: one or more outbound attempts, and no response from the customer.
• Contacted: the customer responded. They spoke, replied or wrote back.
• Meeting set: a specific day and time the customer agreed to, on the calendar.
• Working: the customer has responded, and there is a dated next step with an owner.
• Closed: a reason from the list, with the effort recorded.

Every one of those can be checked against something. A manager can ask to see the response that moved a record from attempted to contacted, or the effort behind a closure. A status nobody can check is a status that will drift.

Three checks that find the drift in an afternoon

1. Working with no dated next step. Sort the pipeline by next step date and look at the empty ones. Every one of those is parked, whatever the status says.
2. Contacted with nothing inbound. Take twenty records marked contacted and look for a single inbound call, text or email from the customer. The ones with nothing inbound were attempts.
3. Lost with thin effort. Take twenty closures from last month, count the actual attempts and the channels used, and look at the dates. Two calls on one afternoon is not an effort.

Do not run all three as a one-time audit and present the results to the team as a scandal. Run one of them every week on a small sample and handle it rep by rep. The goal is a team where statuses mean something, not a memorable meeting.

The definitions are not the whole fix

If your pay plan or your Monday report rewards a full pipeline, reps will keep records in working, and no definition survives that. The same is true in reverse: if lost records get audited hard and working records do not, everything stays in working forever.

So pair the definitions with two changes. Make the report show working records with a dated next step, not working records overall, so an inflated pipeline stops looking good. And make closing a record with a real reason easy and unpunished, so the rep has somewhere honest to put a customer who is genuinely gone.

What to do with the pile you already have

You are going to find many records in the wrong status. Do not try to fix all of them.

1. Take the most recent ninety days only. Beyond that, the contact information has often gone stale anyway.
2. Pull the records in working with no next step and no customer response in the last month, and give each one a real attempt before anything else.
3. Pull closures marked unreachable and check for any inbound message that arrived after the record was closed. Those are live customers.
4. Recategorize what is left under the new definitions, and accept that the pipeline number is going to drop.
5. Tell the team the number dropped because the definitions changed, before somebody else explains it for you.

What to do this week

1. Write the six status definitions on one page and get every manager to agree on them before the team sees them.
2. Split contacted from attempted in your system, and explain why attempted is not a failure.
3. Run the empty next step check today and clear it before the end of the week.
4. Replace your closure reason list with the short honest one, including effort.
5. Put one of the three checks on a weekly recurring slot and keep it small.