Handling a Negative Google Review as a Mortgage Broker (Without Breaching Confidentiality)

18 August 2026·6 min read

Quick answer: The biggest risk in responding to a negative Google review as a mortgage broker isn't sounding defensive — it's accidentally confirming, in a public reply, that the reviewer was ever a client, which can breach privacy obligations before you've said anything about the file itself. The safe process is a short public reply that never confirms a client relationship, a private follow-up to actually resolve it, an internal record, and — if it's still unresolved — a clear path to AFCA. Below is the exact script, the escalation ladder, and the mistakes that turn a one-star review into a bigger problem. 🤍

Every broker gets one eventually — the review that lands on a Friday afternoon and ruins your weekend. The instinct is to reply immediately, defend the file, and set the record straight. That instinct is exactly what gets brokers into trouble, because the fastest way to make a bad review worse is to confirm, in public, that the person was ever your client. Getting this right isn't about winning the argument — it's about protecting the client's privacy while still showing every future prospect reading your profile that you handle problems like a professional. 💖

Please note: general information, not financial or legal advice — check current ASIC/NCCP guidance and your best-interests-duty obligations before relying on it.

What most mortgage brokers get wrong when a bad review lands

Replying within the hour, while still angry — the first draft is rarely the one that should go live.
Confirming in public that the person was a client — writing "Sorry we couldn't get your loan approved, John" breaches confidentiality even if everything after it is polite.
Arguing the facts in the review section — a public back-and-forth about file details reads worse to every future reader than the original review did.
Not keeping an internal record of the reply — no paper trail of who responded, when, or what happened next.
Assuming a bad review means a complaint is coming — most are resolved with a calm private conversation, and escalating your own tone before you need to just adds heat.

The four-step response script (copy and adapt)

Step 1 — Public reply, within 24-48 hours, never confirm a client relationship:

"Thanks for taking the time to leave feedback. We take all feedback seriously and would really like to understand what happened here — could you please contact us directly at [email/phone] so we can look into this properly? Client privacy means we won't discuss specifics publicly, but we're genuinely keen to make this right."

Step 2 — Private follow-up, call rather than email where possible:

"Hi [name], thanks for reaching out. I wanted to understand what happened from your side, and explain a couple of things about the process that might help. [Listen fully before explaining anything.] Is there something we can do to resolve this for you?"

Step 3 — Internal escalation record: log the review date, your public reply, the private conversation outcome and any follow-up commitments in your CRM or complaints register, even if it resolves in one phone call.

Step 4 — If unresolved, formal complaints process then AFCA: point the client to your written internal dispute resolution process first. If it's still unresolved after that, they're entitled to take it to the Australian Financial Complaints Authority — mention this calmly, as a normal part of the system, not a threat.

Review about a declined loan: A one-star review said "Wasted three weeks then declined me, terrible broker." The public reply avoided confirming anything at all beyond inviting contact — no "sorry your application was declined." The private call revealed the lender's servicing calculator had changed mid-application, which nobody had explained clearly at the time. The broker followed up in writing with two other lenders' criteria, and the reviewer amended the review to three stars a week later.

Review about slow communication: "Took five days to return a call, very disappointing." Public reply stayed generic — invitation to discuss, no confirmation of client status. Private follow-up found the client had emailed a shared inbox that wasn't checked daily, a process gap rather than a one-off. Fixed it with an autoresponder and a same-day triage rule, then, once resolved, asked whether the reviewer would consider updating it — no pressure, just an honest ask.

Review from someone who was never a client: A review named the brokerage but described a loan type they don't even write. The public reply stayed identical to the standard script — inviting contact, no denial, no "we have no record of you." Flagging it for removal through Google's review policy, rather than arguing in the replies, was the right move, since a public denial can look defensive even when it's true.

Why the public/private split actually matters

A public reply that confirms a client relationship — even implicitly — can be read as a disclosure issue, especially in a profession handling sensitive financial information. A calm, generic public reply is enough to show prospective clients you're professional and take feedback seriously; the actual resolving happens privately, away from public view. Keeping an internal log matters too, because if a complaint ever does progress further, having evidence you tried to resolve it promptly and appropriately is exactly what a proper internal dispute resolution process is meant to show.

💡 Heads up: Even writing "we have no record of working with you" in public can be read as commentary on your client records — keep the public reply identical in tone whether the reviewer was a client, a prospect who never proceeded, or a stranger, and save any specifics for private contact or a formal flag to Google.

Mistakes that make a bad review worse

Ignoring it entirely — silence on a visible one-star review often reads as guilt to anyone else researching you.
Getting into a public back-and-forth — every exchange stays visible to everyone who looks you up later.
Using a template that's obviously copy-pasted — readers can tell, and it undoes the warmth the reply is meant to show.
Escalating to legal threats too early — a firm, calm process almost always resolves things without a lawyer's letter.
Not training the whole team on the same protocol — one person replying warmly and another replying defensively looks inconsistent across your review history.

Frequently asked questions

Can I ask Google to remove a fake or defamatory review?

Yes — you can flag it through Google's review policy if it violates their rules (fake, off-topic, conflict of interest), or lodge a legal removal request for genuinely defamatory content. It's not fast and it's not guaranteed, so running the standard response process in parallel is worth doing regardless of whether the flag succeeds.

Do I have to respond to every negative review?

Not every single one — a lone old review with no ongoing relevance can sometimes be left alone. But most one and two-star reviews benefit from at least the standard public reply, both for the reviewer and, more importantly, for every future prospect reading your profile afterward.

What if the review is about something that genuinely went wrong?

Then it might be the most useful thing that happens to your process that month — a real service or communication gap you can fix once, for everyone who comes after them, rather than something to argue away.

Should I mention AFCA in my public reply?

No — AFCA belongs in the private conversation or your written internal dispute resolution response, not the public review reply. Raising it publicly can read as combative even when you mean it as a genuinely helpful next step, and it isn't something the public reply is designed to carry.