AI phone agent and TheFork: answering every call when your book lives in TheFork Manager

Why TheFork is not a booking system like the others

TheFork wears two hats: a public marketplace where diners find you, and TheFork Manager, the software your team runs the room with. Your book therefore fills itself, at any hour, with no action from anyone on the floor. Every phone setup you consider has to survive that.

The consequence is concrete. With a closed booking system, the book only moves when your team moves it, so a voice agent working from a fifteen-minute-old copy is usually a nuisance rather than a hazard. With TheFork, a table can be taken from the marketplace three seconds after that copy was made, while your caller is still describing their allergy. Real-time reading is not a refinement here, it is the price of entry.

This is also why the generic advice about connecting a voice agent, covered in our guide to integrating an AI voice agent with your booking software, tightens on TheFork: the same mistake costs more.

What TheFork Manager already does for your calls

One thing, and it does it well: caller identification. When a known guest calls, TheFork Manager surfaces their booking history, preferences and allergies before you have said hello. TheFork puts the gain at around thirty seconds per call, and the feature is rolled out in France, Italy, Spain, the Netherlands and Switzerland.

Note the assumption buried in it: someone is standing in front of the screen, free to answer. That holds at 3pm. It stops holding at 8:15pm on a Saturday, which is precisely when the calls pile up. Caller ID makes an answered call faster; it does nothing for a call nobody answers.

So the two features solve opposite halves of the problem. TheFork improves the calls you take. A voice agent takes the ones you do not. If you have never put a figure on that second half, our guide on what missed calls cost a restaurant gives you the method.

How do you connect an AI voice agent to TheFork Manager?

Three setups exist, and providers rarely tell you which one they are selling. They differ on a single question: who types the booking into TheFork Manager once the call ends. Your team, the agent through the API, or nobody, because the agent kept it elsewhere.

Setup B is not something a voice agent can grant itself. TheFork frames access commercially: its B2B API documentation states that rate limiting is enforced « at the default level as outlined in your contract ». Read that sentence twice before believing a logo wall. A provider claiming to write into TheFork either has that contract or is describing setup A in flattering terms.

One nuance in favour of setup A: it is honest and it ships tomorrow. While call volume stays modest, re-entry holds up fine. Past a certain point, which your own call log will pinpoint far better than any market average, it turns back into the job you were trying to remove.

Phone or marketplace: what each booking actually costs you

A booking taken on the phone is a direct booking, and TheFork lists direct channels as included. Bookings sourced from its marketplace are charged as a percentage of your average bill per guest. The phone is therefore your cheapest channel, and every call left ringing pushes a guest towards the expensive one.

Two honest caveats. First, TheFork publishes neither the percentage nor the plan prices: its pricing page shows the structure and a « ask for pricing » button, so run this calculation on your own contract rather than on figures found in a blog post. Second, a guest who cannot reach you does not automatically rebook through the marketplace: some go to the restaurant next door, and no arithmetic recovers them.

The reasonable way to size this: take last month's call log, count the unanswered calls during service, and apply your own contractual rate to the share you believe would have booked. Our guide to AI voice agent pricing and ROI walks through the same exercise on the subscription side.

5 questions before you believe « integrated with TheFork »

These five are specific to TheFork, on top of the general checks in our integration guide. Ask them during the demo, and get the answers in writing: each one separates setup B from setup A wearing a nicer jacket.

1. Do you hold a partner contract with TheFork, or do you go through my own account?
2. Is availability read live during the call, or from a copy refreshed on a schedule?
3. Do you listen to TheFork webhooks, so you see the bookings that arrive from the marketplace while a call is in progress?
4. What happens when the write fails: transfer to a human, message taken, or a table promised anyway?
5. Do you write allergies and special requests into the TheFork guest record, or only the name and the party size?

Question 3 is the one nobody expects, and it is the TheFork-specific one. An agent that reads availability but ignores incoming marketplace bookings is right at the start of the call and wrong ninety seconds later. For the broader criteria, see the 8 questions in our integration guide and, if you are still choosing an agent, our complete guide to the AI phone agent for restaurants.

Where ImaginoVox stands on TheFork

Plainly: our native integration is Zenchef, where the agent checks availability and creates, modifies or cancels the booking in real time during the call. A TheFork Manager adapter is planned and not shipped. On TheFork today, that puts us at setup A: the agent answers, handles the conversation and captures the request, and your team enters it.

We would rather write that here than let you discover it after signing. It is also worth knowing what the agent does not do, whatever the booking system: it is inbound only, so it answers calls and warm-transfers the complex ones to a human, it never calls guests back, and confirmation texts keep coming from your booking software, not from us.

If you also run Zenchef, or are weighing the two, our Zenchef Call AI vs ImaginoVox comparison covers what a real-time write changes day to day.

See our pricing or get started.