Reviews Are a System, Not a Favor
Most firm owners know they need more reviews. They also know how it usually goes. Someone at the front desk is told to ask. A few clients who seem happy get an email. Then a busy month hits, the asking stops, and the rating sits still for a year.
It feels like a people problem, but it is not. You do not have a review problem. You have a review system problem. Firms that grow their rating are not asking harder. They decided when the ask happens, how it is sent, and who receives it. That last part is simple: every client, every time.
Why reviews matter more than they used to
Reviews have always shaped who gets the call. Now AI tools read them too. When someone asks ChatGPT for a firm in your city, the engine reads your reviews before it reads your homepage. Recent, steady, well-answered reviews feed Google and the AI tools that read them. So a review program is no longer only about your star rating. It is part of how your firm gets found, trusted, and cited by name.
This is the job of the Reputation Engine: a tuned Google Business Profile, a review request to every client, review alerts, and replies written by a person. It also includes missed-call text-back and website capture, which later modules cover.
The ask belongs at the right moment
Every firm has a natural point when the work is done. The matter closes. The treatment plan works. The closing funds. The plan is delivered. That point is when the request should go out.
The most common mistake is asking at the wrong time, usually at invoice time. A client who just received a bill is not in the mood to write about you. Asking then is why most review programs quietly fail, even when the work was excellent.
The right moment is different in every practice. Part of good review work is finding yours and naming it clearly. What matters is that the moment is tied to the work, not to a guess about how any one client feels.
The request fires on its own
Once you know the moment, the next step is making sure the ask actually happens on that day. In a well-built system, a real trigger in your CRM starts the request. That trigger might be a matter, visit, or engagement being marked complete.
Memory is not a system. An ask that depends on someone remembering disappears on busy weeks. When it is tied to an event the firm already records, it happens every time.
The sequence itself is short. One text and one email with your review link, then one reminder, then it stops. Asking twice is effective. Asking five times damages the relationship you just earned.
Texting has its own rules. The client must have agreed to receive texts, every message needs a way to opt out, and business texting requires A2P 10DLC registration. Budget two to three weeks for that registration before the texts can go out.
Every client, every time
This is what separates a careful program from a risky one. The same request goes to every client. The system does not first ask how the experience went and then send only the satisfied clients to the public review site. It does not pick out the clients you expect to be happy.
Asking only the clients you expect to be happy is called review gating. Google prohibits it, and the FTC review rule targets it. A program that screens clients by mood before the public ask is gating, however it is labeled.
The FTC also bans paying or rewarding reviews, so nothing of value is ever offered in exchange.
Unhappy clients still matter a great deal. The next lesson shows how a negative review reaches a named person who can respond and fix the problem. Every client keeps the same chance to leave a public review.
A concierge medical example
Picture a concierge medical practice with loyal patients, well-liked doctors, and a thin, old set of reviews. Nobody has a routine for asking.
In a system built for this practice, the ask is built into the visit. When a visit is marked complete, every patient who agreed to texts gets the same short message with the review link, plus an email, and one reminder later. No one is screened out. When a review arrives, staff are alerted and a person writes a reply that never confirms the reviewer is a patient.
The practice did not get better at medicine. It got better at asking everyone, the right way.
What to ask a provider
When you talk to anyone about building this for your firm, a few questions tell you a lot:
- What event in our CRM starts the request, and why that moment?
- Does every client get the same request, with no screening by how they feel?
- How many times will a client be asked, and when does it stop?
- Is our texting registered, and does every message include an opt-out?
If a provider suggests asking about satisfaction first and sending only happy clients to Google, treat it as a warning sign. That is review gating.
The takeaway
A rating moves through timing and consistency, not tricks. Ask at the right moment, let a real event in your CRM start the request, stop after one reminder, and send the same request to every client, every time. Run that way, the program survives a busy month, stays inside Google's rules, and helps your firm get found, trusted, and cited by name.
Go deeper:
The rest of this academy is free
See every lesson in AI Automation: Systems That Answer, Book, and Follow Up