How to Respond to a Google Review About Unanswered Calls

A woman woke up to water spreading across her kitchen floor from a leaking water heater, grabbed her phone, and called the plumber whose magnet was on her fridge. It rang out and went to voicemail. She called again, then a third time, then left a message. No one called back. Twenty minutes and a growing puddle later, she called the next plumber on the list, who picked up on the second ring. The first plumber lost the job and earned a one-star review titled "called four times during an emergency, never picked up, never called back."

A phone-call complaint sits in its own corner of the negative-review world, because it is rarely about a single missed call. It is about reachability. The customer is not arguing that you owe them a perfect phone day, they are telling future readers that when they needed you, they could not get through, and for most local businesses being reachable is the entire point.

That is also what makes it dangerous. The next person reading that review is often holding a phone, deciding whether to call you or the business below you, and "never picked up, never called back" answers their question before they dial.

Quick Answer: Figure out which phone failure you got, because the complaint covers four gaps: an unanswered call (it rang out or hit voicemail), an unreturned call (a message or promised callback that never came), the runaround (long holds, an endless menu, or circular transfers), and the brush-off (they reached a person but got rushed off or hung up on). Acknowledge the customer by name and name the exact failure, own it without blaming call volume or staffing, and give them a real way to reach you now plus the fix you are making. Keep it to three or four sentences and move the resolution to a named contact. For the broader framework, see our complete guide to responding to Google reviews.

In this guide, you will learn:

• Why a phone-call complaint is really a reachability dispute, not a one-off bad day
• The four kinds of phone complaint, and why naming the type is the first move
• A four-part formula that owns the gap without making excuses
• Templates for eight common phone scenarios across clinics, contractors, salons, and shops
• What never to say when a customer flags a phone problem, including the "we were slammed" trap
• How to fix the phone and callback problems that quietly generate these reviews

Why a Phone Complaint Is Really About Reachability

Most negative reviews describe a thing that happened: the food was cold, the room was loud, the deposit was kept. A phone-call review describes a thing that did not happen, a connection that never got made, and that absence is exactly what makes it sting. The customer reached out, got nothing back, and is now telling everyone that you are hard to reach.

That is why "we were very busy that day" is such a weak shield. It is true, and it convinces no one. To the reader it sounds like a business that is unreachable precisely when people need it, and "unreachable when busy" is the impression that costs you the next call, because busy times are when customers call most.

It helps to see that "phone complaint" actually covers four different failures, and the right reply depends entirely on which one you got.

Unanswered: the phone rang out or went to voicemail. The most basic failure and the most common. The customer called, no one picked up, and either there was no voicemail or they did not bother leaving one. They feel like the door was locked during business hours. The reply has to own that a call going unanswered is a real gap, not a customer expecting too much.

Unreturned: a message or promised callback that never came. This is the broken-promise version, and it often stings more than never reaching anyone, because the customer trusted that you would call. They left a voicemail, filled out a form, or were told "someone will get back to you," and then waited. This type overlaps heavily with reviews about communication.

The runaround: long holds, an endless phone menu, or circular transfers. This is the wasted-time version. The customer did get through to your system, but the system made reaching a human feel deliberately hard. Fifteen minutes on hold or a menu that loops back on itself reads as a business that does not respect the caller's time.

The brush-off: they reached a person, but got rushed off or hung up on. This is the human version, where a real interaction went wrong on the phone, rushed off the line, told to call back later, or disconnected mid-sentence. It overlaps with reviews about rude staff, but the channel matters: being brushed off on the phone, when you finally got through, feels like a second rejection.

A reply that says "we are sorry we missed your call" answers none of these well. The unanswered customer wanted to know they can reach you now. The unreturned customer wanted you to admit the callback was dropped. The runaround customer wanted a faster path. The brush-off customer wanted to be treated like the call mattered. The first job is to read the review and decide which failure you are actually answering.

The First Move: Diagnose Which Phone Complaint You Got

Before you draft anything, read the review and settle which of the four types it is, because the entire response hinges on that call. The same complaint, "I couldn't reach you," points in four different directions, so look for the specific cue.

A few questions to answer before you type.

Did they fail to reach anyone, or fail to get a callback? If the customer called and no one picked up, you are in an unanswered complaint, and the question is how to prove you are reachable now. If they left a message or were promised a return call that never came, you are in an unreturned complaint, and the question is a dropped promise and a broken callback loop. These need different replies, one offers a direct line, the other owns the broken commitment.

