

To let your customers send review requests from inside your product, connect a trigger in your platform (a job completed, a booking checked out, an order delivered) to a review request API that sends an SMS or email with a link to the right review page for that location. The parts you have to get right are the trigger, the channel, the timing and reminders, the review link for each location, opt-outs and tracking. And every customer should get the same ask, with no screening for happy ones first.
This guide is about the build: how the pieces fit, and the product choices behind each one. If you need the rules, our post on review solicitation compliance for platforms covers Google's policies, the FTC rule and the UK rules in detail. Nothing here is legal advice.
Whether you build or buy, the building blocks are the same: a trigger event, a contact record (name plus phone, email or both), branded SMS and email templates, a schedule with reminders, a review link for each location, an opt-out list checked before every send, and tracking from send to review. The sections below take them in order.
The best trigger is the event that marks the end of the experience the customer will review. In most vertical software it already exists as a status change:
Fire once per completed transaction, not once per status update, so a reopened job doesn't send twice. Skip cancelled, refunded and test transactions. Store the transaction ID with each request so it traces back to a real event. And let each business turn the trigger on or off per location.
For older software with no webhooks, a daily export of completed jobs works as a fallback.
SMS is short and hard to miss. Email has room for branding and a clear button. Let the business choose per location, with a simple default:
Keep both messages short: one line on who is asking and why, the customer's first name, and one link. Don't tell customers what to write, how many stars to give or which staff member to mention. Google's Maps user contributed content policy says merchants should not request that specific content be included in reviews.
For in-person businesses, a QR code at the counter or on a receipt covers customers you have no contact details for.
Ask while the experience is fresh: within hours for most services, a few days after delivery for shipped orders. Make the delay a per-location setting, because a car wash and a kitchen remodel are not the same.
Three more settings matter:
Add a frequency rule too, so repeat customers don't get a request after every visit.
A link that opens a search page, or the wrong location, loses people. Every location needs its own review link for each site it asks for reviews on.
For Google, the business can get that link from its own profile. Google's help page on how to create a Google link or QR code to request reviews (checked November 2026) says to go to the Business Profile and select Read reviews, then Get more reviews, where the owner can copy the review link or download a QR code. Google suggests putting the link on receipts and in thank-you emails. Google's tips to get more reviews also note that customers must be signed in to a Google Account to leave a review.
In practice, platforms store one review URL per location per site, and check it during onboarding. Ways to make that easier:
Some review sites don't want businesses to ask for reviews at all, so per-site settings matter. The compliance post covers which sites allow what.
Review gating means asking customers how they felt first, then sending only the happy ones to the public review site and steering unhappy ones somewhere private. It's a tempting feature to build, but it breaks Google's policy and the FTC warns it can mislead:
The safe design: send the same request to every eligible customer. If you offer a private feedback form, show it alongside the public review link, never instead of it, and never pick what a customer sees based on the rating they gave. No discounts or rewards for reviews either: Google's policy prohibits incentives.
Review requests are messages, so messaging law can apply. The compliance post covers the review rules; for the messages themselves, two US rules shape the build (check the rules in every country you serve):
The product work is a suppression list. Record each opt-out with the channel, time and business. Check it before every send, including reminders. Decide whether an opt-out from one location covers the whole business (usually it should). And record consent for texts when you collect the phone number.
Businesses want to know if requests work, and you need a record of what was sent. Track each request through these steps:
The last step is the hardest. Review sites don't say which customer left which review, so platforms usually match new reviews to a location and time window. Seeing new reviews at all needs review data from each site. Our guides on what a review API is and the Google reviews API explain how that side works.
Report by location, channel and template.
Plan for single-location businesses and brands with hundreds of locations:
Collecting reviews on your own platform too? See verified reviews for marketplaces.
Shout About Us is the review management API for marketplaces and platforms. The Review Solicitation API sends email, SMS and QR review requests from your platform. Here is what the docs and product page describe:
The same API covers the rest of the review loop: Review Data (Google, Yelp, Facebook and 80+ sites) to see the reviews that come in, plus Review Insights, Review Response and Review Removal, with Verified Reviews (first-party reviews) available to approved partners. Pricing is $0.50 to $3.00 per location per month plus usage. For a full breakdown, see how much a review management API costs.
The event that ends the experience: a job completed, an appointment checked out, an order delivered or a ticket closed. Fire once per transaction and skip cancelled or refunded ones.
Let each business choose. SMS suits customers who gave a mobile number and agreed to texts. Email suits everyone else and allows more branding. Stop reminders on both channels once the customer clicks.
The business can copy it from its Business Profile under Read reviews, then Get more reviews. Store one link per location per site, and block sends until it's set.
You can ask, but every customer must still get the public review link. Sending only happy customers to the review site is review gating, which Google's policy prohibits and the FTC says can be misleading.
See how the Review Solicitation API fits your platform. Book a demo or request an API key to start building.