ReviewsRelay Start free

Completed-visit integrations

Start Google review follow-up when the visit is actually complete.

Connect a supported booking or payment event so eligible customers enter the review-request queue without staff retyping them. ReviewsRelay verifies completion, suppresses duplicates and opt-outs, and keeps every handoff visible.

Local businesses that want Google review requests to follow a real completed appointment, service, class, or payment without replacing their booking or point-of-sale system.

Start freeSee it work

Signed direct connections

Choose the system that already knows the visit is complete

Each direct adapter accepts a deliberately narrow provider event. These are signed webhook connections, not one-click marketplace installs. Open a provider page to see the exact trigger, required access, ignored states, test plan, and official source.

  • Square directQueue a fair Google review request only after Square reports that the customer payment is complete.
  • Vagaro directTurn a completed Vagaro service into an eligible review-request handoff without retyping the customer.
  • Mindbody directUse Mindbody attendance and schedule data without asking for a review before the visit is actually over.

Check access, channels, and costs before signing up.

Square direct

Access: Square Developer Console access, a payment webhook, and a customer-read access token for customer matching and email opt-outs.

Channels: Direct email intake. For text follow-up, use a bridge or CSV with recorded SMS permission; a phone number alone is not consent.

Costs: ReviewsRelay guided setup is included. Square controls API availability and account access.

Verify: Test a completed payment with your own linked customer. Verify queue timing, duplicate suppression, cancellation/refund, and customer.updated with email_unsubscribed=true, including while intake is paused. Prepayments need a visit-completion bridge.

Vagaro direct

Access: Vagaro API and webhook access, verification token, client ID, client secret, and your account region.

Channels: Direct email intake from completed appointments. SMS uses a bridge or CSV with confirmed permission. Keep provider opt-outs synchronized with your do-not-contact list.

Costs: Vagaro may charge separately for API or webhook access. Confirm availability before subscribing.

Verify: Mark your own test appointment Service Completed. Confirm the email lookup, request queue, duplicate suppression, and cancellation handling.

Mindbody direct

Access: Approved Mindbody developer access, a linked business, an active webhook subscription, and its signature key.

Channels: Direct email intake from attended visits. Import existing email opt-outs before enabling intake, then subscribe to client.updated: sendPromotionalEmails=false suppresses queued follow-ups. SMS requires a bridge or CSV with permission.

Costs: Mindbody controls developer approval, account eligibility, and API pricing.

Verify: Use your own attended appointment or signed-in class. Verify the request waits until visit end; test cancellation, duplicates, and a client.updated email opt-out while intake is paused.

Zapier (easiest)

Access: Your app must expose a completed-visit or paid-order trigger. Add a Webhooks by Zapier POST action.

Channels: Email or E.164 mobile number. Map sms_consent only from explicit permission; map email_consent=false and do_not_contact=true for opt-outs.

Costs: A Zapier plan supporting Webhooks and your trigger may cost extra; it is not included in ReviewsRelay.

Verify: Send your own completed visit with a stable event_id. Repeat the event to verify suppression. A cancelled visit uses the same event_id and event_status=cancelled.

Make

Access: A completed-visit trigger in your app and an HTTP POST module. Send JSON, not form-encoded fields.

Channels: Email or E.164 mobile number with sms_consent=true. Preserve source opt-outs instead of mapping every contact to true.

Costs: Make operations and any source-system API subscription are separate from ReviewsRelay.

Verify: Run once with your own contact details. Confirm queue timing, run again to check deduplication, and send a cancellation with the same event_id.

Booksy

Access: Use a client and completed-visit export available for your Booksy account, or request it from Booksy support. Partner access must be confirmed individually.

Channels: CSV email or SMS with your permission confirmation. Import respects explicit opt-out and visit-status columns.

Costs: CSV import is included. There is no self-serve Booksy API connection here; a partner connector needs confirmed access and separate scoping.

Verify: Import a small export first. Check the preview, names, contacts, completed visits, opt-outs, and duplicate rows before adding anyone.

Fresha

Access: Export clients and completed visits as CSV. Fresha’s paid Data connector uses Snowflake; it is not a direct ReviewsRelay connector.

Channels: CSV email or SMS with permission confirmation. A separately configured bridge can send completed visits if your account has the necessary access.

Costs: CSV import is included. Fresha Data connector and any bridge are separate subscriptions; confirm the dataset before purchasing them.

Verify: Preview a small completed-visit export. Verify opt-outs and duplicate contacts. Do not treat the entire client list as recent completed visits.

Custom webhook

Access: A system that can POST JSON after a completed visit, with a stable event_id and a private ReviewsRelay URL.

Channels: Email or SMS with explicit sms_consent. Preserve do_not_contact and email_consent fields.

Costs: The webhook endpoint is included. Custom connector development and hosting are scoped separately.

Verify: Test valid, malformed, duplicate, opted-out, cancelled, and out-of-order events. Retry 429/5xx responses; fix 4xx payload errors before retrying.

Other connection paths

Your current system does not need to be replaced

  • Zapier: use a completed appointment, paid order, or finished-service trigger already available in Zapier
  • Make: use a completion trigger with field mapping or branching in a visual workflow
  • Secure webhook: post the documented event from a CRM, booking system, POS, or backend
  • CSV or manual entry: keep a dependable fallback when the source system exposes no approved completion event

Before a request can queue

Completion is only the first eligibility check

ReviewsRelay also checks customer contact data, stable event identity, opt-outs, and the 90-day contact window. Every customer gets the same fair Google review destination.

  • Duplicate provider events are suppressed
  • Missing usable contact data is ignored
  • Email opt-outs remain suppressed
  • Recently contacted customers wait at least 90 days
  • No positive-only filter, incentive, or review gating

Practical outcomes

  • Remove the after-visit retyping step
  • Trigger only from completion evidence
  • Respect duplicates, opt-outs, and contact windows
  • See connection and delivery status in one workspace

Workflow

  • Choose the provider or bridge that already knows a visit is complete
  • Create the private signed connection with the required provider access
  • Send a controlled test using contact details you own
  • Confirm verification, completion timing, customer data, and suppression before enabling live intake

Safety guardrails

  • No request before the provider reports completion or a safe scheduled end
  • No booking-system password shared with ReviewsRelay
  • No positive-only filtering, incentives, or review gating
  • No send when usable contact data is missing
  • No duplicate request for the same event or a recently contacted customer

Frequently asked questions

Which systems connect directly?

ReviewsRelay supports signed direct completed-visit connections for Square, Vagaro, and Mindbody. Zapier, Make, and a secure custom webhook support other systems that expose a reliable completion event.

What if my booking system is not listed?

Use Zapier, Make, a secure webhook, CSV import, or manual entry. Booksy and Fresha do not currently offer a public self-serve completed-visit webhook contract that ReviewsRelay can promise universally, so support first confirms an approved bridge or fallback.

Are the direct connections one-click installs?

No. Square, Vagaro, and Mindbody direct connections use signed provider webhooks. They require the provider account permissions needed to create subscriptions and credentials. ReviewsRelay includes a guided checklist, a connection test, and direct support; your booking-system password is never requested.

Does every completed visit receive a request?

No. The event must include an eligible customer and usable contact channel. Duplicates, opt-outs, recently contacted customers, missing contact data, and events outside the accepted completion rules are ignored or suppressed.

Which plans include automatic customer intake?

Automatic completed-visit intake is included with Growth and Pro. Starter focuses on Google review monitoring, replies, and weekly summaries.

Related review automation pages