Did your system reach them, or did it wear them down? A customer who writes "I was on hold for twenty minutes" or "I kept getting transferred" did get through, but your phone setup punished them for it. That is the runaround, and the reply has to value their time and offer a shortcut, not defend the menu.

Was there a real interaction that went badly? If the customer reached a person and was rushed off, told to call back, or hung up on, this is the brush-off, and it overlaps with customer-service reviews. The reply has to treat the interaction itself as the failure, not just the phone.

Were the stakes high? Be honest about timing, because it decides how hard you lean in. A missed call about store hours is different from a missed call during a plumbing emergency, a sick pet, or a medical question. Future readers can feel the difference too, and a casual reply to a high-stakes miss reads worse than the missed call ever did.

The owner reflex on a phone review is to reach for "we were short-staffed" or "we never received your call," because from inside the business those feel like proof you did nothing wrong. But the customer did not experience your staffing or your call logs, they experienced reaching out and getting silence. Diagnose the type, then answer the reachability question that type raises, as an owner who wants the next call to land.

The Four-Part Formula for a Phone-Call Review Response

Every reply to a phone complaint should hit the same four beats, whether the call was unanswered, unreturned, lost in a menu, or brushed off. The whole response fits in three to four sentences.

Step 1: Acknowledge the customer by name and the specific failure

Open with the first name from the review and a direct acknowledgment of what actually happened. Name the failure, including the detail they gave. "Sorry we missed you" is too vague to land. "You called four times during a water-heater emergency and could not reach anyone, and that is exactly the moment we should have answered" tells the customer you read their story, not just their star rating.

Say this: "Hi Dana, you called us four times while your water heater was leaking and could not get through or get a callback, and I am genuinely sorry we left you stranded at the worst possible moment."

Not this: "Dear Customer, we apologize for any difficulty you experienced contacting our office."

Step 2: Own it without excuses

This is the step that separates a transparent reply from a defensive one. Take responsibility for being hard to reach in plain language, and do not blame call volume, staffing, or your phone provider. Do not say you have no record of the call, and do not imply they called the wrong place. The goal is for a stranger to read your reply and think "they own it," not "they have a reason for everything."

Say this: "There is no good reason a call like that should go unanswered, and being hard to reach when someone needs us is on us to fix, not on you to work around."

Not this: "We were experiencing an unusually high call volume and were short-staffed that day."

Step 3: Give them a reliable way to reach you now

A phone complaint is, at its core, a customer saying they could not get through. So hand them a path that works: a direct number, a named person, a text line, or online booking, and where you can, resolve the original reason they called. This is the phone equivalent of making it right, you are proving the next attempt will land.

Say this: "Please reach me directly at [phone] or text [number] and I will make sure you get same-day help, no phone tree and no waiting on hold."

Not this: "Please try calling back during our regular business hours."

Step 4: Move the resolution to a named contact and name the fix

Hand the real resolution to a named person so the customer feels like someone reached out, not like a complaint got managed. Then, briefly, signal the change you are making, because future readers want to know it will not happen to them. Keep the fix concrete, not a vague promise to "review our process."

Say this: "Ask for me, Marcus, and I will sort out your repair personally. We have also added a second line and a callback log so emergency calls stop slipping through."

Not this: "Your feedback has been forwarded to the appropriate department for review."

Response Templates for Common Phone-Call Scenarios

These templates follow the formula. Fill in the name, the situation, the contact details, and the fix that matches what actually happened. Avoid copy-pasting the same wording across multiple phone reviews. Future readers and the AI-generated business summary both scan for repetition, and a row of identical "sorry we missed your call" replies reads worse than a row of slightly different honest ones.

Template 1: Call rang out, no answer (shop or restaurant)

"Hi [Name], you called during our open hours and could not get anyone on the line, which is frustrating when you just need a quick answer. That is on us, not on you. Please reach me directly at [phone] or [email]. We have added phone coverage during our busy stretches so calls stop going unanswered, and I would still love to help with whatever you were calling about."

Template 2: Voicemail or message never returned (service business)

"Hi [Name], you left a message and waited for a callback that never came, and a dropped promise like that is worse than a busy signal because you trusted us to follow up. Please reach me at [phone] or [email] and I will handle your request personally today. We have put a callback log in place so every message gets an owner and a return call, and yours should never have slipped."

Template 3: Stuck on hold for too long (clinic or call-heavy office)

