Setting up a 24-hour callback window for missed calls
Most service businesses lose 15-30% of inbound leads to missed calls. A structured 24-hour callback discipline recovers most of them. Here's how to build one.
Most service businesses lose meaningful revenue to missed calls. The phone rings, no one answers (busy, lunch, after-hours, technician in the field), the customer hangs up, and depending on the urgency of their need, they're either calling the next listing or moving on to a competitor.
Industry data suggests 15-30% of inbound calls in residential trades go unanswered on the first attempt. Of those, less than half ever get followed up by the business. The rest become competitors' customers.
A structured 24-hour callback discipline recovers most of the recoverable revenue. Here's how to build one.
The basic mechanic
Every missed call enters a callback queue. Every entry in the queue gets called back within 24 hours.
Sounds obvious. The implementation has more layers.
What the queue should track
For each missed call:
- Caller's phone number
- Time of original call
- Source (which advertised number rang? — gives you channel attribution)
- Voicemail content (if any)
- Last callback attempt (timestamp)
- Status (new, called once, called twice, contacted, dead)
Most modern phone systems surface this automatically. If yours doesn't, a simple shared spreadsheet works for low volume.
The callback cadence
Within 1 hour during business hours. This is the highest-conversion window. A customer who called 30 minutes ago is still in problem-solving mode. Calling them back fast feels like good service.
Within the first business hour after-hours calls. A call that came in at 9 PM Tuesday gets called back at 8 AM Wednesday, not 4 PM.
Within 24 hours, no exceptions. Even calls that don't fit the "high urgency" pattern. Some of these are loyal customers, some are scheduling routine work, some are emergencies you misclassified as routine. All are worth calling back.
What to say on the callback
Identify yourself by name and business immediately. "Hi, this is Sarah at ABC Plumbing. I'm calling back about a missed call from earlier today."
Don't apologize excessively. "Sorry we missed you" once is fine. Three apologies in a row makes the experience worse.
Get to the point quickly. "How can we help?" If the customer has a clear ask, hear it. If not, ask: "Were you calling about service, a quote, or something else?"
If they don't pick up. Leave a voicemail naming yourself, the business, the original missed-call time, and a callback number. "Hi, this is Sarah at ABC Plumbing returning a missed call from this afternoon. You can reach me back at 555-1234, or I'll try you again tomorrow morning."
Send a follow-up SMS. Same text as the voicemail, sent right after. Many customers prefer SMS — particularly for non-emergency callbacks. SMS-based callback often catches customers that voicemail doesn't.
What to do when there's no answer
Try twice on day 1. Once during the originally-attempted callback window. Once toward end of business day.
Try once on day 2. Different time of day from day 1.
SMS handoff after 3 unanswered attempts. "We've tried calling a couple times — feel free to text back here when convenient, or you can reach us at [phone] any time."
Mark dead after 5-7 days of no response. At that point the customer has either solved the problem elsewhere or wasn't really in market. Move on.
Special cases
Emergency-keyword voicemails. "Water everywhere" / "no heat" / "smoke" should jump the queue. Configure phone-system keyword detection if available, or have whoever processes the queue scan voicemails before triaging.
Recurring customer callbacks. Voicemails from customers in your existing book go to the front of the queue. They've already trusted you with their business; making them wait erodes that trust.
Callbacks from competitor poaching attempts. Common pattern: a customer calls multiple service providers; whoever calls back first gets the job. Speed matters disproportionately for new-customer acquisition calls.
Measuring effectiveness
Track these metrics weekly:
- Missed-call volume (total)
- Callback completion rate (callbacks made within 24 hours / total missed calls)
- Connect rate (callbacks that reached the customer / callbacks attempted)
- Conversion rate (callbacks that became booked jobs / callbacks that connected)
- Revenue from callbacks (rough attribution)
Healthy numbers for a residential service business:
- Callback completion rate: 95%+
- Connect rate: 50-70%
- Conversion rate from connected callbacks: 25-40%
If your callback completion rate is below 90%, you have a process problem. If your connect rate is below 50%, your callback timing or your messaging needs work. If your conversion rate is below 25%, your sales conversation on the callback is the bottleneck.
What it's worth
For a typical residential operator with 200-400 inbound calls per month and a 20% miss rate:
- 40-80 missed calls per month
- 20-40 of those reachable on callback
- 5-15 of those conversions
- At an average ticket size of $400, $2,000-$6,000 in monthly revenue from disciplined callbacks
That's $24k-$72k per year from a process most operators don't have. The cost is one office staff member doing 1-2 hours per day of structured queue work.
For phone setup that surfaces the missed-call queue automatically and integrates with your dispatch board, see how ServiceGrid's phone subsystem handles inbound, missed-call queue, and callback discipline.