The short answer
Not natively — Checkfront handles booking, payment, and confirmations, but it has no Google review request and no reputation tool in its integrations directory. ReviewNudger connects with a token-authentication application you create in your own Checkfront account, watches for bookings whose end time has passed, and sends the guest one neutral 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 memorable day every week and has 120 Google reviews after five seasons. The guests are thrilled — and then they are in the car, at dinner, on the plane home. The ask has to happen in the hours after the trip ends, automatically, or it does not happen. A sign at the checkout counter and a line in the confirmation email both depend on the guest remembering later, which they do not.
Checkfront knows the booking, the guest, and the exact end time of the activity. What it does not do is ask for reviews, and its integrations directory has no review or reputation vendor. Its webhooks fire when a booking is edited, not when time passes, so "the trip is over" has to be derived — which is what ReviewNudger does on your behalf.
How the booking-ended trigger works
You create a token-authentication application in Checkfront (Manage › Developer › New Application) and paste your Checkfront address, the API key, and the API secret into ReviewNudger. No partner listing, no OAuth screen; the same credentials work on an account migrated to Checkfront's newer booking-platform address.
ReviewNudger checks your bookings ending on each local day every few minutes, in your account's timezone. Once a confirmed booking's end time passes — the booking's own end date, or the latest item end for multi-item bookings — it reads the guest's email and phone from the booking, applies your sending rules, and after the delay you choose sends one neutral 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 backfilled; and each booking asks once, so a multi-day trip or a later edit never produces a second text.
Every confirmed guest gets the same ask. Asking only the groups that seemed happiest is review gating — against Google policy and the FTC consumer-review rule. The public Google link is always on the landing page, and a disappointed guest can send private feedback from the same place.
Hourly rentals and multi-day trips
The trigger is the end instant of the booking, so a two-hour kayak rental is asked that evening and a three-day guided trip is asked after the last day — both after the delay you set from the moment the booking ends. Repeat guests fall under your per-customer cooldown, so a season-pass regular is not asked every Saturday.
Frequently asked questions
Do I need a particular Checkfront plan or a partner listing?
No. Any Checkfront account can create a token-authentication application under Manage › Developer; the key and secret are all ReviewNudger needs.
Which bookings count, and when is the guest asked?
Confirmed bookings whose end time has passed. The request goes to the email or phone on the booking (the listing email is the fallback). Bookings with no reachable contact are recorded and skipped, and the connection panel shows how many.
Our account moved to the new bookingplatform.app address. Does it still work?
Yes. ReviewNudger follows Checkfront's redirect with your credentials attached, so a migrated account connects with the same key and secret.
What about a booking edited after the trip?
Edits never produce a second request — the review request is keyed on the booking. A booking cancelled or voided before its end time is never asked.