When a guest's experience ends in Xola, Reviewflowz asks that guest for a review. The review that comes back is matched to the booking and credited to the guide on it, when the booking names one.
How it works
A confirmed booking's experience ends in Xola, its arrival time plus its duration.
At the next hourly read, Reviewflowz picks up the booking, the guest and the event's guides.
The request goes out after your delay.
The guest's review is matched to the booking and credited to the guide.
What triggers a request
Trigger | When it fires | Who is asked |
The experience ended | The experience is over and not every guest on the booking is marked No-Show | The guest on the booking |
A guest was checked in | The experience is over and at least one guest is marked Checked-In in Xola | The guest on the booking |
Ask when is set to The experience ended from the moment Xola is connected. If you check guests in and only want to ask the ones who came, pick A guest was checked in instead. Both feed one request, Xola review requests, so a guest is asked once. The guest is asked by the email and phone on the booking.
Bookings made on your website, at your checkout, in your office or in Xola itself are asked. Bookings from agents, partners and resellers, such as Viator or GetYourGuide, are kept for matching and never asked, and neither are guests when your business or the guest is in the EU, the UK or Switzerland.
Experiences that ended in the 90 days before you connected are imported so their reviews still match. Nobody is messaged for those.
Connect Xola
You connect with an API key an Administrator creates for Reviewflowz in Xola. No Xola approval is needed, and your other keys and logins keep working as they are.
In Xola, open Settings, then Users & Access, and click Add API Key. Name it Reviewflowz, select the Reservationist access level and click Save. Copy the new key. Xola's own guide is Xola Settings.
In Reviewflowz, open Integrations, go to the Automate Review Requests tab and click the Xola card. If you already have an integration connected there, click Connect another integration first. Paste the key into API key and click Connect Xola. The Connection card names your Xola business with Status: Connected.
Link your experiences to locations
Under Experiences, give each Experience in Xola, shown with its Meeting point, the Reviewflowz location where it runs, so its guests are sent to that location's review page. Redwood Ridge Adventures links Big Sur Coastal Zip to its Big Sur location, and Canopy Zip Tour and Sunset Zip & Sip to Santa Cruz. An experience you leave unlinked uses the location in Fall back to. If your Reviewflowz account has one location, every experience is linked to it for you. Added an experience in Xola? Click Refresh list and link it.
Set up the request
Timing. A booking counts from the moment its experience ends, and your delay comes on top. Redwood Ridge Adventures emails 3 hours later, then sends a reminder 3 days after that with the subject "One more thing about your zipline, {{first_name}}" and the button "Leave a review". Follow-ups stop once a guest clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, set per message.
Message. Redwood Ridge Adventures' From name is "Redwood Ridge Adventures", the Subject "How was the zipline, {{first_name}}?", which Paolo Ricci reads as "How was the zipline, Paolo?", and the Button text "Review your zipline". Try yours with Send myself a test.
Direct reviews to. Smart routing gives one button, and your goal for reviews decides which site it opens. Redwood Ridge Adventures aims for as many Google and Tripadvisor reviews as possible. Show all options on the email lists every site instead.
Turn it on
Open Xola review requests and click Turn requests on. The status line reads "Sending requests to every new contact", and the Syncing panel's Asking guests whose experience ended after shows the day you connected.
When a booking is cancelled or marked No-Show
If a booking is cancelled, or every guest on it is 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 booking it came from, and credited to the guides on that event. Ingrid Ferreira's five star review of the Sunset Zip & Sip lands on Kenji Arai. Reports > Dashboard > Team Attribution Leaderboard counts the reviews credited to each guide, Kenji Arai, Marisol Vega and Tanner Brooks at Redwood Ridge Adventures. The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped, and the CRM Integration widget under Reports > Dashboard tracks requests, links clicked and reviews matched from Xola.
Good to know
Keep the Reviewflowz key in Xola. If the card shows Reconnect needed, create a new key under Settings, then Users & Access (Add API Key, Reservationist) and enter it with Enter new credentials. Your triggers and experience links stay as they are.
Reviewflowz reads Xola every hour and looks back over the last three days each time, so a check-in, a No-Show or a cancellation made after the experience is seen.
The Syncing panel counts bookings nobody could be asked, such as a booking with no email or phone. They're still kept, so a review from that guest is matched by name.
Disconnect stops the reads and withdraws every request that hasn't gone out.
