OpenTable

During the rush nobody can pick up. The receptionist reads available tables in OpenTable and writes the request into Zenvox; no booking is announced without confirmation from the floor plan.

7 days, 20 answered calls, no card

Where your table request lands

The request is written into Zenvox: date, party size, time, special requests, and whether a booking was already made online — because a call that duplicates an existing reservation costs an empty table that same evening. OpenTable keeps the floor plan and real table inventory, and your host enters the reservation: the receptionist texts the official booking link or hands the request to a person.

Access runs through OpenTable's partner programme and your restaurant's authorisation. With it, the receptionist reads real table inventory before answering about a time; the reservation itself is written by your host. An allergy stated on the phone is handed to a person, not treated as a booking note.

OpenTable holds the floor plan, real table inventory and guest history: it is what knows whether a party of six fits at seven, and not the book sitting on the host stand.

Read, create, update, cancel

What the receptionist does with OpenTable, action by action, and what your host does.

ActionWhat that means
ReadShe queries real table inventory: that is the decisive step, the one that lets her answer about a time instead of promising blind.
CreateThe receptionist takes the complete request and texts out your official booking link; your host enters the reservation in OpenTable and confirms it, with its own reservation reference.
UpdateThe receptionist finds the existing reservation in OpenTable, captures the change with name, time and party size, and hands it to the host, who enters it.
CancelThe receptionist takes the cancellation, time-stamps it and passes it on right away: that is a table freeing up mid-service. The host enters it in OpenTable, where arrivals are reconciled against no-shows.

What is included, what needs an add-on

Answering during service, qualifying a table request, turning away a sales call and passing everything on belong to your restaurant base. Waitlists and party handling are a named add-on, included in the free trial.

Add-ons that work with your software

Waitlist and groups

A last-minute cancellation and a party looking for a seat the same evening: the waitlist is what connects the two without tying up the host during service.

The authorisation, and what holds the truth

Two rules guide the receptionist: the restaurant confirms the table, and an allergy goes to the kitchen.

  • Access rests on OpenTable's partner programme and restaurant authorisation; Zenvox asks for no password
  • No written reservation is announced to a caller until the restaurant has confirmed it
  • Special requests and allergies are passed to a person as spoken: the kitchen decides, and no food safety guarantee is given on the phone
  • A party beyond capacity or a deposit exception belongs to the host
  • A phone request is checked against a booking already made online, to avoid a duplicate

Friday, quarter past seven, full room. The host is working the floor plan. The call is taken by Zenvox, which reads available tables in OpenTable.

CallerHi, I would like a table for six tomorrow evening, around eight.

ReceptionistLet me take your name and a callback number. Have you already booked online for that date? I would rather check first, so we do not create a duplicate.

ReceptionistThere is a severe allergy in the party: I am recording it word for word and passing it to the kitchen. A table for six is free at eight: the host confirms the reservation with its reference number.

The restaurant receives a complete request — date, time, party size, allergy flagged, duplicate ruled out — while the host keeps seating guests. Confirmation goes out from the restaurant, with the reference that counts.

When the connection is not there

The receptionist works in your Zenvox app: the official booking link, or a request handed to a person.

  • The request is created inside Zenvox with date, time, party size and special requests
  • Your official booking link is texted to the caller
  • Allergies and sensitive requests go to a person, with no interpretation
  • You find the call, its transcript and its reason in the app
  • With the connection in place, the receptionist also reads available tables, and your setup does not change

Questions about this connection

Does Zenvox book a table?

The reservation is written by your host: the receptionist reads available tables, takes the complete request and texts out your official booking link, then the restaurant confirms with its own reservation reference; no written reservation is announced to a caller before that confirmation.

Why not promise a time?

Because real table inventory is what decides: the receptionist reads it in OpenTable before answering. The floor plan knows whether a party of six fits at seven; the book sitting on the host stand does not.

How is an allergy handled?

It is passed to a person as spoken, not treated as a booking note. The kitchen decides, and no food safety guarantee is given on the phone.

What if the person already booked online?

The phone request is checked against a booking already made online, to avoid a duplicate. A call that duplicates an existing reservation costs an empty table that same evening.

What happens to a cancellation taken mid-service?

It is taken, time-stamped and passed on at once, because that is a table freeing up mid-service. The host enters it, and the waitlist is what connects the cancellation to the party looking for a seat the same evening.

Where to next

See the practice concerned, or the full list of software.

OpenTable

During the rush nobody can pick up. The receptionist reads available tables in OpenTable and writes the request into Zenvox; no booking is announced without confirmation from the floor plan.

Start your free trial7 days, 20 answered calls, no card