"Hi [Name], waiting that long on hold just to get a simple answer is not a fair ask, and I am sorry we put you through it. Please reach me directly at [phone] or text [number] and skip the hold entirely. We are adding staff to the phones at peak times and a callback option so you can hang up and we call you, instead of you waiting on the line."

Template 4: Endless phone menu, could not reach a human (larger service business)

"Hi [Name], fighting a phone menu to reach an actual person is the opposite of what you wanted, and that is a setup problem we own. Please call me directly at [phone] and you will get a human, no menu. We are shortening the menu and adding a clear option to reach a person right away, because no one should have to work that hard to talk to us."

Template 5: Reached someone but got rushed off the line (the brush-off)

"Hi [Name], you finally got through and then felt rushed off the phone, which makes reaching us feel pointless. That is not how we want any call to go. Please reach me at [phone] or [email] and I will give your situation the time it actually needs. I have spoken with the team about slowing down on calls so people feel heard, not hurried."

Template 6: Could not reach you during an emergency (plumber, HVAC, vet, locksmith)

"Hi [Name], you needed us in an emergency and could not get through, and that is the single worst time for a call to go unanswered. I am sorry we were not there. Please save my direct line, [phone], for anything urgent and you will reach me or someone who can help. We have set up after-hours and overflow coverage so an emergency call never rings out again."

Template 7: Listed phone number was wrong or disconnected (listing problem)

"Hi [Name], it sounds like the number you called was out of date or not working, which means you did everything right and our listing failed you. Thank you for flagging it. Please reach me at [phone] or [email], our current line. We have corrected the number on our Google listing so the next person gets straight through."

Template 8: Transferred in circles, no one could help (multi-department)

"Hi [Name], being passed from person to person without anyone solving your problem wastes your time and ours, and I am sorry it played out that way. Please reach me directly at [phone] and I will own your issue from start to finish, no transfers. We are fixing how calls get routed so one person can actually help instead of handing you off."

Drafting calm, non-defensive phone-call replies adds up across a busy week. Try our free AI response generator for a clean, on-brand starting draft in seconds, no signup needed.

What Never to Say in a Phone-Call Review Response

Each line below shows up in phone replies that backfire. Each one reads worse to future readers than no reply at all, and several follow the listing for months because they get pulled into the AI-generated business summary or the snippet shown on Google search.

Do not blame call volume or short staffing

"We were extremely busy and short-staffed that day" is the single most common phone-reply mistake, and it loses every time. To the reader it does not explain the miss, it predicts the next one, because busy is exactly when they will call. Own that being hard to reach is a problem you are fixing, and let your reply point to a path that works now rather than a reason it did not work then.

Do not say you have no record of the call

"We have no record of receiving your call" calls the reviewer a liar in public, and future readers side with the caller almost every time. The call may have hit a full voicemail box, a forwarding error, or a wrong number on your listing, all of which are your systems, not their imagination. Acknowledge that they tried and could not get through, and investigate privately through a named contact if you really need to.

Do not tell them to just call back

"Please try calling again during business hours" answers a complaint about being unreachable by asking the customer to try the thing that already failed. It reads as a brush-off on top of a brush-off. Give them a better path instead, a direct line, a text number, or online booking, so the next attempt does not depend on the same overloaded line.

Do not hide behind a vague "we'll look into it"

"We will review our phone process" is the sentence that tells a reader nothing will change. A phone complaint is specific, the customer named the unanswered call, the dropped callback, or the endless hold, so the reply has to name the same thing and a concrete fix, even if that fix is simply a direct contact and a real callback commitment.

Do not defend the phone menu or the hold time

"Our menu helps us route your call to the right department" defends the exact thing the customer hated. No caller cares about your routing, they care that reaching a human was hard. Acknowledge that the system asked too much of them and offer a shortcut, rather than explaining why the obstacle exists.

Do not use generic apology language

"We apologize for any inconvenience this may have caused" is the sentence that defines a business answering every negative review with the same template. Not being able to reach you in a moment of need is not an inconvenience, it is the customer feeling abandoned, and treating it as a minor hiccup tells future readers you did not really hear the complaint.

For the broader pattern on what to avoid, see our guide on what not to say in review responses, and for the discipline of staying calm under a frustrated complaint, our guide on responding to a bad review without being defensive.

Fixing the Source Problems That Generate These Reviews

The most reliable way to cut phone reviews is not better replies, it is making your business genuinely easy to reach so a customer never feels abandoned in the first place. A large share of phone complaints trace back to a handful of fixable gaps, and most are far more solvable than owners assume.

