How do I stop sales leads falling through the cracks?

If sales leads keep disappearing, start with three questions:

WHO OWNS IT?
WHAT STATE IS IT IN?
WHAT HAPPENS NEXT?

Every genuine sales opportunity should have:

• AN OWNER
  Someone or something responsible for moving it forward.
• A STATE
  A clear understanding of where it currently is.
• A NEXT ACTION
  Something that should happen, with a time attached where appropriate.

If any of those is missing, you've created somewhere for the lead to disappear.

Leads rarely disappear dramatically

Nobody usually announces:

"I've decided we're going to completely forget about this £12,000 opportunity."

It happens much more quietly.

An enquiry arrives.

Someone replies.

The customer says:

"Sounds good. Come back to me next week."

Someone thinks:

"Yep, I'll remember that."

Then:

• another enquiry arrives,
• a customer calls,
• a meeting runs over,
• somebody needs a quote,
• something breaks,
• Friday arrives,
• and nobody remembers.

Three weeks later someone asks:

"Whatever happened to that company from Richmond?"

And everyone stares at each other.

That's how leads fall through the cracks.

The problem is often memory

A surprising amount of small-business sales runs on:

SOMEONE REMEMBERING.

• Remember to reply.
• Remember to follow up.
• Remember to update the CRM.
• Remember what the customer said.
• Remember who was dealing with it.
• Remember when they asked you to come back.
• Remember that you promised something.

Humans are very useful in sales.

Being the business's reminder system is not necessarily the best use of them.

YOUR SALES PROCESS SHOULD REMEMBER THE LEAD.

Start with the three things

For every active lead, you should be able to answer:

• 1. OWNER Who is responsible?
• 2. STATE What's happening?
• 3. NEXT ACTION What happens next?

Let's look at each one.

1. Every lead needs an owner

An enquiry sent to:

sales@company.co.uk

doesn't necessarily have an owner.

It's in an inbox.

That's different.

Likewise:

"I think James was dealing with that."

isn't a reliable ownership model.

For every genuine lead, somebody should be responsible for ensuring it reaches the next appropriate state.

That might be:

• Sarah,
• James,
• the sales team,
• a specific account owner,
• or initially an automated workflow.

The important thing is that ownership is explicit.

Shared ownership can become no ownership

Imagine:

three people receive the same website enquiry.

Each assumes somebody else will answer.

Nobody does.

The business has successfully achieved:

MAXIMUM VISIBILITY.

and:

ZERO OWNERSHIP.

A simple routing rule may fix this.

For example:

• New website enquiry
• Assign based on service.
• Notify owner.
• Create response task.
• Escalate if untouched.

No AI required.

Ownership can change

The owner doesn't need to remain the same throughout the process.

For example:

• NEW ENQUIRYSales admin.
• QUALIFIEDSalesperson.
• TECHNICAL QUESTIONTechnical specialist.
• COMMERCIAL DISCUSSIONSalesperson.

The important thing is that the lead doesn't enter a state where:

NOBODY CURRENTLY OWNS THE NEXT MOVE.

2. Every lead needs a state

"Open" isn't always enough.

What is actually happening?

For example:

• NEW Nobody has reviewed it yet.
• NEEDS INFORMATION Waiting for customer details.
• QUALIFIED Good fit, ready for sales conversation.
• MEETING BOOKED Conversation scheduled.
• PROPOSAL IN PREPARATION We owe them something.
• PROPOSAL SENT Customer has it.
• WAITING FOR CUSTOMER They owe us something.
• FOLLOW-UP DUE We need to act.
• HUMAN REVIEW Something unusual needs attention.
• CLOSED Won, lost or genuinely finished.

The exact states depend on your business.

But they should mean something.

Don't create 37 CRM stages

The answer isn't to create a state for every possible event.

You don't need:

• Proposal Sent Tuesday
• Proposal Sent Wednesday
• Proposal Sent But Customer Seems Quite Positive
• Proposal Sent And Dave Thinks They're Probably Going Ahead

Keep states useful.

A state should help answer:

WHAT IS HAPPENING NOW?

and often:

