Good work. Poor communication. What should you fix?

When a customer praises your work but complains about communication, address both parts. Thank them for the specific praise, acknowledge the communication concern, and privately check the promise that broke down: a callback, a time estimate, a price explanation, or a handoff.

A better public reply can acknowledge the problem. A better operating process is what you need to test next. This guide pairs three fictional Google reviews with a reply, an internal investigation, and a practical check. The scripts are examples to adapt, not real customer cases or proven fixes.

Download the communication check log (CSV). Use it in a spreadsheet to track the promise, responsible role, next update, and outcome. Keep your completed copy private and avoid customer names or account details.

Identify the communication gap before choosing a script

“Poor communication” is too vague to assign to a person or fix in a meeting. Read for the exact moment the customer describes. Did information arrive late, omit something important, conflict with an earlier message, or disappear between team members?

These are hypotheses to check, not diagnoses. A message may have been sent to an old number; an expectation may never have been agreed; a staffing explanation may be wrong. You can acknowledge the concern without inventing why it happened.

1. Good work, missed update

Fictional review: “Happy with the repair. Nobody told me it would take an extra day, so I drove over to collect it for nothing.”

Avoid: “Thanks for the great review! We are glad you loved the repair.” That ignores the part the customer most needs you to hear. Also avoid blaming a busy day before you have checked the facts.

A public reply while you investigate

“Thank you for the feedback on the repair. We are sorry the pickup update left you making an unnecessary trip. Please contact our service desk using the details on our website so we can check what happened with the change in timing.”

Use that route only if someone monitors it. If you already know how to reach the customer appropriately, follow up privately rather than making them repeat every detail in public. Google explains that approved replies appear publicly and the reviewer is notified.

The internal check

Compare the agreed pickup time, the point when the estimate changed, the recorded message, and the handoff between shifts. Confirm whether the issue was a missing update, an undelivered message, or an unclear estimate.

Possible change: When the estimate changes, the assigned adviser records the next contact time and sends an update. The promise can be “I will update you tomorrow morning,” even when the completion date remains uncertain. Promise the communication you control.

Private update example: “We are still waiting for the part confirmation. I do not yet have a reliable collection time. I will call by 10 a.m. tomorrow with what we know.” Only send it if someone has accepted that responsibility.

2. Good result, unclear price

Fictional review: “The room looked lovely after cleaning, but the final bill was higher than I expected and nobody explained the extra charge.”

Avoid: “You signed the terms, so the charge is correct.” That turns a concern about understanding into a public argument and may disclose account information. It also skips the question of whether the charge was actually approved.

A public reply while you check the bill

“We appreciate your feedback on the cleaning. We are sorry the additional charge was unclear. Please contact our office through the details on our website so the manager can review the estimate and invoice with you privately.”

This does not promise a refund or declare the charge valid. Once you investigate, give the customer the actual explanation and any authorized remedy through the private channel.

The internal check

Review the original scope, any change in work, the estimate, and the approval record. A charge can be correctly calculated and still poorly explained; it can also be an error that requires correction. Do not decide which from the star rating.

Possible change: Before additional work proceeds, explain what changed, the revised price, and the available options, then record the customer’s decision according to your business process. This is a workflow example, not a substitute for applicable contract requirements.

Check: For the next relevant jobs, can another team member find the explanation and decision? A new script alone is not evidence that customers received it.

3. Helpful people, repeated explanations

Fictional review: “Everyone was polite, but I explained the same issue to three people and still did not know who would call me back.”

Avoid: “Please call again and ask for another department.” If a transfer is necessary, arrange who accepts it rather than sending the customer back to the start.

A public reply with a clear next step

“Thank you for explaining this. We are sorry you had to repeat the issue without a clear callback. Please use the contact details on our website and ask for the duty manager, who can coordinate the follow-up.”

Confirm the duty manager can actually accept the handoff before using that wording. If you have already assigned the case privately, the public reply can simply acknowledge the concern without requesting another contact.

A handoff note your team can use

• Customer’s requested outcome: What are they asking us to resolve?
• Verified so far: What did we check, and what is still uncertain?
• Current owner: Who has accepted responsibility for the next step?
• Next message: When and how will that person contact the customer?
• Approval needed: Who can authorize a remedy if one is required?

Keep personal information in the appropriate private system. The public reply, team coaching note, and customer record do not need to contain the same details.

Check whether the change happened before claiming improvement

Choose one complaint type and one process change. Use the downloaded log for a small run of relevant jobs. Record what was promised, whether the update happened, and what remains unresolved. These are proposed operating checks, not universal service benchmarks:

• Changed timelines: Did the customer receive an update before the previous contact promise expired?
• Additional charges: Was the change explained and the decision recorded before the additional work?
• Handoffs: Did a named person accept the next step without asking the customer to start again?

Report counts with their context: “7 of 9 changed-time jobs had an update before the promised callback.” That fictional result would leave two exceptions to investigate. It would not show that every customer was satisfied or that the change caused better Google ratings.

Compare later review themes over consistent periods, but keep them separate from the process check. New reviews may be few, and different customers may choose to respond. For a fuller method, see how to analyze Google review feedback.

Give the team a change they can practice

Use the 15-minute staff meeting agenda to rehearse the next update or handoff. For complaints involving safety, privacy, discrimination, or a disputed transaction, involve an authorized manager before drafting a detailed public response.

Reply Champion can help organize Google review feedback and prepare replies for review. Its sample Review Intelligence report shows suggested actions; it does not check your invoices, contact your customer, or verify a resolution. Explore customer feedback analysis when you need a regular view of what your reviewers are reporting.