Toast runs the POS. WFW answers the phone.
WFW connects to the Toast Platform API. Menu inquiries are answered from live Toast data. Order status updates go out automatically. After-hours calls capture catering and event inquiries — not voicemail.
Delivery platform AI callers checking order status get structured JSON. Human customers get conversation. One WFW integration handles both.
Live Data Flow — Menu Inquiry + A2A Order Check
A2A dual-mode — customers + delivery platforms
Human customers get voice. Delivery platform AI gets structured JSON. Toast data powers both.
Capabilities
What this integration enables.
Three concrete capabilities unlocked by connecting WFW to Toast.
Live Data
Menu Inquiry Calls — Hours, Specials, Allergens
When customers call asking about hours, daily specials, dietary accommodations, or menu items, the agent queries Toast for current menu data. Specials that change daily are always accurate — the agent reads from Toast, not a static knowledge base.
Live Data
Order Status Update Calls
WFW queries Toast for order status and initiates outbound calls when orders are ready for pickup or when delivery estimates change significantly. Customers stay informed without calling back — reducing inbound call volume during peak service.
Live Data
After-Hours Message Capture and A2A Delivery Responses
After closing, the agent captures customer messages — reservations, catering inquiries, event requests — and logs them for morning staff review. Delivery platform AI callers checking order status receive structured JSON, not an unanswered phone.
Data Flow
How it works.
From caller identification to menu answer or order status — what moves between WFW and Toast.
Caller type identified — customer or A2A
WFW determines whether the inbound call is from a human customer or an A2A caller (delivery platform, aggregator AI). Human customers get voice conversation. A2A callers checking order status get structured JSON with the current Toast order state.
Menu and location data queried from Toast
For menu inquiries, WFW queries the Toast menu API for current items, prices, allergen flags, and daily specials. Location-specific data — hours, address, parking — is pulled from the Toast location configuration.
Order status checked against Toast POS
For order status inquiries, the agent looks up the order in Toast using the confirmation number or customer phone. Status — received, in kitchen, ready for pickup, dispatched — is spoken to the customer from the live Toast record.
Analytics and call data available via API
GET /v2/agents/{id}/calls provides call analytics across all Toast-connected locations — call volume, peak inquiry times, most-asked menu questions, and order status call frequency — for the restaurant manager's review.
Use Cases
Before and after.
Real restaurant phone workflows transformed by the Toast + WFW integration.
Before
Staff fielding "are you open?" and "what are your specials today?" calls during lunch rush. Informational calls pull staff away from in-restaurant guests at the worst possible time.
After
WFW answers every informational call instantly with current Toast data. Staff never interrupted for hours or menu questions. Peak-hour phone volume drops measurably.
Before
Customers calling in to ask if their takeout order is ready. Each call takes 2–3 minutes from a staff member who is actively working the line.
After
WFW calls customers proactively when their Toast order hits "ready" status. Inbound "is my order ready?" calls drop substantially. Staff focus on service, not status updates.
Before
Calls after closing go unanswered. Catering inquiries, large group reservations, and event requests are lost entirely or found in a voicemail queue the next morning.
After
WFW answers after-hours calls, captures the inquiry type, contact details, and request specifics, and logs them in a structured queue for morning staff. Every inquiry gets a response.
Technical Details
Integration specifications.
API connection, A2A mode, multi-location routing, and analytics endpoints for your tech team.
| Connection method | Toast Platform API — REST over HTTPS |
| Auth method | Toast API credentials stored encrypted in WFW vault |
| Data pulled from Toast | Menu items, prices, allergen flags, daily specials, location hours, order status, location configuration |
| A2A mode | Delivery platform AI callers receive structured JSON order status — no voice latency, machine-readable format |
| Analytics endpoint | GET /v2/agents/{id}/calls — call volume, inquiry types, peak times for restaurant manager reporting |
| Multi-location support | WFW handles location routing — callers are matched to the correct Toast location based on the number they called |
API Endpoints
The WFW endpoints this integration enables.
These /v2/ endpoints become available once Toast is connected. Pull call analytics for manager reporting — inquiry types, peak call times, and order status call frequency — via the WFW REST API.
Full API Reference →Available Endpoints
/v2/agents/{id}/callsCall analytics for restaurant manager — volume, inquiry types, peak hours
/v2/calls/initiateTrigger outbound order-ready notification call from Toast order status
/v2/agents/{id}Check agent health and Toast API connection status
Setup
Connect Toast in three steps.
Toast credentials, location configuration, agent activation. Menu calls answered from day one.
Add Toast API credentials
Enter your Toast API client ID and secret in WFW admin under Integrations → Toast. Encrypted and stored in the WFW vault.
Configure locations
Map your Toast location IDs to WFW phone numbers. For multi-location restaurants, WFW routes each inbound call to the correct location's Toast data.
Enable on your agent
Toggle Toast active on your agent. Menu inquiries, order status calls, and after-hours capture go live immediately.
Get Started
Connect Toast to your voice agents.
Menu inquiries answered instantly. Order status calls handled automatically. After-hours inquiries captured — not lost to voicemail. All powered by live Toast data.
Connect ToastQuestions? Talk to our team →