Make sure your listed number works and rings to a real person. A wrong or disconnected number on your Google Business Profile quietly generates "no one answered" reviews from people who did everything right. Verify the number is current and that it actually reaches a human during your hours, the same way a clean profile prevents other avoidable complaints, which is worth checking during a Google Business Profile audit.

Build a callback loop that actually closes. A voicemail that no one owns is a review waiting to happen. Log every message, assign each one a person, and confirm it gets returned within a set window, so "I left a message and never heard back" stops being true. A dropped callback is the most preventable phone complaint there is.

Offer visible alternatives to the phone. Not everyone can wait on hold, especially during the workday. Make text, web chat, and online booking easy to find and clearly offered, so a customer who cannot get through by phone still has a way in. A second channel turns a missed call into a captured one.

Cut the menu and the hold. If callers have to fight a phone tree or wait fifteen minutes, shorten the menu, add a clear "press zero for a person" path, and staff the phones during your busiest hours. A caller who reaches a human in under a minute almost never writes a phone review.

Use a voicemail greeting that makes a promise you keep. If you genuinely cannot always answer, say so on the greeting, give a realistic callback window, and then beat it. A clear "we return all calls within two hours during business hours," followed by an actual callback, prevents far more reviews than an endless ring ever will. Being reliably reachable, even by callback, is the same responsiveness that helps you respond to reviews faster once they post.

When Phone Complaints Become a Pattern Worth Tracing

A single phone review reads as a possible one-off, a bad day on a busy line you can explain and move past. Several phone reviews naming the same gap read as a structural problem the business has chosen not to fix, and that pattern carries real weight, because "you can't reach them" spreads fast among people deciding whether to call you at all.

A few signals that the pattern is worth tracing.

Repeated "no one answers" complaints. When multiple reviews say the phone rang out, the problem is not the callers, it is your phone coverage or your listed number. The fix is staffing, routing, or a working line, not a better-worded reply. This is the most common phone pattern and one of the easiest to solve.

Repeated "left a message, never heard back" complaints. When several reviews name a dropped callback, your callback loop is broken, not your customers. Messages are coming in and dying somewhere, and the fix is a system that assigns and confirms every return call.

Phone complaints alongside communication, customer-service, and missed-appointment reviews. When phone reviews show up next to communication, customer-service, and missed-appointment reviews, the business has a broader responsiveness gap rather than one isolated phone problem. Reading them together tells you customers struggle to reach and rely on you, which is worth more attention than any single reply.

For the broader framework on review patterns and what they signal, see our guide on Google review analytics.

Protecting the Front Desk Through the Process

Phone duty usually falls on the front-desk or reception staff, the people juggling a ringing line, a lobby full of customers, and a stack of messages all at once. A phone review can land hard on them, because being named in a one-star review for a call you could not get to while you were helping three other people is a demoralizing spot to be in. How the owner handles it decides whether the team gets better at these moments or just gets defensive.

A few small habits make it healthier.

Tell the team about the review yourself, before they see it. Walking into a shift already knowing a phone review is on the listing is far better than discovering it through a customer screenshot or a tagged post in the team chat.

Separate the system from the person. "One line cannot cover our busy hours, so let us fix the coverage" lands very differently from "why didn't you answer the phone." The first treats reachability as a system the whole team can improve. The second blames an individual for a gap they did not design.

Give the front desk the tools to actually keep up. Most phone complaints escalate because one person physically cannot answer every call and return every message alone. A shared callback log, a second line at peak times, or an overflow path takes the pressure off staff and stops messages from dying in a stack.

Track the changes that came out of the review. A simple log of "phone review on [date] led to peak-hour phone coverage on [date] and a new callback system" gives the team visible proof the feedback is shaping the business. Reviews that change nothing land as noise. Reviews that lead to a real change land as evidence the work matters.

Teams that have enough coverage to answer and a reliable loop to call people back are the ones who quietly prevent the next phone review before a customer ever has to write it.

Frequently Asked Questions

How do you respond to a Google review about not being able to reach you by phone?

Start by figuring out which phone failure you got, because the complaint covers four different gaps: an unanswered call (the phone rang out or went to voicemail), an unreturned call (a message or promised callback that never came), the runaround (long holds, an endless phone menu, or circular transfers), and the brush-off (they reached a person but were rushed off or hung up on). Acknowledge the customer by name and name the exact failure, own it plainly without blaming call volume or staffing, and give them a real, reliable way to reach you right now along with the fix you are making. Keep the public reply to three or four sentences and move the actual resolution to a named person or direct line.

