Why the CRM accumulates overdue tasks

Why overdue tasks are not about a salesperson being lazy

The manager opens the CRM, sees the list of overdue tasks and thinks about discipline first. The salesperson swears they called the client, they just did not create a new task. And often that is true: a task can show up in the CRM as overdue simply because nobody created a new one for tomorrow — the call happened, but the system never learned of it.

The problem is not the person's character but the way the process around the task is built. If setting the next step rests only on the salesperson's memory, overdue is a matter of time, not of probability. The more deals in progress, the faster the system accumulates a gap between what actually happens and what is visible in the report.

A separate category is tasks nobody created at all. There are deals with a long-term interest where the decision is postponed for months, and there are more urgent ones that quietly slide into the same heap without reminders. As long as the CRM has no clear rule about when and which task appears, the overdue will grow by itself.

Where the line runs between normal and alarming

There is no universal threshold for overdue tasks that suits every department alike. The deal cycle, the number of salespeople and the specifics of the niche are too different for one figure to describe the norm for everyone. Going by someone else's percentages from articles online is a bad idea: they were calculated on a different business.

It is more sensible to look at the dynamics inside your own CRM: is the share of overdue growing week on week or falling. If after introducing new rules for setting tasks the number of overdue deals goes down, the movement is in the right direction, even if the absolute number is not yet ideal. If it grows — that is a signal to investigate rather than to hope it passes by itself.

The second benchmark is not the overall percentage but the breakdown by type of deal. Overdue on hot clients ready to pay now is far more critical than overdue on deals with a long-term interest, where a reminder once a month is a normal rhythm. Mixing them into one figure is a way of not seeing the real problem.

Three reasons tasks turn into overdue

The first reason is technical: the CRM has no deadlines or notifications set up, so a task formally exists but nobody gets a reminder in time. The second is process-related: the pipeline stages have no automatic task creation, so the next step depends on whether the salesperson remembers to set it. The third is motivational: tasks are created properly, but the salesperson ignores them because they see no link between a timely call and the result.

These three causes need different solutions, and it is easy to go wrong here. If the problem is technical and the manager starts fining people for overdue, nothing will change — the salesperson physically never got the reminder. If the problem is motivational and the company tunes the notifications, tasks will simply be closed formally, without an actual call.

Mixing the causes is the most common mistake when analysing overdue. A sales department introduces new rules in the CRM, waits for improvement, and the figure does not move because the real cause was somewhere else. Separating these three layers is the first step towards actually fixing the problem rather than spending time on symptoms.

How to tell the cause apart from the CRM reports

The technical cause is visible quickly: it is enough to open the deal cards and check whether all tasks have a deadline and whether a notification to the owner is switched on. If some tasks hang without a date or without a salesperson attached, the matter is not the people but the setup. That is fixed once, at the level of the CRM, and not in a conversation with an employee.

The process cause is shown by the report on pipeline stages: if at a certain step deals regularly hang without a task, then no auto-creation rule is set up for that step. For example, a deal moves to the “negotiations” status, but a call task appears only sometimes, when the salesperson remembers to create it by hand. You see it in the unevenness — at some stages there is almost no overdue, at others it is systematic.

The motivational cause is revealed by a breakdown by individual salespeople with the process set up identically. If some employees have overdue close to zero and others consistently high with the same tools, the CRM is not the issue. Here quality control helps: listening to calls and scoring against a checklist show whether the salesperson really carries out the task or merely closes it with nothing behind it — this is handled by quality control.

Ready automation rules that close the technical cause

In amoCRM, overdue caused by forgetfulness is solved by rules that fire without a person. The first is auto-creating a task with a deadline at every pipeline stage: the deal moves into a status and the system sets the next step with a specific date itself, instead of waiting for the salesperson to remember. The second is auto-escalation to the manager on overdue: if a task is not closed on time, the notification goes not only to the assignee but also to their manager.

The third rule concerns the change of stage: if a deal moves further along the pipeline, the old task is automatically closed or re-created for the new stage. Without this rule the CRM accumulates ghost tasks for years — the deal moved on long ago while the old task still hangs there overdue, distorting the whole picture of the department. This is especially noticeable when the manager tries to calculate the real percentage of overdue and runs into dozens of such dead tasks.

