MILabs
Integrations

Review request automation with Rezdy for tour operators

Review request automation for Rezdy tour bookings, asking guests for a review once a tour is marked complete.

Updated 2025-12-10

Review request automation with Rezdy

Rezdy holds the record of each tour or activity booking. That makes it a useful trigger for asking guests to leave a review once their experience has finished. The difficulty for an operator is timing. A review request sent before the tour ends reads oddly, and one sent long after is easily forgotten. A workflow can watch for bookings marked as completed and queue the message for the hours that suit the guest. MILabs would build the link between the two, keeping the wording in the operator's own voice and leaving the choice of review sites with the team. Guests who cancelled or asked not to be contacted would be left out. Because the trigger depends on how completed tours are marked, the first conversation covers the status the team uses to show a tour has finished.

How it works

  1. Confirm with the team which booking status marks a tour as finished, and which products should trigger a request.

  2. Connect the booking data from Rezdy to the workflow using the API access the account holds, limited to the fields the message needs.

  3. When a completed booking is found, check the guest's contact preferences and skip anyone who has opted out or cancelled.

  4. Prepare the message from a template that uses the guest's name, the tour and the date, held for the send schedule the business has chosen.

  5. Send the request by email or SMS, with a link to the chosen review sites, and write each send to a log the team can read.

  6. Review the log with the team regularly and adjust the wording or timing as needed.

good questions, straight answers

Frequently asked questions

Can I start with a part of a review request automation on Rezdy?
Yes. Many operators begin with the trigger and the message alone, sending requests from a short list of completed tours while the link to the review sites and the opt-out check are added later. The first stage is smaller and easier for staff to check. The scope depends on which booking data the Rezdy account can share with the workflow, so that question is settled before any build starts.
How does MILabs test a review request automation against Rezdy?
MILabs would test the workflow with a set of sample bookings in a non-live setting, checking that completed tours are picked up, opted-out guests are skipped and the message quotes the correct tour name and date. Staff would review the drafted messages before the live send is switched on. Any step that depends on a Rezdy field is confirmed against the account's actual data, so gaps in permissions are found early.
What does MILabs do after delivering a review request automation for Rezdy?
After handover, MILabs can review the message log with the team, check that requests are reaching guests and that the opt-out check is working, and adjust the wording or the trigger where needed. Changes to Rezdy permissions or account settings are raised with the business owner before anything is altered. Any support arrangement beyond the handover is agreed in writing with the client.
Does a review request automation work with Rezdy?
It can work with Rezdy, provided the account can reach the booking data the workflow needs. Rezdy offers an API for integrators, and the endpoints and account types available should be confirmed on the official site before planning. Zapier, Make and n8n are workflow tools that can be used to connect the two systems, and the choice depends on the team's existing tools and how much control they want over the flow.
Which data does a review request automation write to Rezdy?
As designed here, the workflow reads completed bookings from Rezdy and does not change them. It does not take payments, alter rates, or cancel anything. Any note or tag written back to a booking would depend on the write permissions the account allows, and that is confirmed before the build. Where writing is not permitted, the request log is kept in a separate sheet.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.