The Phone Never Stops Ringing: How to Tell Which Calls Are Eating Your Working Hours

The phone never stops ringing because the same question usually gets an answer only from you. Which calls eat your working hours shows not in the ringing but on a tally sheet: one week, every call, with caller, request and duration. Then you see which questions repeat, which you can pre-empt and which need your conversation.

Why does the phone in your business never stop ringing?

It never stops because the answers to recurring questions sit in one place: with you. Anyone who wants to know when you're coming, whether the part has arrived or what a line on the invoice means has no route other than your number. For the caller, that's the shortest path. For you, it's an interruption.

Look at an ordinary morning. You're at the vehicle or on site, the phone rings, a customer asks whether they can still pick up today. You say yes, hang up, and look for the spot where you left off. Ten minutes later the next question, this time from the supplier, asking whether yesterday's order is right as it stands. None of these calls is unjustified. Each one is, for the caller, the only route to a piece of information that sits with you. Together they add up to a day that feels like work and on which the actual work barely moves forward.

An interruption costs you twice. Once for the minutes on the phone. And once for getting back into what you were doing: taking the measurement again, restarting the sentence in the email, listening to your employee a second time. The second bill appears on no call log. That's why you underestimate it. A one-minute call is one minute in the call list. In your day it's that minute plus the way back into the task, and that way is longer the more concentration the task demands.

I think this is the core: this isn't a lack of order. It's a lack of routes. Your business knows a great deal: where the fitters will be tomorrow and when, which part was delivered, why a line on the invoice is called what it's called. But most of it only gets out through you, because there's no second route by which the customer could learn it. What only you know only rings at you.

That's why it helps you little to get annoyed at the ringing or to resolve to work with more focus. The phone doesn't respond to your discipline. It responds to whether the information reached the caller by another route. And that is exactly what you can measure, in one week.

How do you make visible in one week which calls repeat?

With a tally sheet you fill in for every call across five working days. Four columns are enough: who's calling (customer, supplier, new enquiry, your own team), what they want in three words at most, how long it took, and whether the answer needed you. Nothing more.

The fourth column is the most important, so I'll define it precisely: the answer needed you if nobody else in the business could have given it and it isn't written down anywhere. Everything else gets a No. A customer asks whether their car is ready, and you know because you've just finished it. That's still a No, because the information could have been in a message. A customer wants to know whether you can manage the additional job by Friday, and only you can judge that. That's a Yes.

A line then looks like this: Customer, part arrived, two minutes, No. Or: Team, where's the key, one minute, No. Or: Customer, complaint tiles, twelve minutes, Yes. You don't write sentences. You write keywords you'll still understand on Friday.

The sheet sits where the phone rings: next to the landline, as a note on your mobile, on the clipboard in the van. You enter every call straight away, not in the evening from memory. From memory, you keep the long conversations and the many short ones drop out. The short ones are exactly what you're looking for.

You may be thinking: I don't have time to write down every call on top of everything else. Do the maths. One line with four keywords takes barely longer than hanging up. What you get for it is, for the first time, a picture of where your phone time actually goes, instead of a feeling that feels the same every evening.

Count the calls you didn't answer too, and the callbacks you therefore handle in the office after hours. A missed call that needs two callbacks is three units of work for one question. If your staff also take calls, each of them gets the same sheet. Otherwise you count only the part of the phone that reaches you and miss the part that chops up your team's day.

One more rule for this week: change nothing. You don't sort, you don't judge, you don't rearrange. Whoever starts improving while counting ends up counting what they changed, not what was. The sheet is meant to show you how your phone rings today. Only once the picture is complete is intervening worth it.

What kinds of calls will you probably find on your sheet?

Two kinds that differ fundamentally: follow-up questions and requests. A follow-up question collects information that already exists in your business. A request brings something new in: a job, a problem, a decision.

For you, the difference isn't wordplay but the lever. A follow-up can be replaced, because the answer already exists and simply hasn't found its way to the customer. A request can't be replaced, because the answer only comes into being the moment you give it. Before the conversation, it doesn't exist. One is transport, the other is work.

