Skip to main content

Clover integration: review requests after every paid order

Connect Clover and ask your customers for a review after they pay in store, with the credit going to the employee on the order.

A
Written by Axel Lavergne

When an order is paid at your Clover register, Reviewflowz asks that customer for a review, from the right store, and credits the review to the employee on the order. See the Clover integration.

How it works

  1. A customer pays for an order on Clover.

  2. Clover tells us right away, and the customer becomes a contact in Reviewflowz.

  3. The request goes out after your delay.

  4. Their review is matched to the order and credited to the employee on the order.

What triggers a request

Trigger

When it fires

Who is asked

An order is paid

As soon as Clover reports the payment, with a nightly re-read of the last two days

The customer on the order, by email or phone

An order counts when every payment on it is cash, a credit or debit card, a check or PIN debit. Orders paid with a gift card or any other tender, even in part, aren't asked, and neither are DoorDash, Uber Eats and Grubhub orders, since those customers ordered through the delivery app. Customers who said no to marketing in Clover are never asked. A customer who later says yes is asked from then on.

On connect we import your last 90 days of orders, so your employees get credit for reviews you already have. None of those customers is messaged.

Clover sync status in Reviewflowz

Connect Clover

In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click the Clover card. Clover's own page opens: sign in as the owner of the merchant account and approve Reviewflowz. Running Clover in Latin America? Click In Latin America? in the card's corner instead.

Each Clover merchant is one store. To add another, click + Add a store under Stores and approve that merchant the same way.

Clover card in the Reviewflowz integrations directory, with the Latin America link

Link each store to a location

Each store points at one Reviewflowz location, which decides the review page your customers see. With one location, it's linked for you. With several, the store shows Pick a location: choose one under Location. Two locations with the same name show their street, so Lantern Row Deli Riverside goes to "Lantern Row Deli · 48 River St". Orders from a store are kept while it waits, and its customers are asked from the moment you link it.

Harbor Street Bakery links Harbor Street Bakery Old Port and Harbor Street Bakery Munjoy Hill to their own locations.

Clover merchants linked to Reviewflowz locations

Clover store waiting for its location, with the location picker open

Set up the request

Click + Add a trigger, pick An order is paid and switch it on. That creates its request, "Clover — order paid".

  • Timing. Harbor Street Bakery emails 3 hours after the order, then follows up 2 days later. Delays go up to 7 days, with up to 3 messages, and follow-ups stop once a customer clicks, reviews or unsubscribes.

  • Channel. Email, SMS or WhatsApp, one per request.

  • Message. The From name is "Harbor Street Bakery", the Subject "How was your visit, {{first_name}}?" and the Button text "Review Harbor Street Bakery". Ella reads "How was your visit, Ella?". Try yours with Send myself a test.

  • Direct reviews to. Smart routing shows one button and picks the site per customer for your objectives. Harbor Street Bakery wants as many Google reviews as possible and a 4.8 on Yelp. Show all options on the email gives each site its own button, on email only.

Clover trigger for review requests

Email editor for the review request after a Clover order

Follow-up email editor for the Clover review request

Review routing options with Google and Yelp objectives

Review request email a Clover customer receives

Turn it on

Open the request from Sends to and click Turn requests on. Orders paid after you connect the store, link it and turn the request on get a request. An order that reaches us more than 7 days after it was paid is recorded, never asked about.

Requests page listing Clover customers after a paid order

Refunds

A refund in Clover withdraws the unsent request for that order. The customer's next paid order brings it back. A message already sent can't be pulled back.

See what it brings back

The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped. Dylan Abbott's Google review of Harbor Street Bakery is credited to Lily Chen, the employee on the order. Change the employee on an order in Clover and the credit follows. The Team Attribution Leaderboard ranks your team, and the CRM Integration widget tracks requests, links clicked and reviews matched.

Customer review credited to the employee from the Clover order

Leaderboard of reviews credited to each employee

Dashboard widget showing Clover review requests, clicks and matched reviews

Good to know

The Syncing card shows when we last checked, and how many orders of the last 30 days carried an email or phone. The Connection card shows your merchants connected and their status.

Clover connection status in Reviewflowz
  • If a store shows Authorization lost, Clover no longer accepts our access to it, usually because the app was uninstalled from the Clover dashboard. Click Authorize with Clover again: your triggers and location links are kept.

  • Remove takes one store off. Its orders and location link are kept, so you can reconnect it any time.

  • Disconnect stops reading orders from every store and keeps your contacts, requests and location links.

  • Only the teammate who connected Clover can change its settings.

  • Nothing is written back to Clover.

Clover store with authorization lost and the Authorize with Clover again button

Related

Did this answer your question?