A small company cannot answer every call. Someone is with a customer, on another line, driving or at lunch. That is normal. The loss happens afterwards, when the missed call sits on a screen, three people see it and each assumes another will ring back.
Callers who reach voicemail rarely wait. Many hang up and try a competitor. A person who leaves a message is telling you they would still like to hear from you, which makes that message one of the warmest enquiries you receive. It deserves the same care as a form submission or an e-mail.
This article describes a routine that fits a company with a few phones and no call centre. It needs one shared sheet, one rule and about ten minutes a day.
Decide what a missed call is
Include all of these, or the routine will leave gaps:
- Calls that rang out with no answer
- Calls that went to voicemail, with or without a message
- Calls received while the line was busy
- Calls outside opening hours
- Calls that were answered but promised a call-back ("I will ring you later")
The last one is the most often forgotten. A promise made on a live call is still a missed call until someone makes it.
Name one owner for each day
Shared responsibility is no responsibility. Choose one person per day, or per half day, who owns call-backs. Write the rota where everyone can see it, with a backup for holidays and sickness.
The owner does not have to make every call personally. They make sure each one is made. If a missed call belongs to a colleague's customer, the owner passes it on and records who took it.
If you already have a shared mailbox with owners and triage rules, use the same people and the same habits. A missed call is simply another item in the queue.
Set one call-back time and say it out loud
Pick a time you can keep. Two working hours is realistic for most small companies; one working day is the outer limit. A shorter promise you break is worse than a longer one you keep.
Put the promise in your voicemail greeting, so the caller knows what will happen:
"Thank you for calling. We cannot take your call right now. Please leave your name, your number and a short reason for calling, and we will call you back within two working hours. If it is urgent, you can also write to us at the address on our website."
Keep the greeting under 20 seconds. Asking for name, number and reason gives the person calling back something to prepare. Check the greeting on a real phone once a quarter; old greetings that mention a former colleague or wrong hours are common.
Write each one down
Keep a shared sheet or a simple list in your team tool. One line per missed call is enough:
| Time | Number | Name / company | Reason | Owner | Called back | Outcome |
|---|
The columns do the work:
- Reason tells the owner whether this is a new enquiry, an existing customer with a problem, or a sales call to ignore.
- Owner is the person who will ring back, not the person who noticed.
- Called back is a time. If there was no answer, note "no answer" and the time of the attempt.
- Outcome is a few words: "quote requested", "booked for Thursday", "wrong number".
Do not copy personal details beyond what you need to call back. Keep the log in a place with limited access and delete old lines on a schedule. If you operate in the UK or EU, the ICO's UK GDPR guidance is a good starting point for how long and why you may keep contact details.
Rules for the call-back itself
- Try twice, at different times. If the first attempt gets no answer, try again later that day or the next morning. Do not leave a long voicemail; say who you are, why you ring and how to reach you.
- Send a short message after the second failed attempt. A text or e-mail with your name and one line about the reason often gets an answer when the call did not.
- Close the line. Mark it done only when the person has been reached, has replied or you have made two attempts and sent a message.
- Move real enquiries to the usual place. If the caller wants a quote or a visit, create the same record you would for a website enquiry. Our article on handling website enquiries in one working day describes that follow-up.
- Pass complaints on. If the caller is unhappy, the call-back is the first step of a complaint log entry, not a chat to be forgotten.
Look at the pattern once a month
After a month you have real data. Spend fifteen minutes on three questions:
- When do calls get missed? If most fall between 12:00 and 13:00 or at the end of the day, the fix may be a rota change, not a new tool.
- How long did call-backs take? Compare with your promise. If you miss it often, change the promise or the staffing, but do not ignore it.
- What did callers want? If the same question appears repeatedly, answer it on your website or in the greeting.
Write one change for the next month and check it then.
Where AI can help, and where it cannot
Voicemail transcription is the most useful and least risky step. A service can turn each message into text and send it to the call-back owner, so they can read the reason before dialling. Software can also sort messages into categories, draft the text message after a failed attempt or count calls by hour for the monthly review.
Keep a person in the call. Do not let software promise prices, dates or refunds to a caller, and check transcripts of names and numbers before you use them, because they are often wrong. Tell callers if messages are transcribed or recorded, and follow the rules that apply where you operate. Treat each automated output as a draft for the owner to check.
A first step
This week, write down who owns call-backs tomorrow and the day after. Record your voicemail greeting with the call-back time in it. Start a log with the seven columns above and fill in every missed call for five working days. That is enough to show how many you miss and how many you answer in time.
If you would like help building a routine that fits how your company works, see our AI consulting service.