WHO NEEDS TO DO SOMETHING?

State is not probability

This distinction matters.

Suppose a customer says:

"This looks good. I just need Finance to approve it."

The state might be:

WAITING FOR FINANCE APPROVAL.

That's useful.

Changing the CRM to:

90% likely to close

is a different judgement.

The first describes what's happening.

The second predicts an outcome.

For preventing lost leads, knowing the actual state is usually more useful than pretending we know the future.

3. Every lead needs a next action

This is probably the most important one.

A lead can have:

• an owner,
• a perfect CRM record,
• a beautifully defined stage,
• and still go nowhere.

Ask:

WHAT HAPPENS NEXT?

For example:

• ACME
  State: Proposal sent.
  Next action: Follow up Thursday.
• NORTHSTAR
  State: Waiting for technical information.
  Next action: Tom to confirm API compatibility by Tuesday.
• WESTFIELD
  State: Customer reviewing.
  Next action: Customer asked us to contact them after 25 September.
• BRIDGE & CO
  State: New enquiry.
  Next action: Sarah to review today.

Now the process has somewhere to go.

"Waiting" still needs a next action

This catches businesses out.

CRM says:

WAITING FOR CUSTOMER.

Fine.

For how long?

Forever?

If the customer never responds, when does somebody look again?

A better record might say:

Now waiting is an actual state.

Not a black hole.

A lead without a next action is already at risk

This is worth turning into a rule:

ACTIVE LEAD + NO NEXT ACTION = NEEDS ATTENTION.

You don't need AI to detect that.

A CRM report can do it.

An automation can do it.

A dashboard can do it.

The important thing is that somebody stops relying on memory.

Start with a simple morning view

Imagine opening the sales system and seeing:

That's more useful than a dashboard containing 17 graphs about pipeline activity.

It tells you:

WHAT NEEDS TO HAPPEN.

You don't need AI for most of the foundation

This is important.

These rules are predictable:

• New lead must have an owner. Automation.
• Active opportunity must have a next action. Rule.
• Follow-up date has passed. Automation.
• New website enquiry hasn't been reviewed within two hours. Automation.
• Proposal sent but no next action exists. Rule.

None of that needs generative AI.

BORING AUTOMATION IS VERY GOOD AT BORING RULES.

Use it.

So where does AI help?

AI becomes more useful when the problem isn't:

DID SOMETHING HAPPEN?

but:

WHAT HAPPENED?

For example:

A customer replies:

"Thanks, we've discussed this internally. The project is still happening, but our office move has taken priority. Can we pick it back up in January?"

A rule can detect:

EMAIL RECEIVED.

AI may help interpret:

• Project not lost.
• Timing changed.
• Customer asked to pause.
• Follow-up should move to January.
• Reason: office move.

Now the workflow can potentially prepare:

That is where interpretation becomes useful.

The system should understand replies before continuing follow-up

This is particularly important.

Suppose your automated sequence says:

• DAY 5 Follow up.
• DAY 10 Follow up.
• DAY 20 Follow up.

But on Day 7, the customer replies:

"We're interested, but please don't chase me until October."

A sensible system stops the sequence.

It doesn't send on Day 10:

"Just bumping this to the top of your inbox!"

That isn't persistence.

It's evidence your systems aren't listening.

Follow-up should respond to state

Think:

STATE → NEXT ACTION.

Not:

TIME PASSED → EMAIL.

Time can trigger a check.

But the next action should reflect what's actually happening.

For example:

• PROPOSAL SENT
  No reply. → Follow up.
• PROPOSAL SENT
  Customer asked to wait. → Wait.
• PROPOSAL SENT
  Customer asked technical question. → Answer / escalate.
• PROPOSAL SENT
  Customer declined. → Close appropriately.
• PROPOSAL SENT
  Customer complained. → Human.

Same original state.

Very different next action.

Related: Can AI follow up sales leads automatically?

Don't let leads disappear between systems

Another common crack is the gap between tools.

• Website enquiry lands in email.
• Email gets answered.
• CRM never gets updated.
• Meeting gets booked.
• Calendar knows.
• CRM doesn't.
• Proposal gets sent.
• Proposal software knows.
• CRM still says: Discovery.
• Customer replies.
• Information stays in email.

