Integrations: connecting your AI phone agent to your booking software

What « integrated » really means: the 4 levels

Integration between a voice agent and booking software runs on a scale of four levels, from no connection at all to writing a confirmed reservation during the call. The level decides one thing: whether someone on your team has to retype the booking afterwards. Vendors rarely name their level, so ask.

1. 01No connectionThe agent talks, nothing lands anywhere. You listen to the recording and enter the booking yourself. Useful to stop the phone ringing out, and nothing more.
2. 02Notification onlyThe agent emails you a summary or drops a form entry. Someone retypes it into the software, often minutes or hours later. This is the level most often sold as “integration”.
3. 03Read-only availabilityThe agent can see open slots but cannot write. It announces a time, then your team confirms behind it. Fewer wrong promises, still double entry.
4. 04Real-time read and writeThe agent checks availability, then creates, modifies or cancels the booking in your software during the call, and confirms it out loud. Nothing to retype, nothing pending.

The gap between level 2 and level 4 is the whole point. At level 2 a call at 8pm on a Saturday sits in a mailbox until someone opens it, and two callers can be promised the same table. At level 4 the software allocates the table before the caller hangs up.

Cancellations follow the same line, and they are the half people forget. A cancellation written into the book at 7pm frees a table you can still sell; the same one sitting in a mailbox is an empty cover. Our guide on reducing restaurant no-shows picks up there.

Which booking systems can be connected to an AI voice agent?

Any booking software that exposes an API with availability and booking endpoints can be connected. In France that means Zenchef, TheFork Manager, SevenRooms, Guestonline and a few others, each on its own terms. The limit is almost never the voice agent: it is whether the vendor opens its API, and to whom.

Two details matter more than the logo wall. First, an API is a commercial decision: TheFork ties its rate limits to « your contract » in its B2B API documentation, and SevenRooms routes new integrations through a partnership form. Second, having an API does not mean the agent uses all of it. Reading availability is the easy half; writing a booking that respects your service rules is the real work.

TheFork deserves a case of its own, because it is a marketplace as well as a booking system: your book keeps filling while the phone rings. We cover the three possible setups, and what they do to your commission bill, in our guide to the AI phone agent for restaurants on TheFork.

How does the agent avoid double bookings?

By never working from a copy. A properly integrated agent queries your booking software during the call and writes into it, so the software stays the single source of truth and allocates the table. Double bookings appear when a second system keeps its own list of free slots and syncs later.

That is why a batch sync every fifteen minutes, an exported spreadsheet or a duplicated calendar are risky on a Friday night: two callers can be handed the same 8:30pm table because neither copy knew about the other. With a live read and write, the second caller is offered the next opening instead.

Ask what happens when the write fails, too. Networks and APIs go down. The honest behaviour is to tell the caller, hand over to a human or take a message; the dangerous one is confirming a table that exists nowhere. Same logic as for a busy service: the worst outcome is not a slow answer, it is a phantom booking that shows up at 8:30pm. If you are still weighing the cost of unanswered calls, our guide on what missed calls cost a restaurant puts numbers on it.

Do you need an API to integrate an AI phone agent?

You need an API for level 4, not to answer the phone. Without one, an agent can still take calls, answer questions and capture booking requests; it simply cannot write into your book. The API is what turns a captured request into a confirmed table.

Three realistic options when your software stays closed:

• Stay at level 2 with a clear routine: the agent captures the request, one named person enters it at fixed times. Workable at low volume, painful at 40 calls a day.
• Wait for the adapter: ask the provider for a date and what it depends on. « Soon » without a partner agreement means nothing.
• Change booking software: the heaviest option, and rarely worth it for this reason alone. Weigh it against everything else the tool does for you.

What matters is that the provider says it plainly. A vendor listing twenty logos without naming the level is telling you something about the next twenty months.

8 questions to ask before you sign

These eight questions separate a real integration from a logo on a landing page. Ask them during the demo and get the answers in writing; each one maps to a failure we see restaurants live through.

1. Does the agent write into my software, or only send a notification?
2. Can it modify and cancel, or only create a booking?
3. Is availability read live during the call, or synced in batches?
4. Does it respect my service rules: turn time, capacity, max party size, closures?
5. Where do allergies, special requests and the phone number end up?
6. What happens if the write fails: transfer, message, or a promised table?
7. Where is guest data hosted, and what is kept on the agent’s side?
8. Who sets up the connection, in how long, and how is access revoked if I leave?

Question 4 is the one most often skipped. An agent that books a table of ten at 9:15pm because it ignores your last-seating rule creates more work than the calls it saved. For the wider criteria, see our complete guide to the AI phone agent for restaurants, and for the budget side, our guide to AI voice agent pricing and ROI.

Connecting ImaginoVox to your booking software

ImaginoVox sits at level 4 with Zenchef today: it checks availability, then creates, modifies or cancels the booking in your Zenchef account in real time, writes allergies and special requests into it, and confirms out loud before the caller hangs up. It is an inbound agent, so it answers calls and warm-transfers the rare complex case to a human; it does not place outgoing calls, and guest confirmation SMS keeps coming from Zenchef, per your own setup.

The rest is deliberately plain. Zenchef is our native integration; a TheFork Manager adapter is planned, and other systems are looked at case by case. Zenchef users can also compare our agent with Zenchef's own call feature in our Zenchef Call AI vs ImaginoVox comparison, or check the Zenchef help centre for their side of the setup. Setup takes 2 to 3 business days after a first call within 48 hours.

See our pricing or get started.