All three rules are set up once at the pipeline level and then work without a salesperson's manual involvement. This does not remove the substantive part of the work — the call still has to be made and the conversation run against a checklist — but it removes the very possibility of forgetting to set a task. Setting up pipelines for the client's process and connecting such rules is part of CRM implementation.

What a sales robot does where rules do not save you

Automation in amoCRM solves the technical cause of overdue but does not solve the problem of an enquiry arriving when the sales department is physically not working. In the live GetGate project 27% of enquiries came in the evening and at weekends — they used to wait until morning, and by the time the salesperson sat down at the computer the first-contact task was already overdue by time, even if it had been created properly.

Here it is no longer an automation rule that works but a sales robot: it replies to the client at the moment of the enquiry, not when a salesperson is free. The robot works out the right step for the situation itself — for example, if the client did not reply, it decides when it is better to call back — and records the outcome of the conversation in the CRM instead of the salesperson creating an entry by hand. This does not remove tasks from the CRM entirely, but it moves the moment of first contact into what used to be overdue by definition.

In the same GetGate project salespeople free up about an hour of working time a day — time that used to go on setting tasks by hand and on messaging about standard questions. And in a blind check on real correspondence the assistant's reply turned out to be no worse than a human's in 80% of cases, which means part of the first contact can be entrusted to a robot without risking the quality of the conversation. More about how this works is on the page about the sales robot.

What overdue tasks turn into if they are not fixed

An overdue task is not an abstract line in a report but a specific client nobody got in touch with in time. One telling case from practice: a client with VIP status first worked with one salesperson, then that person left, the client was forgotten, and they existed in the CRM almost surreally — listed as a VIP but with nobody talking to them. On paper the overdue looks like a percentage; in reality it is a specific lost deal, found out about too late.

A similar story goes with long-term interest. Deals where the client's decision is postponed for months easily sink among urgent tasks if there is no reminder system for them. The salesperson updates such deals after the fact, with a long overdue, and decides anew when to write to the client — although the right moment for a reminder passed long ago.

No percentage of overdue on its own says how much money a company is losing — that depends on the deal amount, the niche and how hot the client was. But the principle is one: the longer a task hangs overdue, the higher the chance the client has already found another supplier. To assess the scale of the problem in your own figures, use sales analytics — the plan-against-actual breakdown by channel and salesperson shows where exactly the money is lost, not only where tasks pile up.

A weekly review ritual for the head of sales

It makes sense to turn the review of overdue tasks into a regular ritual rather than a one-off check once a quarter. Start with hot deals — those where the client is already ready to pay and the task is more than a day overdue. That is the most expensive category of overdue and it has to be gone through first, while the client has not yet left for a competitor.

Next come tasks on deals in active work — where the salesperson was supposed to call, write or issue a document. Here it is important to look not only at the fact of the overdue but at the substance: did the salesperson close the task formally or actually get in touch with the client. Reviewing conversion, calls and the quality of communication is no longer a CRM question but one of rules, scripts and analysis of why clients say no, which is handled by to build the sales department.

Last of all come long-term and “sleeping” deals — the clients it is easy to forget because they create no urgency. It is exactly in this category that stories like the forgotten VIP client are most often found. Going through this list regularly, even once a week, costs less time than restoring a relationship with a client who has decided they were forgotten.

Where to start putting tasks in order

Before setting up automation rules it is worth reviewing the current sales department and understanding where exactly the money is being lost — at which stages, with which salespeople, on which types of deal. Without this step it is easy to spend time automating the wrong cause: setting up notifications where the problem was motivational, or the other way round.

After the review the pipelines are assembled for the client's real process, the channels and telephony are connected, and the rules for auto-creating and escalating tasks are set up. If part of the first contact can logically be handed to a robot — handling evening and weekend enquiries, for example — it is trained for the niche and connected to the same channels the salespeople already work in.

After that the department works under control: plan against actual is visible in real time, overdue does not pile up unnoticed, and the manager sees a problem in the week it appeared rather than a quarter later. Tuning and scaling happen as it becomes clear what works in that particular department. More reviews of similar situations are in the blog.