Now no single system understands the state of the opportunity.

The lead hasn't disappeared.

THE CONTEXT HAS FRAGMENTED.

Map the handovers

Look for places where one system or person hands work to another.

For example:

• WEBSITE → SALES Did the lead get created?
• SALES → TECHNICAL Did somebody accept ownership?
• MEETING → CRM Were decisions recorded?
• PROPOSAL → FOLLOW-UP Was a next action created?
• EMAIL → OPPORTUNITY Did the customer's response change the state?
• PERSON A → PERSON B Does the new owner know what happened?

These are common places for leads to fall through the cracks.

Every handover needs confirmation

Don't assume:

"I sent it to Tom."

means:

"Tom now owns it."

A good handover might include:

Now the process has continuity.

The salesperson shouldn't have to reconstruct the story

Imagine somebody takes over an opportunity.

They shouldn't need to search:

• CRM,
• email,
• calendar,
• notes,
• proposal,
• and three Slack messages

to understand what is happening.

The system should be able to show:

• WHERE ARE WE?
• WHAT HAPPENED?
• WHAT ARE WE WAITING FOR?
• WHAT HAPPENS NEXT?

That is the useful context.

One simple rule can expose a lot

Run this query across your active opportunities:

SHOW ME EVERY ACTIVE LEAD WITH NO NEXT ACTION.

You may discover quite a lot.

Then:

SHOW ME EVERY OVERDUE NEXT ACTION.

Then:

SHOW ME EVERY UNASSIGNED LEAD.

Then:

SHOW ME EVERY LEAD WAITING FOR SOMEONE FOR MORE THAN X DAYS.

You don't need sophisticated AI to discover basic process gaps.

Then look for the interpretation gaps

Once those foundations work, ask:

Where does somebody still have to read information and decide what changed?

Examples:

• customer replies,
• meeting notes,
• new enquiries,
• technical questions,
• proposal feedback,
• requests to wait,
• commercial objections.

That's where AI can start helping.

A practical lead-continuity workflow

Here's a stronger version.

• NEW LEAD
• OWNERAssign responsibility.
• UNDERSTANDWhat does the customer need?
• STATEWhere is the opportunity?
• NEXT ACTIONWhat happens next?
• DO THE WORKHuman, automation or AI.
• CHECKDid it happen?
• UPDATE STATEWhat changed?
• CREATE NEXT ACTIONWhat happens now?
• CONTINUE OR CLOSE

The important bit is the loop.

EVERY COMPLETED ACTION SHOULD CREATE A NEW STATE OR A NEW NEXT ACTION.

Until the opportunity is genuinely finished.

The sales process is a loop, not a list

A CRM pipeline often looks like:

Lead → Qualified → Meeting → Proposal → Won.

Lovely.

Real life looks more like:

Lead → Question → Response → Missing information → Customer replies → Meeting → Technical question → Internal review → Proposal → Customer asks to wait → Follow-up → Revised proposal → Finance → Negotiation → Decision.

That's why next-action discipline matters.

The process moves through many small states before the big stage changes.

What about long sales cycles?

This becomes even more important.

If the buying process takes:

• three months,
• six months,
• or a year,

memory is an increasingly poor system.

A lead may be completely legitimate but currently:

• waiting for budget,
• waiting for a contract to end,
• waiting for a project,
• waiting for a board meeting,
• waiting for a particular month.

Don't mark it dead because nothing happened this week.

Record:

WHY WE'RE WAITING

and:

WHEN WE SHOULD LOOK AGAIN.

"Not now" isn't always "no"

Suppose a customer says:

"We definitely can't do this this financial year. Speak to us in April."

Bad system:

LOST.

Better:

Now the system remembers what the salesperson shouldn't have to.

But don't keep zombie leads forever

The opposite problem exists too.

Your CRM contains 4,000 "active opportunities" because nobody wants to close anything.

Some haven't responded since 2023.

That's not a pipeline.

That's an archaeological site.

Define what happens when:

