The short answer
Not on its own. Checkfront handles booking, payment, and confirmations. It has no Google review request and no review tool in its integrations directory. ReviewNudger connects with a token-authentication application you create in your own Checkfront account. It watches for bookings whose end time has passed. Then it sends the guest one text or email with a one-tap link to your Google review form. Every confirmed booking, once.
Why tour and activity operators are under-reviewed
A kayak outfitter, zipline park, or walking-tour company gives hundreds of people a great day every week. Yet it has 120 Google reviews after five seasons. The guests are thrilled, and then they’re in the car, at dinner, on the plane home. The ask has to happen in the hours after the trip ends, automatically, or it doesn’t happen. A sign at the checkout counter and a line in the confirmation email both rely on the guest remembering later. They don’t.
Checkfront knows the booking, the guest, and the exact end time of the activity. What it doesn’t do is ask for reviews. Its integrations directory has no review vendor. Its webhooks fire when a booking is edited, not when time passes. So "the trip is over" has to be worked out separately. ReviewNudger does that for you.
How the booking-ended trigger works
Create a token-authentication application in Checkfront (Manage › Developer › New Application). Paste your Checkfront address, the API key, and the API secret into ReviewNudger. No partner listing, no OAuth screen. The same keys work on an account moved to Checkfront's newer booking-platform address.
Every few minutes, ReviewNudger checks your bookings ending that local day, in your account's timezone. A confirmed booking ends at its own end date, or at the latest item’s end for bookings with several items. Once that passes, ReviewNudger reads the guest's email and phone from the booking. Your sending rules apply. After the delay you choose, it sends one review request by text or email with a one-tap link to your Google review form. Pending, pre-booking holds, waitlisted, cancelled, voided, and no-show bookings are never asked. Bookings that ended before you connected are never asked. Each booking asks once. A multi-day trip or a later edit never brings a second text.
Every confirmed guest gets the same ask. Asking only the groups that seemed happiest is review gating. That goes against Google policy and the FTC consumer-review rule. The public Google link is always on the landing page. A disappointed guest can send private feedback from the same place.
Hourly rentals and multi-day trips
The trigger is the moment the booking ends. So a two-hour kayak rental is asked that evening. A three-day guided trip is asked after the last day. Both wait the delay you set from the moment the booking ends. Repeat guests fall under your wait before asking again. A season-pass regular isn’t asked every Saturday.
