# A lead follow-up system you can check: one owner, one next task, one weekly report

https://salesbond.app/blog/lead-follow-up-system-owner-next-task-report/
Published: 2026-10-15 · Updated: 2026-10-26

A lead follow-up system needs three things in the CRM: one owner for every lead, one next task with a date, and a weekly report of leads with no touch in the last N days. Lead follow-up here means every contact after the first reply, until the lead converts or is closed. Templates, cadences and reminders all hang off those three. If any one of them is missing, the follow-up depends on how a rep feels on a Tuesday afternoon, and the leads that go quiet are the ones nobody notices until the quarter is over.

## Follow-up is a task, not a feeling

Ask a rep whether they are following up on their leads and the answer is always yes. They mean it. They have a sense of which leads are warm, which ones they “should get back to”, which ones have gone cold. That sense is real, and it is also unverifiable. A manager cannot open a feeling on Monday morning.

What a manager can open is a task. A task has an owner, a date and a done state. When the follow-up lives as a task in the CRM, the question “are we following up?” stops being a conversation and becomes a filter. It is a smaller change than it sounds.

Most of what ranks for “lead follow up” is about the first reply and the wording of the messages. [Salesforce’s small-business guide](https://www.salesforce.com/blog/small-business/how-to-follow-up-with-a-lead/) opens on timing and points at software that triggers tasks and emails when a lead arrives; [Pipedrive’s lead follow-up page](https://www.pipedrive.com/en/products/sales/lead-follow-up-software) is a tour of its automation, reminder and segmentation features. Both are fine as far as they go. Neither describes what the system looks like once week two arrives, the automation has fired, and the lead has not answered. We covered the first touch separately in [speed to lead in Pipedrive](https://salesbond.app/blog/speed-to-lead-pipedrive/). This is the article about the second and third week.

## One owner per lead

Shared ownership is nobody’s ownership. A lead with two names on it gets two people assuming the other one called, and a lead with no name on it gets everyone assuming the same thing. Our rule on every team we have worked with: one lead, one owner, set the moment the lead is created, never left blank overnight.

In Pipedrive this is the Owner field on the lead in the Leads Inbox ( [Pipedrive: Leads Inbox](https://support.pipedrive.com/en/article/leads-inbox)). HubSpot, Salesforce and Zoho CRM each have an owner on the record under their own name for it, and the principle does not change: the record carries a name, and the name is one person. On HubSpot, the manager view of this is a weekly check for [overdue tasks in HubSpot](https://salesbond.app/blog/hubspot-tasks-task-queues-overdue-check/).

The hard part is not the field. It is the unassigned lead: the form fill at 11pm, the referral someone forwarded from outside sales, the inbound call written on a sticky note. Decide in writing who those belong to by default. On a small team the cleanest answer is a weekly rotation: whoever is on duty owns every unassigned lead until they claim it or hand it to a named colleague, and the handover happens by changing the Owner field, not by a message in chat. Owners can still change later. What cannot happen is a lead that spends a night with no one responsible for it.

One more thing about owners, because it is where this quietly breaks. When a rep leaves or goes on vacation, thier leads do not stop arriving. Reassign them on the day, not when someone notices the untouched count climbing two weeks later.

## The next task with a date

Reps resist this one most, and it matters most. Every open lead carries exactly one scheduled activity, with a date. Not “follow up at some point”. A date.

The task is for the rep, but it is written so that the manager, or a colleague covering, could run it without a conversation. What goes in it:

- The channel and the concrete thing to do: “Call Priya about the demo recording”, not “Follow up”.
- The date, and if the lead gave one, their date. “She said after the board meeting on the 22nd” is a better next task than one the rep guessed.
- What the lead last said, in one line, so the next touch does not start with “just checking in”.
- What happens if there is no answer: the touch after this one, or the decision to stop.

When the task is done the rep schedules the next one before closing the lead. That is the habit. In Pipedrive the composer on the lead lets you schedule an activity on the spot ( [Pipedrive: Leads Inbox](https://support.pipedrive.com/en/article/leads-inbox)), and a lead with nothing scheduled is exactly what the weekly report in the next section will look for. The HubSpot version of the same discipline is in our piece on a [saved view for deals with no next step](https://salesbond.app/blog/hubspot-deals-without-next-activity-saved-view/); Zoho CRM teams can let a Cadence carry the task for them, as long as [the Cadence stops when the buyer replies](https://salesbond.app/blog/zoho-crm-cadences-sales-manager/).

We do not think a sequence replaces this. A sequence schedules the touches; it does not decide what the lead actually needs next, and when it finishes, the lead has no task unless someone writes one. (Where sequences do earn their place is later, on deals: [sequences for deal follow-up in Pipedrive](https://salesbond.app/blog/pipedrive-sequences-deal-follow-up/).)

## The weekly lead follow-up report: leads with no touch in N days

The owner and the next task are what reps do. The report is what the manager does, and without it the first two quietly decay within weeks.

The report answers one question: which open leads has nobody touched in the last N days? Pick N once. For an inbound team with short cycles we would start at seven days; for considered purchases, fourteen. The number matters less than the fact that it is fixed and everyone knows it.

How to build it, using Pipedrive as the example:

1. Open the Leads Inbox and add the activity columns you need, next to Owner. Columns are set from the gear icon, and the same help article covers custom filters ( [Pipedrive: Leads Inbox](https://support.pipedrive.com/en/article/leads-inbox) ).
2. Under Filter > Filters > + Add new filter, build a custom filter for leads with no activity in the last N days, then a second one for leads with nothing scheduled. The two lists tell you different things: the first is leads nobody has touched, the second is leads nobody plans to touch.
3. Star both filters so they sit in your favorites. The report is now a click.
4. Run it at the same time every week. Monday, before the pipeline review, works because the week is still open. Read it by owner, not by lead.
5. For each name on the list, the owner gets to one of three outcomes by end of day: a dated next task, a reassignment, or an archive with a reason. The list goes to zero. The point is not to catch anyone out; a lead on the list is a lead with a decision pending.

![Mock Monday report of leads with no touch in 7 days, grouped by owner; most rows still have no next task.](https://salesbond.app/wp-content/uploads/2026/10/lead-follow-up-system-owner-next-task-report-2.png)

The other CRMs get you the same report by other means: a saved view in HubSpot, a list view in Salesforce, a custom view in Zoho CRM. Build it where your team lives, not in a spreadsheet, because a spreadsheet goes stale the moment someone forgets to export.

Two things to watch when you read it. A rep with a long list is not necessarily a slow rep; often they are the the one the routing sends everything to. And a list that is empty every week for a month deserves a second look. Either the team is genuinely on top of its leads, or someone has learned to clear the filter without doing the work. The next section is about the second case.

## What counts as a touch

A touch is a deliberate attempt to reach the person: a call, a personal email, a message, a meeting. It is not an automated sequence step, not a tracked open, not a newsletter the lead happens to be on, and not an internal note.

This matters because the report counts activities, and the CRM does not know the difference between a rep calling and a sequence firing. If auto-logged emails count as done activities in your setup, the “no touch in seven days” list will look clean while the leads are, in practice, untouched. We went through how that happens with [auto-logged emails in Pipedrive](https://salesbond.app/blog/pipedrive-email-activities-activity-report-inflated/) and what it does to a rep’s numbers. The fix is the same here: stop logging automated mail as done activities, so the only activities the filter sees are the ones a person did.

If a touch is in doubt, the test is simple. Could the lead tell you it happened?

## When to stop following up

A lead that has had its touches and has not replied does not belong in the open list forever. Nor does it belong in a “nurture” column that is really a graveyard. Set the stop rule next to the N you chose for the report: after a fixed number of dated touches with no answer, the lead is archived with a reason, or moved to a long-term nurture that has its own dated task, months out, to look again.

The rep writes the reason in one line. “No reply after four touches, last one 3 Oct” is enough. It keeps the archive honest, and it means the next person who meets that company a year from now knows what happened.

If a buyer did reply, with a reason and a date, that is not silence. The clock resets to their date and the next task moves there. We described how “no” actually sounds, and how to close a conversation without burning it, in [the follow-up rhythm after a proposal](https://salesbond.app/blog/follow-up-after-proposal-pipedrive/); the same signals apply earlier in the cycle, before there is a proposal at all.

## The Monday that tells you it is working

You will know the system has taken hold on the Monday when the report is short and the explanations are boring. A handful of leads, each one gets a dated task before lunch or a reason in the archive, and nobody at the table is surprised by any of them. Nothing dramatic. Just no leads that nobody knew about.

If you only do one thing this week, build the two filters and run them next Monday before you change anything else. The first list will tell you where to start.

A disclosure: we build SalesBond, a sales management layer on top of the CRM a team already uses; we started with Pipedrive. It reads the deals from your CRM and shows the risk and the missed steps on each one, a missing next activity among them, so the second half of this system keeps running once a lead becomes a deal. The weekly leads report above takes an afternoon to build in your CRM. If you want to see the deal side with your own data, [check your CRM with SalesBond](https://salesbond.app/).