Before you pay for more leads, find out what happens when one calls and nobody picks up. An ad can do its job perfectly and still lose the customer at the phone.
This is the missed-call test from the video: when to call, what to watch, how to walk one missed call through with your team, and how to give every callback one name. There's a log to print, a rule to copy, and a prompt for Claude or ChatGPT.
Why call your own office first
More leads means more phone calls. If calls already slip through at lunch or after hours, more leads just means more customers slipping through. That's the expensive way to find out.
The test is cheap. You call, you let it ring out, and you watch three things:
- Does the missed call show up anywhere? A call log, a text alert, an email, your customer system.
- Does a rep get it? Is it clear whose job the callback is? (A rep is whoever calls customers back: an office manager, a dispatcher, a salesperson.)
- Does anybody call back? And when?
Before you call
- Use a number they won't recognize, that can be called back. A spare cell, or a family member's phone with their OK. Don't hide your caller ID. The whole test is whether someone calls back, so they need a number to call.
- Pick a test name. Something like "Jordan Sample," so the test is easy to find and clean up later.
- Pick your times. Right at lunch, and after you close. Those are where the gaps hide.
- Don't announce it. Don't tell the team the time. Do tell them afterward that you were testing the process, not them.
- Print the log. It's in "Copy this" below.
The missed-call test, step by step
Call at lunch and let it ring out
Call during lunch. Don't hang up early. Let it ring until something happens. Write down the time and what you got: voicemail, a menu, a full mailbox, a text back, or ringing forever.
Leave a message on one call, not the other
Some callers leave a voicemail and some just hang up. Test both. On one call, leave a short, normal message with your test name: you'd like a quote, please call back at this number. On the other call, hang up without a message.
Call again after hours
Same thing, after you close. Listen to the greeting. Does it say when they'll hear back? Is that true?
Watch where it lands
For the rest of the day, check. Does the missed call show up anywhere? Who saw it? Did anybody call back, and when? Don't remind anyone. You're watching the process, not the people.
Walk one missed call through with your team
The next day, sit down with whoever handles the phones. Take one test call and trace it together: where it landed, who saw it, what was supposed to happen next, and what did happen.
Then ask: "Whose job was the callback?" If the answer is "whoever's free," you found the gap. Everybody figured somebody else had it.
Give the callback one name
Not "whoever's free." A name. One for each time slot: business hours, lunch, after hours. Write the role and the person, like "Office manager (Dana)." Add a backup for when that person is out. Put it where the team can see it. The callback rule below is ready to fill in.
Check tomorrow that it happened
The next morning, look at yesterday's missed calls. Each one should have a callback next to it, with the time and who made it. Keep doing the morning check until it's boring. Then run the test call again.
If your ads have a call button
If you run Google Ads with call reporting turned on, Google puts a forwarding number on your ad and keeps a record of each call. Its Call details report shows each call's status, missed or received, plus the start time and the caller's area code.
Open the Call details report
WhereGoogle Ads: the Campaigns icon → Insights and reports → Report editor → under Ads and assets, Call detailsLook for calls marked missed. Those are people your ad got to call. The report doesn't call anyone back. That's still the job with one name on it.
Call reporting is a setting: in Google Ads, go to Account settings and find the Call reporting section. If you use a different call-tracking service, look for its missed-call list instead.
Copy this: the missed-call test log
Print it and fill it in while you call. One log for each round of test calls.
MISSED-CALL TEST LOG
Test name used: ____________
Called from: _______________
CALL 1 · LUNCH Time: ______
When it rang out, I got:
[ ] Voicemail [ ] A menu
[ ] Mailbox full [ ] A text
[ ] It just kept ringing
Left a message? Y / N
CALL 2 · AFTER HOURS Time: ___
When it rang out, I got:
[ ] Voicemail [ ] A menu
[ ] Mailbox full [ ] A text
[ ] It just kept ringing
Left a message? Y / N
Greeting says when they'll
call back? Y / N True? Y / N
AFTER EACH CALL
Showed up in: ______________
Seen by (role): ____________
Called back? Y / N
When: ______ By: __________
NEXT DAY, WITH THE TEAM
Whose job was the callback?
____________________________
"Whoever's free" = the gap.Copy this: the one-name callback rule
Fill it in, print it, and put it where the phones are. Use a role and a name. A role on its own slides right back into "whoever's free."
CALLBACK RULE
Every missed call gets one owner.
Business hours:
____________ (role + name)
Lunch:
____________ (role + name)
After hours:
____________ (role + name)
Backup when they're out:
____________ (role + name)
Missed calls show up in:
____________________________
We call back by: ____________
Log each callback in:
____________ (who + when)
Next-morning check:
____________ (role + name)
reads yesterday's missed
calls. Each one needs a
callback next to it.Do it with Claude or ChatGPT
After your test calls, paste this into Claude or ChatGPT along with your notes. It maps where each call went, points at the gap, and drafts your callback rule. Use your test name only. Don't paste real customers' names or numbers.
I ran a missed-call test on my own business. I called our main number at lunch and after hours, let it ring out, and watched what happened next. Help me find where missed calls fall through, and fix it.
My business: [what you do]
Who handles the phones, by role: [e.g. office manager, dispatcher]
Our hours: [your hours]
Where a missed call can show up: [e.g. phone app, voicemail email, customer system, text alerts]
My test log:
[paste your notes: the times, what happened when it rang, where it showed up, who saw it, and whether anyone called back and when]
Please:
1. Write the path each test call took as a short numbered list. Mark the step where it stalled.
2. For each time slot (business hours, lunch, after hours), tell me whose job the callback was. If my notes don't say, write "nobody named." Don't guess.
3. Draft a one-page callback rule: one role and name for each time slot, a backup, where missed calls show up, when we call back, and where we log it. Leave a blank for anything you don't know.
4. Write a short checklist for the next-morning check.
5. Ask me anything you need, one question at a time.
Rules: plain words, short sentences. Don't promise customers a callback time in any greeting unless I tell you we can keep it. Fix the process; don't blame a person.Then read the rule it drafts out loud with your team. If anyone says "wait, that's not how it works," fix the rule before you print it.
Example (made up)
Everything here is made up: a fictional company and a test caller.
At Bayside Plumbing, the office manager handles the phones. The owner calls the main line from a spare cell as "Jordan Sample."
| Test call | What happened | Did it show up? | Called back? |
|---|---|---|---|
| 12:30 PM, lunch | Rang out to voicemail. Left a message asking for a quote. | The voicemail went to an email inbox nobody checks. | No |
| 6:15 PM, after hours | The greeting said "we'll call you back today." Hung up without a message. | Only on the desk phone's missed-call list. | No |
The next morning they walk the lunch call through together. Whose job was it? "Whoever's free." Nobody did anything wrong on purpose. The process just never named anyone.
The fix: missed calls during the day go to the office manager, Dana. At lunch and after hours they go to the dispatcher, Luis. The voicemail email now goes to both of them. The greeting now says what's true: "We'll call you back by 10 tomorrow morning." Every morning Dana reads yesterday's missed calls, and each one needs a callback time next to it.
They run the test again the next week, to make sure it stuck.
Mistakes to avoid
- Testing at an easy time. A quiet weekday morning tells you nothing. Call when it's hard: lunch and after hours.
- "Whoever's free." That's nobody. One name for each time slot, plus a backup.
- Blaming the person. A callback with no owner is a process problem. Fix the process.
- A greeting that promises what you can't do. "We'll call right back" at 9 PM is a promise. Say when you'll really call.
- Buying more leads first. Fix the callback, then turn up the ads.
- Using a real customer's number. Use a spare phone and a test name.
Otherwise we're all in a marketing meeting, wondering which font will fix voicemail.
Make the callback somebody's job
Call, let it ring out, watch where it goes, and give the callback one name. Then check tomorrow. The ad got them to call. Let's not make the customer do the follow-up too.
Checked on Oct 4, 2026 against
Every claim about a third-party tool in this guide (plans, prices, menu paths, commands, limits) was checked against these official pages on Oct 4, 2026. These screens change often: if something looks different, trust the page over this guide.
- Google Business Profile Help: Edit your business hoursHours show on your profile for Google Maps and Search; Edit profile → Hours; set a break with two entries for the same day.
- Google Ads Help: About call reportingWith call reporting on, a Google forwarding number is assigned to your ad; turn it on or off under Account settings → Call reporting.
- Google Ads Help: View details of each callCall details include start time, caller area code and status (missed or received); Campaigns icon → Insights and reports → Report editor → Ads and assets → Call details.
