Book reservations by phone — without taking the host off the floor.
WFW connects to OpenTable's API. Your agents check real availability, create reservations, and send confirmations — all while service is happening.
Same phone number handles human guests and AI restaurant platforms. Guests get a warm voice conversation. OTAs get structured availability data in under 500ms.
Inbound Booking Call
A2A Mode — AI Restaurant Platform Calling
When a dining app or OTA platform dials to check availability, WFW detects the AI caller and returns a structured JSON payload — available slots, party size limits, time range — in under 500ms. Same number, adaptive response.
Capabilities
What this integration enables.
Three reservation capabilities powered by live OpenTable data.
Live Sync
Voice Reservation Booking
"I'd like a table for 4 on Friday at 7pm" — the agent queries OpenTable availability in real time, confirms the slot, and creates the reservation. Confirmation number read aloud and sent via SMS.
Live Sync
Day-Before Confirmation Calls
WFW initiates an outbound call to every reservation the day before via POST /v2/calls/initiate. Guests confirm, cancel, or modify. The OpenTable reservation record is updated automatically.
Live Sync
Waitlist Notification Calls
When a cancellation opens a slot on your waitlist, WFW calls the next guest immediately. The agent confirms availability in real time and books the table — no manual follow-up.
Data Flow
From phone call to OpenTable reservation.
Exactly what moves between WFW and OpenTable on every booking call.
Guest calls to book
Agent answers the restaurant's phone. Intent is recognized: reservation inquiry. Agent collects party size, preferred date, preferred time, and diner name — conversationally, not via a phone tree.
OpenTable availability queried in real time
WFW queries the OpenTable API with the requested date, time, and party size. If the exact slot is available, it confirms immediately. If not, the agent offers the nearest alternatives.
Reservation created in OpenTable
Guest confirms. WFW posts the reservation to OpenTable — guest name, party size, date, time, phone, and any special requests captured during the call. Confirmation number delivered at call end.
Confirmation call fired day before
POST /v2/calls/initiate triggers the day-before outbound call. Agent confirms the reservation details, offers modification or cancellation, and updates the OpenTable record based on guest response. No-show rate drops significantly.
Use Cases
Before and after.
Restaurant workflows transformed by WFW + OpenTable.
Before
Phone rings during dinner service. Host answers between seating guests — distracted, rushed. Caller gives up and books on OpenTable web, or calls a competitor.
After
WFW answers every call on the first ring. Books reservations without pulling the host away from the floor. OpenTable record created in real time.
Before
Host spends 30–45 minutes each afternoon calling tomorrow's reservations. Half go to voicemail. No-show rate sits at 12–15%.
After
WFW calls every reservation automatically. Confirmations, cancellations, and modifications all written back to OpenTable. No-shows drop to under 4%.
Before
Cancellation comes in. Staff manually call down the waitlist — first available person who answers gets the table. Others get called after the slot is already filled.
After
Cancellation fires a WFW webhook. Agent calls the first waitlist guest within 30 seconds. Table filled automatically. Zero staff involvement.
Technical Details
Integration specifications.
Connection method, auth, data fields, and A2A response specs.
| Connection method | OpenTable API — REST over HTTPS (Connect API) |
| Auth method | OpenTable OAuth 2.0 client credentials — restaurant account authorization |
| Data pulled from OpenTable | Availability slots by date/time/party size, existing reservation records, waitlist queue |
| Data written to OpenTable | New reservation records, reservation modifications, cancellations, confirmation status updates |
| Extractions returned by WFW | Party size, requested date, requested time, diner name — via GET /v2/calls/{id}/extractions |
| A2A mode | OTA platforms querying availability receive structured JSON slot data in <500ms on the same phone number |
API Endpoints
WFW endpoints this integration enables.
Trigger confirmation calls, retrieve booking data extracted from inbound calls, and monitor agent health — all via the WFW /v2/ API.
Full API Reference →Available Endpoints
/v2/calls/initiateTrigger day-before confirmation outreach or waitlist notification
/v2/calls/{id}/extractionsReturns party size, requested date, time, and diner name from the call
/v2/agents/{id}Agent health and OpenTable connection status
Setup
Connect OpenTable in three steps.
OAuth authorization via OpenTable developer portal — no manual API key management.
Authorize via OpenTable OAuth
In WFW admin under Integrations → OpenTable, click Authorize. Redirected to OpenTable — log in with your restaurant account and approve access. 60 seconds.
Configure confirmation call timing
Set when day-before confirmation calls fire — default is 3pm the day before. Configure the message tone (casual vs. formal) and enable SMS confirmation after booking.
Enable on your agent
Toggle OpenTable active on your restaurant agent. Inbound calls check live availability. Confirmation and waitlist calls are scheduled automatically from that point on.
Get Started
Connect OpenTable to your reservation agent.
Voice reservations that book directly into OpenTable. Day-before confirmations that cut no-shows. Waitlist calls that fill cancellations in 30 seconds.
Connect OpenTableQuestions? Talk to our team →