GoHighLevel review requests not sending? Why it happens and how to fix it

When GoHighLevel review requests are not sending, the review feature itself is rarely broken. The request is just an SMS or email built from your Reputation settings, so it fails when one of the pieces underneath it fails: the Google Business Profile connection, the review link, the SMS or email toggle, the contact’s ability to receive messages, or your email sender. The status in the Requests list tells you which one.

This guide walks through those causes in the order I check them on client accounts, each with the exact fix, plus the one setup that “works” but puts your Google profile at risk. It is the same checklist I use when I set up review automation as part of GoHighLevel CRM setup. Menu paths are as of October 2026.

Why review requests matter enough to fix today

Asking works. In BrightLocal’s Local Consumer Review Survey 2026, 78% of consumers said they had been asked to leave a review in the past year, and 28% said they will “always” write one when asked — up from 16% in 2025. Recency matters too: 32% look for reviews written in the last two weeks, so a review flow that silently stopped a month ago is already costing you.

• Asked for a review in the past year78%
• Look for reviews from the last two weeks32%
• Always review when asked (2026)28%
• Always review when asked (2025)16%

Separate survey answers, not one funnel. The jump from 16% to 28% is the share who say they always leave a review when a business asks.

Source: BrightLocal, Local Consumer Review Survey 2026 (as of October 2026)

• 78%of consumers asked for a review in the past year(BrightLocal 2026)
• 28%always leave a review when asked(BrightLocal 2026)
• $53,088maximum FTC penalty per violation(FTC, Dec 2025)

Start with the request status

Go to Reputation > Requests. HighLevel added a search bar and status filters, including Failed, so you can search by the contact’s name, email or phone and see what happened.

Status or symptom	What it usually means	Fix
No request listed at all	The request was never created — toggle off, workflow not firing	Causes 2 and 5
Queued	Waiting behind other requests or for your send delay	Check the delay in Cause 2
Failed	Did not deliver, e.g. an invalid phone number	Cause 3
Email “sent” but never “delivered”	Mailgun does not provide a delivered status	Cause 4 if customers really miss it
Delivered, but the link opens the wrong page or nothing	Review link not set or wrong location	Cause 1
Clicked, but no review appears on Google	Google’s checks or spam filter	Cause 6

Cause 1: Google Business Profile is not connected properly

HighLevel says Google review links need the Google Business Profile integration set up and linked to the correct location. The connection must be made with a Google account that has Owner or Manager access to the location.

The quiet failure is permissions. Google’s sign-in screen now lets people tick only some permissions, and HighLevel warns that ungranted scopes break features such as Google Business Profile. The integration then shows as connected but does not work.

The fix:

1. Go to Settings > Integrations > Google. If you see a permissions missing warning, open it to see which features are affected.
2. Click Reconnect and sign in with the Google account that is an Owner or Manager of the profile — not a staff login that was added later without access.
3. On Google’s consent screen, tick every permission HighLevel asks for.
4. Choose the correct business location if the account manages more than one.
5. Go to Reputation > Settings > Review Link. In Get Reviews on Google, use the Select Page dropdown to pick the right location. If the dropdown is empty, the connection from steps 1–4 has not worked yet.
6. If you use review-link blocks in emails and no platforms show, connect them under Reputation > Settings > Integrations and reopen the email builder.

As a check, compare the link with the one Google gives you: in your Business Profile, open Read reviews > Get more reviews to copy Google’s own review link or QR code. Both should open the same review box.

Cause 2: the request toggle, delay or template is off

Review requests are switched on per channel. Under Reputation > Settings there are separate SMS Requests and Email Requests tabs, and HighLevel notes that template editing is disabled while the SMS toggle is off.

The fix:

1. Go to Reputation > Settings > SMS Requests and switch on the toggle at the top right. Repeat on Email Requests if you want email too.
2. Check When to send SMS after check-in? The options are Immediately, 1 Hour, 2 Hours, 4 Hours or Custom. A request that seems missing may just be waiting for this delay.
3. Set Until clicked, repeat this every and the number of retries — HighLevel allows between 1 and 5 retries, in hours or days. I use two retries, three days apart. Repeats stop once the customer clicks.
4. Make sure every template contains the {{reputation.review_link}} token, which pulls in the link you set under Review Link. A template without it sends a message with nowhere to go.
5. Keep the message short and identify the business:

Hi {{contact.first_name}}, thanks for visiting Riverbend Dental today. Would you mind sharing how it went? It takes a minute: {{reputation.review_link}}

Cause 3: the contact cannot be messaged

A review request is a normal outbound message, so everything that blocks a text or email blocks it too. HighLevel’s error dictionary says messages are blocked when a contact has opted out or has Do Not Disturb (DND) enabled on their profile, and a Failed status is often just an invalid phone number.

The sender matters as well. A request sent manually comes from the signed-in user, while the workflow action sends on behalf of the contact’s assigned user. If that person has no phone number or email set up, the request has nothing to send from.

The fix:

