Monitoring salespeople means comparing the work assigned, the salesperson’s actions and the outcome for the buyer. Every day, you need to see unanswered enquiries, broken promises to customers, mistakes in conversations and completed sales. The head of sales should review these signals: the business owner needs the causes of recurring problems and the decisions that require their authority.

When a buyer complains to you that a salesperson has not replied, you want to open all the sales team’s correspondence immediately. The team know the product, receive enquiries and work in a CRM system — so why the complaint? After an incident like this, it is easy to tell the head of sales to watch every action and send more reports.

But the same delay in replying can come from someone who put off responding to a customer or someone who received an enquiry during a meeting scheduled by their head of sales. If you assess both cases in the same way, you will have to either excuse both people or demand that one be in two places at once.

I believe monitoring must show which requirement was not met and whether the employee could have met it. Otherwise, the owner gets a list of suspects, and the head of sales learns to explain the figures in red.

Monitoring salespeople: four daily signals

Start by deciding what the department promises the buyer. How quickly it replies during working hours, how it handles evening enquiries, where it records agreements, who takes over a customer when an employee is busy. Ask the head of sales to propose a procedure and show that it can be followed. Without this, “slow” and “poor” will mean different things to the owner, the head of sales and the salespeople.

Four groups of signals are enough for a daily review. For each, the head of sales needs to see specific enquiries and actions. The department’s average figure is needed alongside them, but it does not replace the list of customers who need a reply today.

  • Who has not received a reply yet. How many new enquiries came in, how many received a meaningful answer within the set time and how many have been waiting longer. Count automatic greetings separately: they show that the message was delivered, but the buyer has not yet received an answer to their question. The sources are the times of the incoming message and the employee’s first reply.
  • What was promised for today. How many calls, calculations and replies were promised for this date, how many were completed on time and how many are overdue. Moving a task’s date does not in itself make it on time: it must also be clear whether the buyer agreed to the new deadline.
  • Where the conversation stalled because of the salesperson’s actions. For example, a customer asked what a service included but received only the price; they mentioned a time constraint, but the salesperson continued to offer an unsuitable option. The head of sales reviews the relevant part of the conversation alongside the enquiry: what the buyer wanted to know and what they were told.
  • How the work ended. Which sales were completed, which enquiries were closed after a refusal and which are still ongoing. A refusal because a product is unavailable and a refusal after a missed reply require different decisions. Revenue is compared with the time taken to complete the deal: today’s payment often completes work that began earlier.

The owner does not need to read all these lists every day. Their brief summary shows how many enquiries and commitments there were, how many breaches, where a cause keeps recurring and what the head of sales has already changed. The full list remains available to review any disputed conclusion.

There is a simple sign you can check today. Look at what appears next to the number of overdue items in the latest report. If it is only a salesperson’s surname, the cause has not yet been explained to you. If it states when they received the work, what they were busy with and which requirement they failed to meet, there is already a basis for choosing an action.

Methods for monitoring salespeople: each question needs its own approach

A call counter answers a narrow question: how many attempts an employee made to get in touch. It is useful when the head of sales is finding out why an assigned customer list has not been worked through. But the number of calls does not explain whether the salesperson understood the buyer’s request. For that, you need the conversation.

So the instruction to “monitor better” needs to be broken down into ways of gathering facts.

Tracking all deadlines. All incoming enquiries and promised actions go on the list. With a sample, it is easy to miss the single enquiry that has already been waiting too long. The head of sales checks for missed deadlines and redistributes work during the day. The owner decides in advance which changes the head of sales can make independently: for example, passing new enquiries to an available employee.

Reviewing conversations using a specific criterion. The head of sales selects cases where the customer did not get an answer, declined after discussing the terms or asked the same question again. The purpose of the review is to identify the salesperson’s action and show another way to respond. The instruction to “listen to more calls” does not define what to focus on.

Checking records that look fine against the correspondence. The head of sales takes part of the sample from enquiries with no missed deadlines or complaints, alternating between employees and sources. This catches another mistake: a task is marked as completed, but the message sent does not answer the customer’s question. The head of sales chooses the samples for this check; otherwise, the salesperson will bring only successful conversations.

Comparing workloads. Each employee’s new enquiries, previously promised actions and time taken up by meetings are visible. Ten enquiries for someone with an empty calendar and ten enquiries for someone conducting viewings are different workloads. An extra list of calls will not create spare time.

These methods are used at different intervals. A missed deadline requires a response on the same working day. The head of sales reviews a recurring mistake in negotiations separately with the salesperson. The owner decides whether to add an employee based on the accumulated workload and the cost of covering it. A daily complaint alone does not amount to a calculation to support hiring.

Sales team monitoring: a review of twenty enquiries

Let us work through an illustrative example, not a RENTROP case study. During a working day, the department received 20 new enquiries. All arrived early enough for the response deadline to pass before the evening report. In this example, the agreed rule was to answer the question within 30 working minutes. This is a condition of the example, not a universal standard for every company.