Among the follow-ups, in most businesses I know, are always the same patterns: When are you coming. Is my car ready. Has the part arrived. What does this line on the invoice mean. How late are you open today. Did you get my transfer. Add the callbacks from customers who couldn't reach you the first time and try again. And add the calls from your own team asking about something you've already answered three times: where the key is, which supplier handles the seals, whether the customer on Linden Street pays cash or on account.

Among the requests are the new job, the complaint, the supplier with a delay, the employee with a question for which there's no rule yet. You recognise these calls because after the conversation something in the business is different from before: a date is set, a price has been named, a decision has been made.

There's a third group you only notice on the sheet: calls that are follow-ups posing as requests. The customer calls because they want to know whether the car is ready, and in the conversation lands on whether you could change the tyres while you're at it. The trigger was transport. The job came on top. Had they received the ready notice, the job would still have come, just without the call in between, at pickup instead.

When you count the tally marks under follow-ups on Friday, you'll probably see for the first time how much of your phone time goes into information you already have. Not as a feeling, but as marks on paper. That pile is the one you start with.

Which calls can you avoid without annoying customers?

All follow-ups whose answer you could have sent before the call. Avoiding here doesn't mean fobbing off. It means pre-empting: the customer gets the information before they have to come and get it from you.

The mechanics behind it: a customer doesn't call because they enjoy phoning. They call because they don't know something and need to know it to plan their day. The question about progress arises because nobody said when the repair would be done. The question about the appointment arises because the confirmation came without a time window. The question about the invoice arises because a line on the invoice is named differently from the quote. Every follow-up has a gap as its cause, and that gap arose in your process, not with the customer.

For each of these gaps there's a message you write once as a template: the appointment confirmation with a time window and a note on what the customer should prepare. The ready notice as soon as the work is finished. The invoice using the same words as the quote. Each template costs you half an hour once. Each follow-up that doesn't happen saves you one call and one re-entry.

A ready notice doesn't need to be anything big. Three sentences are enough: Your car is ready. Pickup today until 6 p.m. or tomorrow from 7 a.m. The invoice is attached, payment on site or by bank transfer. With these three sentences, the question about progress, the question about opening hours and the question about payment all disappear at once. Three calls, one message.

The same goes for the appointment confirmation. Someone who hears "We'll come on Thursday" calls on Thursday morning and asks when. Someone who gets "Thursday between 8 and 10 a.m., please keep the access to the basement clear" has no reason left to call. The difference between the two messages is half a sentence. The difference in your day is one call fewer per appointment.

The invoice using the words from the quote is the point I see overlooked most often. The quote says "Replace front brake pads", the invoice shows an article number and "Brake service FA". The customer doesn't recognise their line and calls. Not out of distrust, but because they're holding two documents that don't match. Same words in both places, and that follow-up disappears.

You may be thinking: my customers want personal contact. Test that against your sheet. A customer who asks whether their part has arrived wants the part, not the conversation. They get the conversation when they need it, and then you have time for it. A customer who gets a clear message doesn't experience you as less personal but as more reliable. What you can say beforehand, you don't have to answer afterwards.

How do you get back to customers when you're on site or in the workshop?

With fixed callback times the caller knows in advance. Two windows a day are enough, say late morning and afternoon, in which you handle all callbacks one after another. The message on your voicemail names these times and asks for the request in one sentence.

The caller doesn't want you right now. They want certainty that their request has arrived and when they'll get an answer. A voicemail message that tells them the next callback window gives them exactly that. A message that only asks them to leave a message gives them nothing, so they try again later. And again. Each of those attempts lands as another mark on your sheet, even though there's only one question behind them.

This is what the message can sound like: This is Miller & Sons. We're out with customers right now. We return calls daily between 11 a.m. and noon and between 4 and 5 p.m. Please leave your request in one sentence and a number to call back. Nothing more needs to be there. The sentence with the request is the most important, because it decides what can already be prepared for the callback.

Batching has a second advantage for you. Ten callbacks in a row run with the same head, the same documents and the same rhythm. Ten calls spread across the day pull you out of your work ten times. And if the request is already on the voicemail, someone from your team can prepare the follow-ups or answer them outright: look up the delivery date, pull out the invoice, confirm the appointment. At callback time, all that's left for you is what really needs your conversation.