• follow-up attempts are exhausted,
• the customer explicitly declines,
• the business is no longer a fit,
• the project disappears,
• or no meaningful next action exists.

Closing something properly is part of good lead management.

AI shouldn't decide that silently either

AI can help identify:

But:

FLAGGING

is different from:

CLOSING.

Depending on the business and opportunity, a person may still need to decide.

Again:

capability isn't authority.

What should happen when a lead is overdue?

Don't simply send another email.

First ask why it is overdue.

Perhaps:

• the salesperson forgot,
• the customer replied elsewhere,
• a meeting happened,
• the project paused,
• somebody left,
• or the next action is no longer appropriate.

A useful workflow might do:

• OVERDUE ACTION
• Check recent activity.
• Something changed?YES → Update state. NO → Prepare next action.
• Uncertain?YES → Human review.

That's more useful than automatically chasing everything.

Escalation should be part of lead management

Some leads fall through the cracks because nobody knows what to do with them.

For example:

• unusual requirement,
• large opportunity,
• technical uncertainty,
• pricing exception,
• complaint,
• procurement question,
• legal query.

The lead isn't forgotten.

It's stuck.

So give it a route:

• STOPDon't guess.
• EXPLAINWhat is blocking progress?
• ESCALATEWho needs to deal with it?

Then ownership transfers explicitly.

A useful "stuck" view

Your system could show:

That is far more actionable than:

Pipeline value: £84,000.

Don't automate bad follow-up

There is a temptation to solve missed leads with:

MORE EMAIL.

If leads aren't being followed up, you can automate:

• Day 3.
• Day 7.
• Day 14.
• Day 21.
• Done.

Except the real problem may be:

• nobody knows whether the lead is good,
• the customer already replied,
• the quote was wrong,
• the customer asked to wait,
• or nobody owns the opportunity.

Automating emails doesn't fix those things.

FOLLOW-UP IS A PROCESS, NOT A SEQUENCE.

What about small businesses without a CRM?

You still need the three things:

• OWNER.
• STATE.
• NEXT ACTION.

The system doesn't have to begin as a giant CRM implementation.

But those things need to live somewhere reliable.

If your current system is:

inbox + notebook + memory,

you've created multiple places for opportunities to disappear.

Even a simpler structured system is better if everybody actually uses it.

What about businesses with a CRM that nobody updates?

That's a different problem.

Buying a new CRM may not solve it.

Ask why people aren't updating the existing one.

• Too many fields?
• Too much duplication?
• Does information already exist somewhere else?
• Does the CRM ask people to record things nobody uses?
• Is updating it genuinely useful?

This is where AI may help reduce the admin around keeping the CRM current.

But first:

REMOVE THE CRM WORK THAT DOESN'T NEED TO EXIST.

Then automate or use AI around what remains.

Create one rule for every active opportunity

This is the rule I'd put on the wall:

NO ACTIVE LEAD WITHOUT A NEXT ACTION.

That next action might be:

• Call Tuesday.
• Send proposal Thursday.
• Wait until January.
• Get technical answer.
• Review pricing.
• Customer to provide dimensions.
• Close if no response after final review.

But it should exist.

If it doesn't:

the system should notice.

Add the second rule

NO NEXT ACTION WITHOUT AN OWNER.

"Follow up Tuesday" isn't enough if nobody knows who is responsible.

And:

NO OWNER WITHOUT A CLEAR STATE.

Because a person can't move the opportunity properly if nobody knows what's happening.

So:

OWNER → STATE → NEXT ACTION.

Keep the three together.

Who should remember the next action?

Ideally:

THE SYSTEM.

Not the salesperson.

The salesperson should decide things the system can't.

The system can remember:

• dates,
• promises,
• tasks,
• states,
• owners,
• and overdue actions.

This is one of those areas where software is considerably better than humans.

Let it be.

Where AI becomes agentic

Now we can see the step beyond reminders.

Traditional software can say:

Follow up Acme today.

An AI assistant might say:

Here's a draft follow-up.

An agentic workflow can potentially:

