An unanswered callback is one of the most frustrating moments for a small team: the customer left a number a few hours ago and asked to be called, yet nobody picks up. Then one teammate calls once, another half an hour later, and a week on nobody knows if the request is still open. Silence is not lost interest: they may have been driving or ignoring unknown numbers.
This guide gives you a one-page callback policy: a preferred time in the form, the first attempt in that slot, the number and spacing of retries, a voicemail script, a written message and rules for closing. Finally, you will see which booked times most often end without an answer.
Why a missed callback needs rules, not instinct
Without an agreed policy, the number of attempts depends on who happens to have a free minute. One customer gets three calls within an hour and feels hounded, another gets a single call and then silence. Both cost you. With rules, everyone knows the next step.
A good policy answers five questions: when you make the first call, how many times you try, how far apart, what you leave after a failed attempt and when you stop. You need no phone system or dialer, just a shared queue, one owner per request and a note after every attempt.
Ask for a convenient time in the form
Many missed callbacks happen because the business calls when it suits the business. So the customer picks the day and time before any call is made. How such a form works and which fields are worth collecting is covered in our guide to website callbacks; here, all that matters is that the time comes from the customer.
Only offer times when someone can actually call. In Meetlead, the contact request form shows slots calculated from your team schedule, and a topic list lets the customer state the reason for the call right away. In the confirmation, say which number you will call from. People expecting a call are more likely to answer an unfamiliar number.
Make the first attempt exactly at the chosen time
A customer who chose 2 p.m. is waiting for your call at 2 p.m. By 2:40 they may be in a meeting. Before you dial, claim the request so nobody else calls too, and read the topic. Your first sentence should refer to what the customer asked about, not to a generic "I'm calling about your inquiry".
In the Meetlead mobile app, claiming a request stops alerts for the same request on your teammates' phones, and the call button opens the phone app with the customer's number. If nobody answers, do not redial straight away. Leave a message, log it and schedule the next attempt.
How many attempts and how far apart
No study sets one correct number of attempts for every business. For a small team, three calls spread across different times of day followed by one closing message is a sensible starting point. The table below is a sample policy to adapt, not an industry standard.
Scroll the table sideways to see all columns.
| Attempt | When | What to do if nobody answers |
|---|---|---|
| 1 | At the time the customer chose | Voicemail and a short written message |
| 2 | Same day, different time: afternoon instead of morning | No second voicemail, just log the outcome |
| 3 | Next business day, at yet another time of day | Short voicemail saying you will close the request |
| Closing | After the third failed attempt | Closing message and a recorded reason |
Change the time of day, not just the day. Gaps between attempts should grow, not shrink. Schedule the next attempt right away rather than "later". In the Meetlead mobile app you can set a reminder on a pending request and receive a notification on your devices at the time you picked.
The Zoho Voice documentation describes automatic callbacks in a contact center: a maximum of three attempts, a configurable interval after an unanswered call, and requests expiring automatically after 24 hours. These are one product's settings, not proof that this pattern works best in your industry.
What to say on voicemail and what to write
A voicemail needs to convey three things: who is calling, what it is about and what happens next. Leave out offer details and anything a third person should not hear. Keep it short.
"Hello, this is Anna from [company name]. I'm calling about your request to talk about [topic]. I'll try again today at around 5 p.m. If another time suits you better, you can pick it on our website or call me back on this number. Speak soon."
Send the written message through the channel the customer came from. If they asked for a call in a website chat, on Messenger or on Instagram, reply in that conversation. If all you have is a number, you can send a short text from your business phone; Meetlead does not send SMS messages. For example: "We called about [topic]. Next attempt tomorrow around 10 a.m. If another time suits you better, just reply." A customer who returns to your website will see their pending request in the widget and can reschedule it.
When to close the request and what to record
A request that never ends clogs the queue and muddles reports. Closing it creates a clear state: no call happened, the customer knows how to come back and the team knows why the request is closed. The same principle applies to reminders after a proposal, covered in our guide to following up on proposals, although there the conversation has already taken place.
- Send a closing message."We were unable to reach you about [topic], so we are closing the request on our side. Whenever you would like to talk, just choose a new time on our website."
- Record the attempts.Number of attempts, their times and the reason for closing, such as "no answer after 3 attempts" or "wrong number". A Meetlead callback creates a ticket where you can leave an internal note.
- Set the right status.A request can be pending, completed or rejected. Agree as a team which status means no contact was made, and stick to it.
- Keep the number out of other campaigns.A number left for one specific question is not consent to calls about other offers.
In Poland, Article 398 of the Electronic Communications Law, in force since 10 November 2024, prohibits using telephones to send commercial information, including direct marketing, without the subscriber's or user's prior consent. It does not say how many times you may call back at a customer's request. Other countries have their own rules. This is not legal advice.
Measure missed callbacks by booked time
The raw number of unanswered calls says little; the share of unanswered first attempts by booked time says much more. A simple spreadsheet is enough. Meetlead statistics show how callback requests are distributed across statuses, but you will build the breakdown by booked time yourself.
- Booked time and day of the week.
- Whether the first attempt happened on time or late.
- The attempt at which the customer answered, or no contact.
- Request topic from the topic list.
- Outcome of the call: quote, booked meeting, no longer interested.
Fictional example: after a month, an accounting office notices that requests booked for 8 a.m. end without contact far more often than those booked for 4 p.m. So it drops the earliest slots. If your problem is rather customers' calls that you miss, start with our guide to missed calls from customers. Set reminders so they do not drown out the rest of your work; urgency levels are covered in our article on customer service notifications.
Questions about calling back leads
Should I call from my personal number if the business line is busy? Better not. The customer should see the same number on every attempt, the one you gave in the confirmation. Otherwise each attempt looks like a stranger calling.
Will Meetlead call the customer again by itself after a failed attempt? No. Meetlead does not dial numbers automatically or send SMS messages. It accepts a request with a chosen time, lets one person claim it, reminds you about the next attempt in the mobile app and keeps the status and the ticket. A person makes the call.