13 enquiries were answered on time. Seven were answered later. The share of replies sent on time: 13 out of 20, or 65%. The owner’s first reaction is understandable: more than a third of incoming enquiries were handled late, so discipline needs to be enforced.

The head of sales reconstructed what happened in all seven late responses. The causes fall into separate groups, with no overlap:

  • Three enquiries were automatically assigned to an employee during meetings that the head of sales had put in the employee’s calendar. No cover had been arranged for that time. The arrival times match the meeting times. The decision is to pass new enquiries to an available employee; this task is assigned to the head of sales.
  • For two enquiries, the salesperson did not know the answer to a technical question and waited for a specialist. They did not tell the buyer that they were checking the details or agree a deadline. This is visible in the correspondence. The head of sales reviews with them how to acknowledge the question, get a deadline from the specialist and pass it on to the customer.
  • The salesperson saw another two enquiries but put them off. The time they were read is recorded; during that period, the salesperson had no meetings or previously assigned urgent tasks, and knew the response procedure. Here, the head of sales requires the employee themselves to follow the procedure and records exactly which requirement they failed to meet.

The overall figure is unchanged: seven late responses. But the general demand to work faster has been replaced by three specific decisions, each assigned to someone. One employee needs training, the head of sales needs to change how enquiries are allocated, and another employee needs to follow a known rule.

For this example, the evening message to the owner can now be completed:

New enquiries — 20. Replied on time — 13; replied late — seven. Three late replies were linked to allocation during meetings: from the next shift, an available salesperson will receive new enquiries during those times. Two enquiries were delayed by a technical question: the head of sales went through with the employee the procedure for replying and agreeing a deadline. Another two late replies were breaches of a known procedure; the employee has been told to reply within the set time. No decisions are required from the owner today.

This message records the review and the assigned changes. Whether they have been carried out is visible separately: where the enquiries went during meetings, whether the buyer was given a response deadline and whether there were further breaches of the known procedure. Seven late replies cannot be called seven lost sales: the original data contains no information showing that the buyers declined.

If, after the work is redistributed, a queue starts to build up for the employee providing cover, the head of sales brings the owner a calculation of how much extra time is needed. The owner then chooses whether to change the schedule, reduce other work or pay for extra staff. Until that calculation is available, a demand to hire another salesperson remains premature.

A system for monitoring salespeople: what to assign to the head of sales

A reliable procedure starts with a clear decision from the owner: who receives a signal, what they have the authority to do and when they must raise the issue with someone more senior. If every delay is seen by all those in charge at the same time and each demands an explanation, the department spends time giving several answers about the same customer.

Below is an instruction you can use as it stands. Its deadlines apply to preparing a working procedure, not to a promise of sales growth.

By the end of the second working day, prepare a procedure for daily monitoring. Specify response times for our channels, arrangements outside working hours and cover during meetings. Use the team’s schedule to show who will be able to take enquiries.

>

Keep four groups in the daily summary: enquiries without a timely response, overdue promises, mistakes in conversations and sales results. Next to each breach, state the cause, the action assigned and the deadline for completing it. Mark separately any cases where there is not enough information to reach a conclusion.

>

When preparing this, take one completed working day. Show all enquiries where the deadline was missed and a few with no breaches, chosen by you. These should make it clear how you distinguish between excessive workload, a lack of skill and failure to meet a known requirement.

>

For decisions within your authority, report what has already been done. If additional spending or changes to promises made to buyers are needed, bring options and their consequences. Do not wait for the evening summary when an answer is needed sooner.

When reviewing the result, the owner checks three things. The summary’s figures match the original list; there is an action for each type of breach; and the person assigned has the time and authority to carry it out. The same “spoke to the salesperson” in every row means the causes have not yet been analysed.

This procedure also has a limit. If the data is available and the causes can be identified, but the head of sales repeatedly changes nothing, their own work is now in question. A separate article covers this: “No one is monitoring this at the moment. So what is the head of sales doing?”. Here, the owner’s task is to get a sound basis for decisions about salespeople.

When the data is available but the summary still has to be put together manually

A deal record, a call and the correspondence describe the same sale from different angles. If the head of sales sees only the record, they will miss the buyer’s unanswered question. If they look only at the conversation, they will not notice an agreement that has already been fulfilled through another channel. Bringing this information together is a separate task that also takes time.

For this task, RENTROP has AI ROP — sales team monitoring: it analyses calls and correspondence together with the deal record, shows response times and revenue by channel, and sends a report to the owner in Telegram. AI ROP only reads data; the head of sales makes decisions about workload and employees’ actions.

An owner who receives a complaint about a salesperson’s silence is entitled to demand an answer. But daily monitoring should bring them to a more precise choice: who to hold accountable for the breach, who to help and which requirement the company itself has made impossible to meet. The complaint can then reach someone who can actually fix its cause.