• notice follow-up is due,
• check whether anything changed,
• read the relevant conversation,
• understand the current state,
• decide whether follow-up is still appropriate,
• prepare the action,
• act within its authority,
• record what happened,
• and create the next action.

That's a much more interesting job.

Not:

SEND EMAIL.

But:

MAKE SURE THIS OPPORTUNITY DOESN'T QUIETLY STOP MOVING.

And sometimes the correct action is nothing

Suppose the customer said:

"Our board meets on 15 October. Please contact me afterwards."

On 1 October, the agent sees no recent activity.

Does it follow up?

No.

The correct next action is already:

WAIT UNTIL AFTER 15 OCTOBER.

A good sales system doesn't maximise activity.

It maintains appropriate continuity.

How do you know whether you've fixed the problem?

Measure:

• UNASSIGNED LEADS How many?
• ACTIVE LEADS WITHOUT NEXT ACTION How many?
• OVERDUE NEXT ACTIONS How many?
• TIME TO FIRST USEFUL RESPONSE Improving?
• LEADS STUCK IN ONE STATE Why?
• FOLLOW-UP COMPLETED Appropriately?
• LEADS CLOSED WITHOUT CLEAR REASON Why?
• HUMAN ADMIN How much time is spent maintaining the system?
• ERRORS Are automated actions being corrected?

These tell you more than:

EMAILS SENT.

A weekly sales health check

You shouldn't need a giant meeting.

Ask:

• WHAT CAME IN? New opportunities.
• WHAT MOVED? State changes.
• WHAT IS STUCK? Blocked opportunities.
• WHAT IS OVERDUE? Missed actions.
• WHAT HAS NO OWNER? Assignment problem.
• WHAT HAS NO NEXT ACTION? Continuity problem.
• WHAT SHOULD BE CLOSED? Pipeline hygiene.

That's a useful sales review whether AI is involved or not.

The simplest version you can implement tomorrow

If leads are currently being forgotten, do this first:

For every active lead, record:

• OWNER Who is responsible?
• STATE What's happening?
• NEXT ACTION What needs to happen?
• WHEN When should it happen?

Then create views for:

• Unassigned
• No next action
• Overdue
• Stuck

You may fix a surprisingly large part of the problem before AI appears anywhere.

Then automate the predictable parts

For example:

• New enquiry → Assign.
• Proposal sent → Create follow-up task.
• Next action overdue → Flag.
• Lead unassigned → Alert.
• No activity for defined period → Review.

Still no AI required.

Then add AI where interpretation matters

For example:

• Customer email → What changed?
• New enquiry → What do they need?
• Meeting → What was agreed?
• Follow-up due → Is follow-up appropriate?
• Opportunity stuck → What appears to be blocking it?
• CRM update → What factual changes can we extract?

Now AI has a real job.

Then consider agentic behaviour

Once the workflow is reliable:

• WATCHNotice what needs attention.
• UNDERSTANDInterpret what happened.
• RECOMMENDSuggest next action.
• PREPAREPrepare the work.
• ACT WITH APPROVALHuman confirms.
• ACT WITHIN LIMITSRoutine work happens.
• ESCALATEAnything uncertain comes back.

That's how you move from:

REMIND ME ABOUT LEADS

to:

HELP KEEP THE SALES PROCESS MOVING.

So, how do you stop sales leads falling through the cracks?

Don't start by buying an AI sales agent.

Start by making sure every genuine lead has:

• AN OWNER Who is responsible?
• A STATE What's happening?
• A NEXT ACTION What happens next?

Then make the system responsible for remembering those things.

Use ordinary automation for:

• assignment,
• dates,
• reminders,
• rules,
• and predictable actions.

Use AI where someone needs to:

• understand,
• interpret,
• summarise,
• or decide what information means.

Keep people where:

• judgement,
• relationships,
• commercial decisions,
• or unusual situations

make them valuable.

Because leads rarely disappear because the business needed more AI.

They disappear because somewhere in the process:

NOBODY OWNED WHAT NEEDED TO HAPPEN NEXT.

Fix that first.

Then use technology to make sure it stays fixed.

Quick answers

Or put the whole thing together: