HOW IT WORKS
Connect TheFork and Zenchef in three steps.
01
Forward TheFork emails.
You switch on a forwarding rule in your mailbox. Every reservation email from TheFork Manager then goes to the integration automatically.
02
Read and check reservations.
The integration reads the name, date, time, party size and notes. If anything is missing, you get an alert in the portal. We never guess.
03
Sync automatically with Zenchef.
Through the Zenchef API, the reservation lands at the right restaurant. Changes and cancellations sync the same way. Around 95% of reservations go through fully automatically. The rest wait for you in the portal.
WHAT YOU SET UP
What do you set up in TheFork Manager and in Zenchef for the integration?
For the TheFork-Zenchef integration you set up three things: a forwarding rule for the TheFork emails, access to Zenchef and an agreement on availability. Then we set up the integration.
In your mailbox. All reservation emails from TheFork Manager arrive at one address. On that address you set a forwarding rule to the integration. If the emails arrive at more addresses, for example one per restaurant, you set the rule on each address.
In Zenchef. You give us access to Zenchef, so the integration can book through the Zenchef API. Per restaurant we record which service a reservation falls into and in which field notes and allergies go.
In TheFork Manager. You agree how many tables TheFork may sell per service. The integration puts TheFork reservations into Zenchef, but does not adjust availability in TheFork.
TESTING
How do you test the TheFork-Zenchef integration after go-live?
You test the integration by running each type of reservation through once on purpose and checking the result in Zenchef.
A new reservation for two people.
A change of time or number of guests.
A cancellation.
A reservation with an allergy or dietary request.
A reservation with a deposit, if you use one.
A reservation for each restaurant, if you have more than one in Zenchef.
For the first two weeks you go through the alerts in the portal every day. After that a weekly sample of ten reservations is enough.
THREE EXAMPLES
How the TheFork-Zenchef integration works in your situation.
Restaurant using TheFork and Zenchef
Before.
Every day, someone retypes the TheFork emails into Zenchef by hand. Changes and cancellations have to be tracked down separately.
After.
Every reservation is in Zenchef automatically. Your team only checks the alerts in the portal.
Hotel restaurant with several restaurants in Zenchef
Before.
The reservations team works for several restaurants and files each reservation under the right one by hand.
After.
The integration files every reservation under the right restaurant in Zenchef. We set up who has access per restaurant. Your hotel software works together, without replacing anything.
TheFork reservations with a deposit
Before.
The guest receives two or three separate emails before the deposit is settled.
After.
With the deposit add-on, the guest receives one email in your style, with the payment link from Zenchef. That cuts no-shows without extra work.
WHAT GOES WRONG
What often goes wrong with TheFork reservations in Zenchef?
Emails that don’t come through. A second mailbox or a new colleague with their own address means TheFork emails don’t reach the integration. Check with every change to your mailbox that the forwarding rule is still in place.
An incomplete reservation. If a time or number of guests is missing from the email, the integration does not book. The reservation then waits with an alert in the portal.
Notes in the wrong field. Without a fixed agreement, each team member puts notes somewhere else. The integration always puts them in the same field, so agree that the team uses that field too.
A different email format. If TheFork changes the layout of its emails, monitoring catches that before reservations are left waiting.
WHAT IT DELIVERS
Five things the integration changes.
01
No more retyping.
Around 95% of TheFork reservations land in Zenchef fully automatically.
02
Changes and cancellations happen on their own.
No more combing through emails.
03
Notes and allergies in one place.
Always in the same field in Zenchef, whoever is on shift.
04
Nothing falls through the cracks.
An incomplete reservation triggers an alert in the portal.
05
Your team keeps the contact with the guest.
The integration does the legwork, you have the conversation.
WHAT BEST BYTE DOES
Keep TheFork and Zenchef. We build the integration.
An Amsterdam boutique hotel with a Michelin-starred restaurant retyped its TheFork reservations into Zenchef by hand every day. We built this integration for that hotel. “The software does the legwork, the team takes care of the guest.”
When don’t you need the integration? If you only get a few TheFork reservations a week, an integration does not outweigh the retyping. If you are considering a switch of reservation system, choose first. Read what to look for in a reservation system for your restaurant.
How we work
01 Set up
02 Test with your own emails
03 Live
04 Expand
FAQ
Here you’ll find answers to the most frequently asked questions.
What happens if a TheFork reservation is incomplete?
You get an alert in the portal. The integration never guesses. You fill in the gap and resubmit the reservation.
Does the integration work with multiple restaurants in Zenchef?
Yes. Every reservation lands at the right restaurant. We set up per restaurant how reservations come in.
What do I need to do to get started?
Switch on a forwarding rule and give us access to Zenchef. We set up the integration, test it with your own TheFork emails and hand it over to your team.