When a booking is marked Left in TheFork, or it's still Reserved once its mealtime is over, Reviewflowz asks the diner for a review. A review that comes back is matched to its booking and restaurant, so you see which of your restaurants earns it.
How it works
A booking is marked Left in TheFork, or it's still Reserved once its mealtime is over.
Within two hours, Reviewflowz reads the booking, its diner and the restaurant.
The request goes out after your delay.
The diner's review is matched to the booking and the restaurant.
What triggers a request
Trigger | When it fires | Who is asked |
A booking is marked Left | Your team marks the booking Left in TheFork Manager | The diner on the booking |
A booking is still Reserved after its mealtime | The meal time plus the meal's duration has passed | The diner on the booking |
Both are on from the moment you connect and feed one request, TheFork review requests. Keep both if your team doesn't always mark tables Left: a booking that isn't marked Left still counts once its mealtime is over. Untick either one in the trigger's list.
When your restaurant or the diner is in the EU, EEA, UK or Switzerland, the diner is emailed when they ticked your restaurant group's newsletter box while booking on TheFork. Everywhere else, every diner with an email or phone is asked.
We also import your last 90 days of meals, so reviews you already have are matched to their booking. Nobody is messaged for those.
Connect TheFork
You need three things from TheFork: a Client ID, a Client Secret and your restaurant group ID. Every TheFork restaurant belongs to a group, a single restaurant included.
Ask TheFork for your keys. TheFork's team sends them. Email [email protected] with your company name, or ask your TheFork account manager, and paste this:
Please send us B2B API credentials (client ID and client secret) for our restaurant group, with read access to reservations and customers, and tell us our restaurant group ID (groupUuid).
TheFork describes the process in its preliminary steps and authentication guides. Custom API Integration is part of both TheFork Manager plans, Performance and Enterprise. There's nothing to set up in TheFork Manager.
In Reviewflowz, open Integrations, go to Automate review requests > Connect another integration and click the TheFork card. Fill in:
Client ID and Client Secret, as TheFork sent them.
Restaurant group ID: 36 characters in five groups separated by dashes, like 3fa85f64-5717-4562-b3fc-2c963f66afa6.
Click Connect TheFork. We set up a draft request for you to finish, and your restaurants appear within minutes as your recent bookings come in.
Link your restaurants to locations
Under Locations, give each Restaurant in TheFork the Reviewflowz location whose review page its diners should see. The Olivette group links Olivette Bastille in Paris and Olivette Croix-Rousse in Lyon to their own locations. Bookings from a restaurant you haven't linked use the Fall back to location. With one location, every booking lands there and there's nothing to link. A restaurant missing from the list? Click Refresh list.
Set up the request
Timing. A meal counts from the moment it's marked Left, or from the end of its mealtime, and your delay comes on top. Olivette emails 3 hours after the meal, then sends a reminder 3 days later with the subject "How was your evening at Olivette, {{first_name}}?". Up to 3 messages, and follow-ups stop once a diner clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, one per request. For diners in Europe, choose email: the newsletter opt-in covers it.
Message. Olivette's From name is "Olivette", the Subject "Thanks for dining with us, {{first_name}}", which Camille Laurent reads as "Thanks for dining with us, Camille", and the Button text "Review your meal". Try yours with Send myself a test.
Direct reviews to. Smart routing gives one button and picks the site per diner. Olivette aims for as many Google and Tripadvisor reviews as possible. Show all options on the email lists every site instead.
Turn it on
Open TheFork review requests and click Turn requests on. The Syncing panel's Sending requests for meals finished since shows when you connected.
When a booking is cancelled or a No-show
If a booking is cancelled, refused or marked No-show in TheFork before its request goes out, the request is withdrawn. Your team can change a booking's status in TheFork Manager for 72 hours after the meal, and we keep reading it, so a late No-show is caught too.
See what it brings back
The Requests page counts Contacts, Requests, Clicked CTA, Matched and Stopped. The CRM Integration widget under Reports > Dashboard tracks requests, links clicked and reviews matched from TheFork.
Good to know
The Syncing panel counts diners who can't be asked, such as a diner with no email. They're still kept, so a review from that diner is matched by name.
If TheFork stops accepting your keys, the card turns red and asks for the Client ID and Client Secret TheFork sent you. Your request and restaurant links stay as they are.
If the card says TheFork isn't letting your keys read reservations or customers, ask TheFork's team to give your Client ID that access. We check again every day and pick it up on our own.
A second TheFork restaurant group on the same account gets its own request.
Disconnect stops the checks and withdraws every request that hasn't gone out. Contacts, bookings and keys stay, and you can reconnect any time.
