When an appointment is completed in FieldRoutes, Reviewflowz asks the customer for a review and credits it to the technicians who serviced it. Your Team Attribution Leaderboard then shows which technicians earn your reviews.
How it works
A technician completes the appointment in FieldRoutes.
Within about 2 hours, the customer becomes a contact in Reviewflowz, with the appointment and its technicians.
The request goes out after your delay.
Their review is matched to the appointment and credited to each technician on it.
What triggers a request
FieldRoutes event | When it fires | What comes across |
An appointment is completed (always on) | Within about 2 hours: we check FieldRoutes every 2 hours. On the FieldRoutes Premium API tier, right away. | The customer's name, email and phone, the appointment, and its technicians |
We follow each customer's reminder settings in FieldRoutes as they stand when we pick up their completed appointment. Customers with email reminders turned off are never emailed, and customers with text reminders turned off, or who replied STOP to your texts, are never texted or messaged on WhatsApp. Turn their reminders back on and their next completed appointment asks for a review.
On connect we import your last 90 days of completed appointments, so your technicians get credit for reviews you already have. None of those customers is messaged.
Connect FieldRoutes
From FieldRoutes, get a read-only API key and token for your office: email [email protected] or call 404-800-7378 ext. 2. Any FieldRoutes plan works. FieldRoutes gives every office its own key.
In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click the FieldRoutes card. Fill in your Subdomain (yourcompany in yourcompany.fieldroutes.com), the Authentication key and the Authentication token, then click Connect FieldRoutes. Your key and token are stored encrypted and never shown again. Connecting creates your review request, switched off.
Running more than one office? Connect each one with its own key. A key that reads several offices is refused, so each office's appointments come in through one connection only. Syncing shows the exact time from which completed appointments get a request.
Pick the location for your appointments
Appointments belong to sets the Reviewflowz location this office points at, which decides the review page your customers see. With one location, it's picked for you. Saguaro Pest & Lawn points its office at its Saguaro Pest & Lawn location.
Get requests out faster on FieldRoutes Premium
On the Premium tier of the FieldRoutes API, FieldRoutes tells us about each completed appointment right away. In FieldRoutes, add a Trigger Rule for Appointment Status set to Completed, add a Webhook action, then paste the Webhook URL and Body from the panel. Last webhook received shows it working.
Set up the request
Timing. Saguaro emails 3 hours after the appointment, then reminds 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 "Saguaro Pest & Lawn", the Subject "How did today's service go, {{first_name}}?" and the Button text "Review your service". Mason reads "How did today's service go, Mason?". Try yours with Send myself a test.
Direct reviews to. Smart routing shows one button and picks the site per customer for your objectives. Saguaro wants as many Google reviews as possible and a 4.7 on Yelp. Show all options on the email gives each site its own button, on email only.
Turn it on
Open the request, check it and click Turn requests on. Appointments completed after you connect, while requests are on, get a request. One that reaches us more than 7 days after it was completed is recorded, never asked about.
When an appointment is cancelled
If an appointment is cancelled, marked as a no-show or rescheduled after we've read it, its unsent request is withdrawn. The customer's next completed appointment 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. Tiffany Villalobos's Google review of Saguaro Pest & Lawn is credited to Mei Lin, the technician on the appointment. Several technicians on one appointment are each credited. Change the technicians in FieldRoutes and the credit follows when we next read the appointment. The Team Attribution Leaderboard ranks them, and the CRM Integration widget tracks requests, links clicked and reviews matched.
Good to know
The Connection section shows the FieldRoutes office and subdomain your key reads, and its status.
FieldRoutes reads left today shows your office's API reads. The free FieldRoutes API allows 50 a day; when they're used up, we check again after midnight Pacific time.
If a check fails, a banner asks you to confirm with FieldRoutes support that your key is still active, then paste the key and token again.
Only the teammate who connected FieldRoutes can change its settings.
Disconnect stops the checks and keeps your contacts, appointments and requests. Reconnect any time.
Nothing is written back to FieldRoutes, and appointment notes, office notes and custom fields are never read.