> ## Documentation Index
> Fetch the complete documentation index at: https://help.1nspect.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Review requests

> Automatically ask clients for a review after you publish. Use the dedicated Review Request trigger with a 7-day offset; it fires on every publish, pay-first or not.

Review requests are the high-ROI touchpoint most firms underuse. 1nspecT has the plumbing: set your Google or Yelp link, write the email, and wire up the dedicated Review Request trigger with a delay. One or two emails later, you have a measurable lift in reviews.

## Add your review links

In the top bar, click **Business Ops** › the **Company Info** tab. Set:

* **Google Review Link** — the direct link to leave a Google review for your company
* **Yelp Review Link** — the direct link for Yelp (if you use it)

Save Changes. These links are available as dynamic tags (`$GoogleReviewLink` and `$YelpLink`) in your email templates.

## Build the review-request template

Open **Business Ops › Communications › Email Templates**. Add a template:

* A warm subject line (`Thanks for choosing [Company name]`)
* A short body thanking the client and asking for a review
* Use **Insert Variable** to drop the review link into the body
* There is no email preview, so confirm the link renders as a working link by running a test order through the workflow

Save Template.

## Wire up the workflow step

Open **Business Ops › Communications › Workflow**. Add a step with:

* **Trigger**: **Review Request**
* **Template**: your review-request template
* **Recipients**: Primary Client (and Secondary Client if you want)
* **Send Offset**: `+7d` (seven days after the Review Request trigger fires)
* **Enabled**: on

Save the step.

> [!WARNING]
>
> Do not use the **Report Delivered** trigger for review requests. `report.delivered` fires only when a Stripe payment lands after publish, or when you tap the manual Deliver button. In the normal pay-first flow it never fires, so a review-request step bound to it would silently never send. Use the dedicated **Review Request** trigger: it fires on every publish, with your offset applied.

## When Review Request fires

The dedicated **Review Request** trigger fires on every publish (paid or unpaid, delivered or not). It respects the Send Offset you set on the step, so your 7-day delay gives the client time to read the report before you ask.

## Test it

Run one test order end to end (booking → agreement → payment → publish). Wait for your offset to elapse (or temporarily set the offset to 0 for the test). Confirm the review-request email arrives, the review link opens the right platform, and the greeting fills in from the dynamic tags.

## When clients click the link

The review link opens the review page on Google or Yelp directly. The client leaves the review on the platform where it lives. 1nspecT does not host or store the review.

## What not to do

* Do not use `report.delivered` as the trigger (see Warning above).
* Do not offer anything in exchange for a review (coupon, discount) — violates Google and Yelp TOS plus FTC guidelines.
* Do not review-gate ("if you had a great experience, click; otherwise email us") — also violates FTC guidelines.

## Related

* [Review-request best practices](https://help.1nspect.app/1nspect/features/review-requests-best-practices.md)
* [Communication templates](https://help.1nspect.app/1nspect/getting-started/communication-templates.md)
* [Communication workflows](https://help.1nspect.app/1nspect/getting-started/communication-workflows.md)
* [Company profile](https://help.1nspect.app/1nspect/getting-started/company-profile.md)
* [Variable tags reference](https://help.1nspect.app/1nspect/getting-started/variable-tags-reference.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.