When an activity ends in TripWorks with your guests checked in, Reviewflowz asks the guest who booked for a review of the location they went to. The review that comes back is matched to that activity and credited to the guide named on the booking, when it names one.
How it works
An activity ends in TripWorks with a guest in a booking status you picked, Checked In to start.
Within the hour, Reviewflowz reads it from your manifest.
The request goes out after your delay, counted from the end of the activity.
The guest's review is matched to the activity and the location, and credited to the guide when the booking names one.
What triggers a request
Trigger | When it fires | Who is asked |
Activity ended with a guest who is Checked In | The activity's departure time plus the experience's duration has passed | The guest who booked |
The trigger is on from the moment you connect and feeds one request, TripWorks review requests. It starts with Checked In. If your team doesn't check guests in, tick Not Checked In too.
Trips sold by a reseller, such as Viator or GetYourGuide, aren't asked. When the business or the guest is in the EU, the UK or Switzerland, a guest is asked only when Marketing Opt-In is ticked on their TripWorks profile.
Activities that ended in the 90 days before you connected are imported, so reviews from that time are matched to their trip and guide. Nobody is messaged for those.
Connect TripWorks
You need your TripWorks address and a REST API key you create for Reviewflowz.
Plan and cost. The REST API is included with every TripWorks account, at no extra cost.
Who. Someone in your TripWorks Owner group creates the key.
How long. Right away: the key works as soon as you create it.
In TripWorks, go to Setup, then Integrations, and open the REST API card. Switch it on if it's off. On the Keys tab, select Create key and name it Reviewflowz. Set Bookings, Customers, Experiences, Locations and Manifest to Read, select Create key, then Copy. TripWorks shows the key once. Create a new key rather than using Rotate key on one you already use: rotating stops the old key wherever it is. TripWorks' own guides are Set up the TripWorks REST API and API keys and access.
In Reviewflowz, open Integrations, go to the Automate Review Requests tab and click the TripWorks card. If you already have an integration connected there, click Connect another integration first. Fill in the TripWorks address, the one you sign in at, such as canyontrail.tripworks.com, paste the REST API key and click Connect TripWorks. Your TripWorks locations fill the Locations list, and a draft request is ready for you to finish.
Link your locations
Under Locations, give each Location in TripWorks the Reviewflowz location whose review profiles its guests should see. Canyon Trail Adventures links Sedona and Flagstaff to their own locations. If your Reviewflowz account has one location, your TripWorks locations are linked to it when you connect. An activity at an unlinked location uses the Fall back to location.
Set up the request
Timing. An activity counts from the moment it ends, and your delay comes on top. Canyon Trail emails 3 hours later, then sends a reminder 3 days after that as Message 2, with the subject "One more thing about your trip, {{first_name}}". Follow-ups stop once a guest clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, set per message.
Message. Canyon Trail's From name is "Canyon Trail Adventures", the Subject "How was the trail, {{first_name}}?", which Lena Hoffmann reads as "How was the trail, Lena?", and the Button text "Review your trip".
Direct reviews to. Smart routing gives one button, and your goal for reviews decides which site it opens. Show all options on the email lists every site instead.
Turn it on
Open TripWorks review requests and click Turn requests on. The Syncing panel's Asking guests whose activity ended after shows when you connected.
When an activity is cancelled or a No Show
If an activity is cancelled, or its guests are marked No Show, before its request goes out, the request is withdrawn.
See what it brings back
Every review is matched to the guest and the activity it came from, and credited to the guide when the booking names one. Ingrid Okafor's five star Google review of the Sunset Vortex Hike lands on Marco Reyes. Reports > Dashboard > Team Attribution Leaderboard ranks the guides named on your bookings by the reviews they earn.
The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped. The CRM Integration widget under Reports > Dashboard tracks requests, links clicked and reviews matched from TripWorks.
Good to know
Give Reviewflowz its own key. If it's rotated or deleted, or the REST API card is switched off, the card turns red. Create a new key under Setup, then Integrations, REST API, Keys, and enter it with Enter new credentials. Your statuses and request stay as they are.
If the card says your key is missing a permission, select the Reviewflowz key in TripWorks, set Bookings, Customers, Experiences, Locations and Manifest to Read, and select Save changes. We check again every day and pick it up on our own.
The Syncing panel counts guests who can't be asked, such as a guest with no email or phone. They're still kept, so a review from that guest is matched by name.
Disconnect stops the checks and withdraws every request that hasn't gone out.
