November 17, 2026
9-minute read

Review Request API: SMS and Email Review Invites From Your Platform

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.

The parts of a review request flow

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.

Pick the right trigger

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:

  • Field service: job marked completed, or invoice paid.
  • Booking and practice management: appointment checked out or visit closed.
  • POS and ecommerce: order delivered or picked up, not order placed.
  • Marketplaces: booking or job marked complete by both sides.
  • Support tools: ticket closed.

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.

Choose the channel: SMS, email or both

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:

  • Send by SMS when you have a mobile number and the customer agreed to texts.
  • Send by email when you only have an email address, or when the business prefers it.
  • Send both only if the business wants it, and stop reminders on both channels once the customer clicks.

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.

Timing, pacing and reminders

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:

  • Send window: only send during daytime hours in the customer's time zone.
  • Daily cap: cap how many requests a location sends per day. A new location importing its whole customer list at once creates a sudden spike in reviews, and Google's policy lists "unusual volumes or patterns of review contributions" as a sign of rating manipulation. A steady flow is safer.
  • Reminders: one or two follow-ups for customers who didn't click, spaced a few days apart. Stop as soon as the customer clicks, opts out or leaves a review.

Add a frequency rule too, so repeat customers don't get a request after every visit.

Send each customer to the right review page

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:

  • Ask the business to paste the Google review link during setup, and test it with a click before the first send.
  • Block sends for a location that has no link yet, and show the business why.
  • If a location asks for reviews on more than one site, choose which site each request points to (for example, Google for most customers and an industry site for some), rather than listing five links in one message.
  • Re-check links when a location moves, rebrands or merges profiles.

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.

Don't gate reviews

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:

  • Google's Maps user contributed content policy says merchants may not "discourage or prohibit negative reviews, or selectively solicit positive reviews from customers".
  • The FTC's Endorsement Guides FAQ (for the Guides as revised in 2023) says that only asking for reviews from customers you think are likely to be happy would be misleading if it substantially skews how favorable the reviews are.

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.

Handle opt-outs and consent

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):

  • Texts: under the FCC's TCPA rules (47 CFR 64.1200, checked November 2026), a reply of "stop," "quit," "end," "revoke," "opt out," "cancel" or "unsubscribe" to a covered text revokes consent, and revocation requests must be honored within a reasonable time, no later than ten business days after they are received.
  • Email: the CAN-SPAM Act (15 U.S.C. 7704) requires commercial email to include a working way to opt out, and bars sending more than 10 business days after an opt-out request.

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.

Track sends, opens, clicks and reviews

Businesses want to know if requests work, and you need a record of what was sent. Track each request through these steps:

  1. Queued and sent: with the trigger event, channel and template.
  2. Delivered or failed: bounces and bad numbers, so you can fix contact data.
  3. Opened: for email.
  4. Clicked: the customer reached the review page.
  5. Reviewed: a new review appeared for that location.

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.

Multi-location and white-label considerations

Plan for single-location businesses and brands with hundreds of locations:

  • Settings at two levels: brand defaults (templates, tone, channels) with location overrides (review link, send window, time zone, sender name).
  • Roles: a location manager edits their location; a brand admin sees every location's results.
  • Your branding, or theirs: messages should come from the business or your platform, not a vendor the customer never heard of. That means a verified email sender domain and branded landing pages.
  • Per-location limits: caps and allowances per location, so one busy location can't use up another's.

Collecting reviews on your own platform too? See verified reviews for marketplaces.

For platforms: send review requests with the Review Solicitation API

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:

  • Event-triggered sends: call the send endpoint when a job is completed, a ticket is closed or a purchase is made. Each call takes a campaign, the customer's name and an email, a phone number or both. The message is queued and sent within minutes. The send endpoint uses an account token.
  • File-based automation: send requests automatically from a file your system already produces, such as a daily export of completed jobs. You map the columns once.
  • Channels: email, SMS, QR codes and in-store kiosks or tablets.
  • Templates: email and SMS templates with your branding and dynamic fields such as the customer's first name. Emails can send from your own verified domain.
  • Scheduling and follow-ups: campaigns set a daily send cap, a frequency, a delay before the first request and a send time, plus up to three follow-up emails.
  • Review links per location: each request links to the review site URL set for that location. If a template links to a site the location has no URL for, the send fails with a clear error that names the site.
  • Analytics: delivery, opens, clicks and QR scans across email and SMS for every location.
  • Allowances: each plan includes email and text requests per location. Past the allowance, requests are stopped or billed at an overage rate, depending on the plan.

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.

FAQ

What events should trigger a review request?

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.

Should we send review requests by SMS or email?

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.

How do we get the right Google review link for each location?

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.

Can we ask customers how they felt before sending the review link?

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.

Add review requests to your product

See how the Review Solicitation API fits your platform. Book a demo or request an API key to start building.

Cobi Emery

Cobi Emery is Chief Revenue Officer at Shout About Us, the review management API for marketplaces and platforms. Cobi works with product and engineering teams at marketplaces, SaaS platforms and multi-location brands to add review data, AI review replies and review requests to their own products.

SHARE THIS ARTICLE:

Frequently asked questions

No items found.
All
Best Practices
Hotel reviews from Tripadvisor, Booking.com and Google flowing into hotel software through an API
November 12, 2026
8-minute read
Hotel Review API: Tripadvisor, Booking.com and Google Reviews

How hotel software can pull Tripadvisor, Booking.com, Expedia and Google reviews by API, what each site's docs say, and how to plan for many properties.

Cobi Emery
All
Best Practices
November 10, 2026
11-minute read
What Happens When You Report a Google Review? (Plus Yelp and Facebook)

What Google does after you report a review, how to appeal, how to report reviews on Yelp and Facebook, and how platforms handle removal at scale.

Cobi Emery
All
Best Practices
Google reviews flowing into a platform through an API
November 3, 2026
9-minute read
How to Add Google Reviews to Your Product with an API

Compare the Google Business Profile APIs, the Places API and third-party review APIs, with Google's rules and a plan for many locations.

Cobi Emery

Add review management to your platform in days

Book a call to explore the API, see white-label demos, and get custom pricing.