Teach Review Requests
Teaching review requests is the onboarding segment where you show the client how to ask customers for Google reviews directly from inside the GHL conversations interface. This is one of the simplest actions in the entire system and one of the highest-impact daily habits a small business owner can build. A client who sends two or three review requests per day will transform their online reputation within months.
Why This Matters
Most small business owners know reviews matter. They see their competitors with 200 Google reviews and feel the gap. But knowing reviews matter and actually requesting them consistently are two very different things. The friction of the old process — remembering to ask, finding the Google review link, copying it into a text message, sending it manually — means most business owners ask for reviews sporadically at best.
GHL removes that friction entirely. From inside a conversation with a customer, the client can send a review request with a few clicks. The message is pre-written, the link is embedded, and the whole interaction takes less than 30 seconds. But the client will never do this if they do not know the workflow exists.
Review velocity is one of the strongest local SEO signals. A business that goes from two reviews per month to ten reviews per month will see measurable improvement in Google Maps rankings. That improvement translates directly to more calls, more leads, and more revenue. When the client connects the dots between “I clicked a button” and “I got three new reviews this week,” their confidence in the system skyrockets.
How to Think About It
This is not a technical training segment. The actual mechanics of sending a review request take about 60 seconds to learn. The real training here is behavioral. You are building a daily habit. The client needs to leave this segment thinking: “After every positive interaction with a customer, I send a review request. Every time.”
Frame it around timing. The best moment to request a review is immediately after a positive customer interaction, while the experience is fresh. Finished a job and the customer is happy? Send the request before you drive to the next appointment. Completed a service call and the client thanked you? Send it right then from your phone. The mobile app makes this frictionless, which is why Mobile App Training matters so much.
Show the client their current review count and their top competitor’s review count during the training. Make it tangible. “You have 34 reviews. Your top competitor has 187. If you send three requests per day, five days a week, you will close that gap in under a year.” Numbers motivate action.
Common Mistakes
Only showing the desktop workflow. Most review requests will be sent from the mobile app, on the go, right after a customer interaction. If you only demonstrate the desktop version, the client will forget how to do it by the time they are standing in front of a happy customer with their phone in their hand. Train the mobile workflow first.
Not walking through the customer experience. Show the client what the customer sees when they receive the review request. Open the link on your own phone so they can see the landing page and the Google review prompt. When the client understands the full experience from the customer’s perspective, they are more confident sending requests.
Failing to connect this to reputation results. Sending review requests is an action. Getting reviews is a result. Show the client where their reviews appear in GHL, how they can track review count over time, and how new reviews impact their Google Business Profile. This connection between action and result is what builds the habit. Reference Reputation Setup for the full configuration context.
Making it sound optional. Some agencies position review requests as a “nice to have” or an “advanced feature.” It is neither. It is one of the most valuable daily actions in the entire system. Treat it with that level of importance during training.
Tools Involved
Review requests are sent from within GHL Conversations, using either a manual message with the review link or a pre-built template configured during Reputation Setup. The client can send requests from both the desktop interface and the mobile app. If you have configured automated review request workflows that trigger after certain events (appointment completed, invoice paid), explain how those work alongside the manual process.
Where This Fits
Sequence position 24, during the Live Onboarding Call. This segment flows naturally after the Conversations Deep Dive since the client has just learned to navigate the inbox and send messages. Teaching review requests while they are already comfortable in conversations reinforces both skills simultaneously. The Reputation Setup element should already be complete before this training happens.
Common Questions
What if the client does not have a Google Business Profile? If there is no Google Business Profile, you cannot send Google review requests. Address this gap during the onboarding call and help the client understand the importance of getting their profile set up. In the meantime, you can configure review requests for other platforms like Facebook.
How many review requests should a client send per day? There is no magic number, but two to three per day is a sustainable target for most small businesses. The key is consistency, not volume. Three requests per day, five days a week, adds up to over 700 requests per year. Even a 20% conversion rate means 140 new reviews annually.
What if the client is worried about getting negative reviews? This is a common concern. Explain that the review request process typically only goes to customers who had a positive experience. If a customer is unhappy, the client simply does not send the request. Some agencies also configure a review funnel that routes unhappy customers to a feedback form instead of a public review site, giving the business a chance to resolve the issue privately first.