1. Open the contact and check DND at the top of the profile — all channels and the SMS and email channels separately. Do not switch DND off for someone who replied STOP; that is a real opt-out.
2. Check the phone number is a valid mobile in full international format (+1… for US numbers).
3. Open Conversations for the contact and read the error on the failed message. If you see carrier errors such as 30007, my guide to GoHighLevel SMS error 30007 covers the fixes.
4. Make sure your number is on an approved A2P 10DLC campaign — unregistered texting to US numbers is filtered. See A2P 10DLC campaign rejected if yours was turned down.
5. Make sure the assigned user (for workflows) or you (for manual sends) has a phone number and email to send from.

HighLevel adds sender identification and opt-out wording to the first text in a conversation, review requests included, so do not strip it out of your template thinking it is a duplicate.

Cause 4: review request emails are not sending

HighLevel’s own article on review request emails not sending points to the sender setup: check which SMTP or email service is connected, and if it uses a specific user’s address, that user’s account is the one the email goes out from. It also says to check the email for broken custom values, and that Mailgun can add a delay.

The fix:

1. Go to Settings > Email Services and note which service and sending domain the sub-account uses.
2. Send a test request to yourself. If nothing arrives, check the user the request is sent from has a working email address (Cause 3, step 5).
3. Open the email template under Reputation > Settings > Email Requests and check every custom value resolves — an empty {{custom_values.…}} is easy to miss.
4. If emails arrive but land in spam, the issue is authentication, not reviews. Set up SPF, DKIM and DMARC on your sending domain — my guide to GoHighLevel emails going to spam has the exact records.
5. Remember that with Mailgun the status may stop at “sent”, because Mailgun does not provide a delivered status. Judge it by whether your test arrived.

Cause 5: the workflow never fires the request

Most accounts send requests from a workflow, not by hand — typically when an appointment is marked showed or an opportunity moves to Won. HighLevel’s Send Review Request action uses the templates and link from Reputation Settings, so Causes 1–4 still apply. If no request appears in the Requests list at all, the workflow is the problem.

The fix:

1. Open the workflow and confirm it is Published, not Draft.
2. Check the trigger filters match how your team works — if staff never mark appointments as Showed, a “Showed” trigger never fires.
3. Open the Execution Logs for a contact who should have received a request and see where they stopped.
4. Add a Wait of an hour or two before the action if you want the request to arrive after the customer leaves, rather than also setting a delay in Reputation Settings, so you are not stacking two delays.
5. For WhatsApp, use the separate WhatsApp review action, which needs a pre-approved template and a connected WhatsApp number.

If the workflow is not triggering at all, work through my GoHighLevel workflow not triggering checklist.

Cause 6: reviews are left but never show up

Sometimes the request worked and the customer reviewed you, but nothing appears. Google says reviews are checked for policy compliance, which can take a few days, and its automated spam detection occasionally removes legitimate reviews. If the review is not on Google, HighLevel has nothing to sync.

The fix:

1. Search for your business on Google Maps while signed out and check whether the review is visible there.
2. If it is visible on Google but not in HighLevel, reconnect Google as in Cause 1 — expired or partial permissions stop the sync.
3. If it is missing on Google, wait a few days, then contact Google Business Profile support about a legitimate review that was removed.
4. Do not ask several customers to review from your shop’s Wi-Fi or a tablet at the counter. Google’s policy says merchants should not pressure people to leave reviews while on the premises, and a burst of reviews from one place looks unnatural.

The setup that sends but puts your profile at risk

The most common “fix” I undo is review gating: asking customers to rate you first and only sending the Google link to the 4- and 5-star ones. Google’s policy says businesses must not discourage negative reviews or selectively solicit positive reviews, and must not offer discounts or freebies in exchange for reviews.

US law has teeth here too. The FTC’s Consumer Reviews and Testimonials Rule has been in force since 21 October 2024 and bans review suppression, including misrepresenting that the reviews you display are most or all of the ones you received. The FTC put the maximum at up to $53,088 per violation when it warned ten companies in December 2025.

Risks your profile

• ✕Avoid: Google link only for 5-star ratings
• ✕Avoid: Discount in exchange for a review
• ✕Avoid: Reviews collected on a shop tablet
• ✕Avoid: Removing DND to resend
• ✕Avoid: Hiding negative reviews on your site

Builds real reviews

• ✓Do: Same request to every customer
• ✓Do: A simple thank-you, no incentive
• ✓Do: Link sent after they leave
• ✓Do: Opt-outs respected
• ✓Do: Reply to every negative review

Getting reviews flowing reliably

A dependable review flow in GoHighLevel needs four things in place: Google connected with full permissions to the right location, both request toggles on with the link token in every template, contacts you are allowed to message from a registered number and an authenticated domain, and a workflow that fires the request at the right moment for every customer.

If you would rather hand it over, I build review automation as part of GoHighLevel CRM setup and fix the SMS and email sending underneath it through email and SMS deliverability. Local search competition varies a lot by market — the locations pages show how I work with businesses in states such as Texas and Florida.