Enquiry handling means receiving an enquiry, assigning a salesperson, giving a relevant answer and agreeing the next step with the customer. The speed of this work must be measured from the moment the enquiry arrives, including the wait before a record appears in the CRM system. The business owner needs both response times and the number of people who have not yet received a reply.
You pay for advertising to have a conversation with a buyer. But if marketing counts submitted forms and the sales team counts only the records it receives, a part of the process between the two reports has no one responsible for it. The person has already made an enquiry. The salesperson has not received anything yet. A requirement to call sooner does not cover that part of the process.
I think it is too early to promise a quick response until the company can show the full path of an enquiry. Otherwise, the most diligent salesperson will respond on time according to their own report and late from the customer’s point of view. Let’s look at what information the sales team must collect so the business owner understands where to put money: into passing on enquiries, staff working hours or checking what staff do.
Enquiry handling time
Enquiry handling time is measured separately up to the salesperson’s first action, up to meaningful contact and up to a decision on the enquiry. In all three cases, the clock starts when the enquiry reaches the company; the wait before a salesperson is assigned is included.
A call or a message sent by a person in response to the enquiry is enough to count as the first action. Meaningful contact requires an answer to the buyer’s question or a clarification that allows work to continue. A conversation, an estimate and agreeing an order take different amounts of time, so combining them into a single “enquiry handled” measure is unhelpful: it does not show exactly where the sales team was delayed.
Record automatic acknowledgements separately. They say that the form worked, but say nothing about whether a salesperson is ready to respond. I discussed the difference between someone being assigned responsibility and work actually starting in “Enquiries come in. Salespeople keep them waiting”. Here we need the next step: to see the waiting time that does not appear in the usual report at all.
Average response time is calculated for enquiries that have already received a reply. An unanswered enquiry has no response time yet. If the report only shows an average, the people waiting longest are absent from it. An essential line alongside it is how many enquiries are waiting now and how much time has passed since the oldest one arrived. That way, average response speed cannot be improved simply by picking convenient new enquiries and leaving old ones untouched.
I do not set a single time limit in minutes for all sales. A request for the next available slot needs a different response from a request for an equipment estimate for a project. Company rules need separate deadlines for the first response and for preparing the result, working hours and a procedure for delays. Customers are told these conditions before they submit an enquiry.
Outside working hours, keep two figures: how long the person has been waiting by the clock, and how much of that wait fell within the sales team’s working hours. The first is needed to make decisions about the schedule, the second to assess whether employees honour their commitments. Counting the night as zero in a report is easier than arranging staff cover, but it will not get the buyer an answer any sooner.
What is lost before CRM does not appear in the report
Enquiries that never reached CRM are found by checking against the original channels: website forms, call logs, email and messages. Looking only at records is not enough: a missing record will not be in the overdue list either.
The check needs to cover the same dates, use the same time zone and apply the same definition of an enquiry. A form submission, a call and a repeat message from one buyer may all relate to one need. They are linked while preserving the time of the first enquiry. A repeated “Did you receive my request?” must not turn yesterday’s customer into a new one today.
There must be an explanation for every incoming enquiry: a new record, an addition to an existing one or an exclusion with a reason. Spam and technical duplicates do not need a sales response, but deleting these records without a trace prevents the head of sales from checking the flow. The number of entries in the advertising account and the number of deals in CRM do not necessarily have to match.
This table helps you choose an action based on where the delay is, without sending the business owner to investigate every record.
| What the data shows | Where to look for the cause | What needs to change |
|---|---|---|
| The enquiry is in the source, but there is no trace of it being passed on | Delivery from a form, email or communication channel | A designated employee monitors the transfer; a failure triggers a notification |
| The record appears noticeably later than the enquiry | Delayed data transfer or manual sorting of incoming enquiries | The start of the wait is preserved from the source, and the delay before CRM is shown separately |
| The enquiry has been delivered but is waiting for a busy salesperson | Assignment and staff availability | The enquiry goes to an employee who has time to reply |
| The first reply is quick, but the promised estimate is overdue | Continuing the work after first contact | The promised result has a person responsible and a deadline |
Here, the business owner needs the result of the check: how many enquiries have not been matched and where they have been left. Marketing and sales staff work with the data exports. One appointed head of sales is responsible for ensuring that discrepancies are investigated, including the part between departments.
Customer enquiry handling
Customer enquiry handling must keep a record of the request, the person responsible, the response deadline and the agreement on what happens next. The first stage ends with a clear outcome: an agreed action, waiting for the customer’s reply with a date for the next contact, or a justified refusal.
It helps to set out the process in five steps. This is a basis for the sales team’s requirements, to which the head of sales adds the company’s own deadlines.
- Keep the original enquiry. The record keeps the channel, arrival time, contact details and the question itself. The salesperson does not have to start by asking the person to repeat everything they have already written.
- Assign someone who is available. Assignment takes account of shifts, staff absences and the employee’s current queue. If the assigned person has not started by the set time, the head of sales brings in someone else; the time of the first enquiry is kept.
- Give a first response that addresses the request. Say what is known and ask only for the information needed to continue. If an estimate takes time, say when the customer will receive it and exactly what to expect.
- Record what happens next. After the conversation, record the action, the person responsible and the deadline. After an unanswered call, schedule the next attempt according to the sales team’s rules and the customer’s chosen way of communicating. A call attempt and a conversation remain separate events.
- Record the outcome. An agreed meeting, an estimate sent, a buyer’s refusal and no contact are recorded separately. This lets the head of sales see at which action the work stopped, rather than just how many records were closed.
The first stage does not need a questionnaire covering every possible sales situation. It only needs information that changes the immediate next action: what the person needs, by when, where to reply and who will continue the conversation. Fields about budget, what is included or who gives approval are added when the answer affects the choice of offer. Otherwise, filling in the record competes with giving the answer itself.
If a promised deadline becomes impossible to meet, a message goes to the head of sales before it expires. There is a separate procedure for reporting this risk, covered in “Why wasn’t I told while the customer was still waiting?”. A quick first contact does not release the sales team from its next promise.
Why does a quiet day not mean a quiet morning?
The workload involved in handling enquiries depends on how many arrive at once and how much time staff have available at that point. The average number of enquiries per day hides the queue that forms at particular hours.
If you are discussing an additional salesperson, you first need a calculation for short periods. Intervals of 15 minutes are a suitable starting point: the head of sales compares the incoming flow with how busy staff are. Conversations, meetings and work on current orders are deducted from available time. Five salespeople on staff do not mean five available phones.
Fill in the line with your own data for one such period:
First response workload: for example, 4 new enquiries × 5 minutes of work per enquiry = 20 minutes. Available staff time: 15 minutes. Shortfall = workload − available time: 5 minutes.
Use the time per enquiry from your own work: the first contact plus the necessary recording of the result. Repeat attempts on earlier enquiries also take time, so include them in staff workload. If the calculation gives a negative result, there is no shortfall in total minutes. But simultaneous calls and long conversations still require spare time; the calculation sets the minimum time needed.
Where there is a recurring shortfall, the choice is between moving shifts, assigning an employee to incoming enquiries during busy hours and adding more people. Advertising schedules are also coordinated with the sales team’s availability. When there is enough time but enquiries still wait, it is too early to add staff: the head of sales needs to investigate how work is assigned. This calculation separates spending to address a staff shortage from spending caused by a disorganised queue.
Enquiry handling systems
Enquiry handling systems collect enquiries, assign people to deal with them and keep a history of the work. Choose them based on the part of the process where things currently go missing: receiving enquiries from channels, managing the sale or fulfilling a request after a purchase.
| Option | What work it suits | What to find out before choosing |
|---|---|---|
| Shared enquiry list | A small flow that one employee can keep track of manually | Who adds enquiries from each channel and how the head of sales spots an omission |
| CRM with connected channels | A sale involving several contacts, proposals and stages | Whether the original enquiry time is kept, and whether transfer errors and reassignment history are visible |
| A system for support enquiries | Existing customers’ requests for work to be carried out or for help | How deadlines, staff work queues and the link to the purchase are recorded |
Software names do not replace these requirements. A standalone spreadsheet needs manual checks; CRM needs data transfer to be set up; a support system needs an agreement with sales if an enquiry contains a new order. Buying a more complex tool will leave the same delay in place if no one is responsible for the stage before it.
Before moving the whole flow, run a trial on one channel. The person responsible for setup sends an enquiry, then repeats it when the assigned employee is unavailable. In both cases, the original time, text and transfer history must be kept; the head of sales must see when there is no reply within the set time. The employee demonstrates this using the records, and the business owner receives the trial result and a list of remaining limitations.
Which figures should the business owner receive?
The business owner needs a short report on whether all enquiries are accounted for, how long customers are waiting and the head of sales’ decisions. It should show what is preventing a reply: enquiry delivery, how busy the team is or an action that has not been carried out.
Here is a complete report structure for the selected period:
- Unique enquiries received: the number of enquiries after merging duplicates for the selected period. Not matched to records or explained exclusions: the number of enquiries without a record or an explained reason for exclusion.
- Replied to: the number of enquiries with a reply at the time of counting. Still waiting: the number of unanswered enquiries at the same point. Longest wait: the time from arrival to the point of counting for the oldest unanswered enquiry.
- First response deadline missed: the number of enquiries where the reply came after the set deadline or where there is still no reply after the deadline has passed.
- Main delay is at this stage: which stage. What the head of sales changed: the specific change. From when: date and time.
All lines refer to the same set of incoming enquiries and the same point in time for counting. Enquiries whose deadline has not yet arrived are marked separately. This keeps the report from mixing yesterday’s replies with today’s incoming enquiries and from marking work as overdue when there is still time to do it.
When data is being collected but the head of sales finds it hard to identify delays among deals and conversations, AI ROP from RENTROP helps with sales team monitoring: it shows response speed, analyses communications alongside the deal record and sends a report to the business owner in Telegram. The service only reads data; people remain responsible for corrections and tasks.
Failures in transferring enquiries must be fixed separately: analysing records will not recover information that never reached them. After a change, track all new enquiries from the selected channel: whether waiting time has fallen at the relevant stage, how many people are still without a reply and whether the delay at the next step has grown.
The source records the time of the enquiry; the salesperson records the time of the first conversation. In between, the company controls how long the person waits. These minutes cannot be written off as a gap between two reports: the customer has already come to you, even if your CRM does not know it yet.