When a move is completed in Supermove, Reviewflowz asks the client for a review and credits it to the movers on the job. You set it up with one automation in your own Supermove settings.
How it works
A project is completed in Supermove.
Your Supermove automation sends us the project, and the client becomes a contact in Reviewflowz.
The request goes out after your delay.
Their review is matched to the move and credited to each mover on it.
What triggers a request
Supermove trigger | When it fires | What comes across |
Project Completed | As soon as the project is completed | The client's name, email and phone, the project number, and the movers on the job |
Project Cancelled (optional) | As soon as the project is cancelled | Withdraws the request that move started, if it hasn't gone out |
Only completed moves are asked about, and cancelled moves never are. A client with no email and no phone is skipped. Moves in the EU or UK are kept on record and never asked about. We keep only what the request needs: never your crew notes, revenue or street addresses.
Connect Supermove
In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click the Supermove card. Your webhook URL is ready at once, under Finish setting up Supermove, with Click to copy.
In Supermove:
Open Settings, then Automations, and click + Create Automation. Pick the trigger Project, then Project Completed.
Add the action Invoke Webhook. Set the method to POST, paste your URL, keep the default Headers, then Save and switch the automation ON.
To withdraw requests for cancelled moves, add a second automation with the trigger Project Cancelled, posting to the same URL.
Check that it works. Open any project in Supermove, go to its Automations tab and click Run Automations. Then click Check status in Reviewflowz. What arrived shows the client and project it received, such as "Got a project for Rosa Castillo (project 1187)… Your automation works.", and whether an email and phone came with it. Nobody is messaged from this test. If the project isn't completed, the panel says so and tells you to check that the trigger is Project Completed.
Click Confirm. If you have several requests, pick the one completed moves should join. Moves completed from the day after you confirm are asked about.
Pick the request and the location
The Requests section shows the Request completed moves join and, if your account is set up by location, the Location for these moves, which decides the review page your clients see. Each one saves as soon as you pick it. Until a location is picked, completed moves are kept on record and nobody is asked.
Set up the request
Timing. Bluebird emails 120 minutes after the move is completed, then reminds 3 days later with "Settling in, {{first_name}}?". Delays go up to 7 days, with up to 3 messages, and follow-ups stop once a client clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, one per request.
Message. The From name is "Bluebird Moving Co.", the Subject "How did your move go, {{first_name}}?" and the Button text "Rate your move". Vera reads "How did your move go, Vera?". Try yours with Send myself a test.
Direct reviews to. Smart routing shows one button and picks the site per client for your objectives. Bluebird keeps a 4.9 average on Google and gets as many Yelp reviews as possible. Show all options on the email gives each site its own button, on email only.
Turn it on
Open your request, finish the message and click Turn requests on. A move gets a request once you've confirmed Supermove and turned requests on. Moves completed while requests are off aren't asked later. A move dated more than 7 days before it reaches us, such as an old project you run the automation on by hand, is kept on record and never asked about.
When a move is cancelled
With the Project Cancelled automation in place, a cancelled move withdraws the unsent request it started. If the same client has another completed move, their request stays. A move cancelled before its completion reaches us is never asked about. 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. Yusuf Quigley's Yelp review of Bluebird is credited to Luis Ortega and Mateo Silva, the movers on the job. Every mover named on the move gets credit; salespeople and coordinators don't. The Team Attribution Leaderboard ranks your movers.
Good to know
The Webhook URL section shows the deliveries received, when the last one arrived, and the first completion date that gets a request.
If Supermove shows an automation run as Failed, check that the URL in the automation matches the one in Reviewflowz.
Running several Supermove branches? Connect each one: click Connect another integration, then the Supermove card, and add the automation in that branch's own Supermove settings. Each branch gets its own URL, request and location.
Running a project's automation twice never asks the client twice.
Only the teammate who connected Supermove can change its settings.
Disconnect stops accepting moves and withdraws the requests waiting to go out for them. Your contacts and history stay, and your URL is kept. Moves completed while disconnected aren't received. Reconnect puts Supermove back in setup: run the automation once, click Check status, then Confirm.
Nothing is written back to Supermove.