Should you apologize if you think the customer never actually called?

Yes, you still own the experience, even if you are not certain the call reached you. Leading with we have no record of your call reads as calling the reviewer a liar, and future readers side with the customer almost every time. The call may have hit a full voicemail box, a forwarding error, a wrong number on your listing, or a staff member who never logged it, all of which are your systems failing, not the customer inventing a story. Acknowledge that they tried and could not get through, say being hard to reach is a real problem you take seriously, and give them a direct line to a named person. If you genuinely need to investigate, do it privately, never as a public accusation.

What do you say when a customer says no one ever called them back?

An unreturned call is a broken promise, not just a missed task, so treat it as one. The customer left a message or was told someone would call, trusted that, and then waited, which feels worse than never reaching anyone because they expected to hear back. Acknowledge the specific promise that was dropped, own that an unanswered message is on your callback system and not on them, and close the loop now by giving them a direct contact and, if you can, handling the original reason they called. Avoid vague lines like we will look into our process, because a callback complaint is specific and the reply has to be specific too. Then fix the cause: log every voicemail, assign each one an owner, and confirm the loop is closed.

How do you respond to a review about being stuck on hold or an endless phone menu?

The customer is telling you their time was not respected, so the reply has to value it. Long holds and circular menus feel like a business that made reaching a human deliberately hard, which is a worse impression than a single dropped call. Acknowledge that waiting on hold or fighting a menu to get a simple answer is genuinely frustrating, own that the system asked too much of them, and give them a faster path, a direct number, a name, a text line, or online booking, so they never run the gauntlet again. Avoid defending the menu as necessary for routing, because no caller cares about your routing. Then fix the source: shorten the menu, add a clear press-zero-for-a-person option, and staff the phones at peak times.

How do you stop "no one answers the phone" complaints from showing up in your reviews?

Most phone reviews trace back to a reachability gap, not a one-off bad day, so fix how callers actually reach you. Make sure the number on your Google Business Profile is correct and rings to a real person, because a wrong or dead number quietly generates these reviews. Build a callback loop that works: log every voicemail, give each one an owner, and confirm it gets returned. Offer visible alternatives like text, web chat, or online booking for customers who cannot wait on hold, and staff the phones during your busiest hours. Use a clear voicemail greeting that promises a callback window you actually keep. Businesses that are genuinely easy to reach get far fewer reachability reviews than businesses with one overloaded line and no backup.

Is it worth responding to a phone-call review if the problem is just that you are short-staffed?

Yes, and the one thing to avoid is using short staffing as your public excuse. We were short-staffed that day is true inside the business and useless to the reader, because the customer did not get the service they needed regardless of why, and future callers hear it as expect to not reach us when we are busy, which is exactly when they will call. Respond by acknowledging the missed contact, owning that being hard to reach is a real problem, and giving a reliable way to get through now. You can mention you are actively working on phone coverage, framed as a fix you are making rather than a reason it happened. Staffing is the cause you address quietly through scheduling and overflow routing, not the defense you lead with.

The Bottom Line

A phone-call review is not really about one missed call, it is about whether customers can reach you when they need to, and that is why "we were busy" never works. The complaint covers four different failures, unanswered, unreturned, the runaround, and the brush-off, and the reply only lands once you figure out which one you got. Name the failure, own it without excuses, and then give the customer a path that actually works, while signaling the fix that keeps the next caller from writing the same review.

Key Takeaways:

• Diagnose the type first. Unanswered, unreturned, the runaround, and the brush-off are four different complaints that need four different replies.
• A phone complaint is a reachability dispute, not a one-off bad day. Answer the "can I reach you now" question.
• Never blame call volume or short staffing in public. It does not explain the miss, it predicts the next one.
• Never say you have no record of the call. It reads as calling the reviewer a liar, and readers side with the caller.
• Do not tell them to just call back. Give a better path, a direct line, a text, or online booking.
• Give a reliable way to reach you now and move the resolution to a named contact.
• Fix the source: verify your listed number, build a callback loop that closes, offer alternative channels, cut the menu and the hold, and keep your voicemail promise.
• A pattern of "no one answers" or "never called back" reviews is a coverage and callback problem to fix, not a reply problem to repeat.
• Protect the front desk: separate the system from the person, and give staff the coverage and tools to actually keep up.

For the broader framework, see our complete guide to responding to Google reviews. For related cluster guides, see responding to a review about communication, responding to a review about customer service, and responding to a review about a missed appointment.

---