When your team marks a reservation Finished or Seated in Zenchef, Reviewflowz asks the guest for a review. The review that comes back is matched to that reservation and credited to the waiter named on it.
How it works
Your team marks a reservation Finished or Seated in Zenchef.
Within the hour, Reviewflowz reads the reservation.
The request goes out after your delay, by email or text.
The guest's review is matched to the reservation and credited to the waiter.
What triggers a request
Trigger | When it fires | Who is asked |
A reservation is marked Finished | Your team marks the reservation Finished in Zenchef | The guest on the reservation |
A reservation is marked Seated | Your team marks the reservation Seated in Zenchef | The guest on the reservation |
Both are on from the moment you connect and feed one request, Zenchef review requests. A reservation marked Seated and then Finished asks the guest once.
When the restaurant or the guest is in the EU, the UK or Switzerland, a guest is asked by email only if they ticked the marketing box for email in Zenchef, and by text only if they ticked it for SMS. A guest who opted out of review requests on a channel is not asked on that channel, and a guest marked unsubscribed in Zenchef is not asked at all.
We also import your last 90 days of reservations, so reviews you already have are matched to their visit and waiter. Nobody is messaged for those.
Connect Zenchef
You need your restaurant ID and a Zenchef token from Zenchef.
Plan. Zenchef's API comes with the Grow plan. See Zenchef API.
Where to find them. In Zenchef, open Settings, then the Partners tab. Copy the restaurant ID and the Zenchef token at the top of the page. Once you're on the Grow plan, you can connect right away.
A token that lasts. The token on the Partners page belongs to a Zenchef user and stops working when that user changes their password. For a stable one, email [email protected] and paste this:
Hello, we use Zenchef for [your restaurant], restaurant ID [your ID], on the Grow plan. Please create an API user and a stable API token for this restaurant so we can connect Reviewflowz, which reads our reservations and guest profiles to send review requests.
In Reviewflowz, open Integrations, go to the Automate Review Requests tab and click the Zenchef card. If you already have an integration connected there, click Connect another integration first. In the Connect Zenchef window, paste the Restaurant ID and the Zenchef token, or the stable API token Zenchef sent you, then click Connect Zenchef. Your restaurant fills the Locations list, and a draft request is ready for you to finish.
Link your restaurant to a location
Under Locations, give the Restaurant in Zenchef the Reviewflowz location whose review profiles its guests should see. Maison Ardoise in Lyon is linked to its own location. If your Reviewflowz account has one location, the restaurant is linked to it for you when you connect. Anything unplaced uses the Fall back to location.
A group connects each restaurant with its own ID and token, and each gets its own request.
Set up the request
Timing. A visit counts from the moment your team marks the reservation Finished or Seated, or from 6 hours after the booked time if that is earlier, and your delay comes on top. Maison Ardoise emails 3 hours later, then sends a reminder 3 days after that as Message 2, with the subject "How was your evening at Maison Ardoise, {{first_name}}?". Follow-ups stop once a guest clicks, reviews or unsubscribes.
Channel. Email, SMS or WhatsApp, set per message.
Message. Maison Ardoise's From name is "Maison Ardoise", the Subject "Thank you for dinner, {{first_name}}", which Élodie Bernard reads as "Thank you for dinner, Élodie", and the Button text "Review your visit".
Direct reviews to. Smart routing gives one button, and your goal for reviews decides which site it opens. Show all options on the email lists every site instead.
Turn it on
Open Zenchef review requests and click Turn requests on. The Syncing panel's Sending requests for visits since shows the day you connected.
When a reservation is a No show or cancelled
If a reservation is marked No show or cancelled in Zenchef before its request goes out, the request is withdrawn.
See what it brings back
Every review is credited to the waiter on its reservation. Laurent Deschamps's five star Google review, "Camille took lovely care of us all evening", lands on Camille Roux. Reports > Dashboard > Team Attribution Leaderboard ranks your waiters by the reviews they earn.
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 Zenchef.
Good to know
If Zenchef stops accepting your token, the card turns red. Click Enter new credentials and paste both the restaurant ID and the new token. Your request and restaurant link stay as they are.
If the card says Zenchef isn't letting your token read reservations, check under Billing in Zenchef that you're on the Grow plan, or ask your Zenchef account manager. We check again every day and pick it up on our own.
The Syncing panel counts guests who can't be asked, such as a guest with no email or phone. They're still kept, so a review from that guest is matched by name.
Disconnect stops the checks and withdraws every request that hasn't gone out.
