Every completed TheFork reservation asks for a review
Everything you need for reviews, with nothing you don't.
- Live in minutes, no demo
- Every completed reservation asks for a review
- Each review credited to the server
TheFork is connected to Reviewflowz. Trigger in TheFork: completed. A review request is then sent by SMS to the diner, and the Google review that comes in is saved on the reservation, credited to the server, Marco Bellini.
Reservation #4821 
Each completed TheFork reservation sends a review request
When a reservation completes in TheFork, Reviewflowz sends the diner a post-visit review request by email, SMS or WhatsApp. You set the channels and timing once, and every visit after that runs on the same campaign.
Dinner service, private events and special occasions all get the same follow-up. Your team never builds a list or sends a message by hand.
When a reservation is completed in TheFork, a review request campaign runs by itself: an SMS one hour later, an email three days later, a WhatsApp message seven days later, until a new 5-star Google review comes in.
Every diner on a completed reservation gets asked
The diner gets one message on their phone with one review link. That link opens the platform your restaurant needs reviews on most, such as Google, TripAdvisor, Yelp or OpenTable.
Every diner gets the same request. Nobody is screened by rating first.
When a reservation is completed in TheFork, the diner gets an SMS asking how it went, with a link to review it. They tap the link, give five stars and post on Google, and the review lands tied to the reservation and the restaurant: Osteria Lume, Bistro Calder, The Copper Table.
Connect TheFork and start asking today
Every completed reservation sends the diner a review request from the moment you connect.
Each review credited to the server on the reservation
When a diner leaves a review, Reviewflowz saves it against the reservation and credits it to the server who handled the table. Guests never need to mention a name for the review to count.
Past reservations are imported for reporting, so you see each server's conversion rate from the start. Past diners are never messaged.
The reservation in TheFork records which server did the work. The review request carries the reservation, so when the diner leaves a five-star Google review with no name in it, it is credited to the server and saved back on the same reservation.
TheFork integration: questions
When does a diner get the review request?
Reviewflowz sends the request once the reservation completes in TheFork, by email, SMS or WhatsApp on the timing you choose. You connect TheFork from Integrations in Reviewflowz in minutes, with no demo.
Who gets asked for a review?
Every diner on a completed TheFork reservation gets the same request. Nobody is screened by rating first, and the link opens the platform your restaurant needs reviews on most.
What happens with reservations that never complete?
A request only goes out when a reservation completes in TheFork. A reservation that never reaches that point sends nothing, so those diners are not asked.
I run several restaurants. Does each one get its own reviews?
Yes. Each restaurant's requests point to that restaurant's own Google profile, so reviews land where diners searched for it. Pricing is per location.
Can I see which servers get the most reviews?
Yes. Each review is credited to the server on the TheFork reservation, so guests never need to mention a name. Past reservations are imported to show each server's conversion rate, and past diners are never messaged.
What does the TheFork integration cost?
Reviewflowz costs $70 per location per month billed annually, or $80 month to month. Messages cost $5 per 1,000 emails and $5 per 100 SMS. You can start with a 14-day trial, no card needed.