You may be wondering about emergencies, the burst pipe or the customer stranded on the motorway. For those, there's a separate number or an addition to the message that puts them through. Emergencies are rare, and they're easy to spot on your sheet. The problem isn't the emergency. The problem is that today every call is treated as if it were one.

Reachable doesn't mean immediate. Reachable means reliable.

Which calls need you personally?

The ones where something is being decided or something has gone wrong. A complaint. A job whose scope only you can judge. A delivery that upends your schedule. A question from the team for which there's no rule yet. These calls aren't a disturbance. They're your business.

And they're the reason to clear the others out of your day. If you're talking to an annoyed customer while two follow-ups wait on the line, that customer gets part of your attention. They notice. You notice too, usually only afterwards. A complaint you hear with half your mind comes back as a second complaint. A complaint you hear in peace can turn into a customer who stays, because they've seen how you handle a mistake.

The same goes for the new job. Someone who reaches you between two follow-ups gets an off-the-cuff estimate, with figures you'll have to correct later. Someone who reaches you in the callback window, with the quote on the table, gets an answer that holds. The second case isn't just more pleasant for you. It's more profitable, because you don't have to go back and fix it.

Check one point in this pile especially: if the same team question appears three times on your sheet, it's no longer a decision. It's a rule you haven't written down yet. The first time, you decide. The second time, you remember. The third time, you repeat yourself, and your staff learn only one thing from it: that the route to an answer runs through your phone. I've described elsewhere why your team ignores what you say and copies what you do. On the phone this pattern shows most clearly, because every repetition leaves a mark.

Do you need office staff just because the phone keeps ringing?

Not before you've read your sheet. An office worker takes the calls off your hands. They don't take away the reason the calls come. If your sheet shows that the biggest pile consists of follow-ups, you're hiring someone to read out information you could have sent beforehand. That's an expensive way to replace a message.

Add a second effect you only see after a few months. At first, the office worker doesn't know the answers. So they ask you. The customer's call to you becomes the customer's call to them and their walk over to you. The interruption hasn't disappeared, it has only taken a detour. Only once the answers are written down somewhere, in a template, in a schedule, in a rule, can they answer without you. And as soon as they're written down there, the customer could have had them without a call.

You could mute the phone more often instead. That doesn't solve the problem: the question stays open, and the customer asks it again later, with less patience. Muting postpones the call, it doesn't replace it.

Office staff pays off for you when, after pre-empting and batching, enough calls remain that need a conversation but not your conversation: appointments that need coordinating, suppliers to liaise with, quotes to follow up, materials to order. Then you know from the sheet not just that you're hiring someone, but what for. In the interview you can say which calls the role gets every day and which answers are ready for them. Your tally sheet becomes the job description.

The order is decisive: first pre-empt, then batch, then hire. Reverse it and you pay a salary for work a template would have done, and after a year you have the same interruptions, only with higher fixed costs.

What do you do with the sheet at the end of the week?

You sort every mark onto one of three piles: pre-empt, batch, personal. Then you take the biggest pile and change a single thing. A template for the ready notice. A callback window in the voicemail message. A rule for the team question that came up three times.

A single thing, not three. If you introduce the template, the message and the rule all on Monday and the phone is quieter the following week, you don't know which of them worked. If you change one thing, you know. And you have something you can show your team: this follow-up came this many times last week, this many times this week, and in between is a message we now always send.

The week after, you count again. Not whether it feels quieter, but how many marks sit under this one type of call. This many before, this many after. That's your evidence, not your feeling. Feelings are especially unreliable about interruptions, because a single difficult call in the afternoon makes the whole day seem loud.

Then you take the next pile. After three or four weeks you've pre-empted three or four follow-ups, batched your callbacks, and have a set of rules for the team that previously existed only in your head. None of it was a big project. Each step was a line on a sheet of paper that became a message.

What you do differently tomorrow: put a sheet with four columns next to the phone. The phone doesn't get quieter because you work harder. It gets quieter because you answer questions before they're asked.

If your sheet shows that a large share of your calls is triggered by paperwork that hasn't gone out yet, by appointment confirmations, ready notices and invoices, then that is exactly where we start: with the person who runs the business and the routes the information takes. Those messages don't have to be written by hand every time. They can go out on their own as soon as a job changes status with you. Take the first step in the free four-day challenge on impruvement.com.