Voice reservations and A2A availability — connected to Mews.
WFW connects to Mews Distribution and Operations APIs. Guests book by phone with live inventory. OTA AI callers get structured JSON. Pre-arrival personalization calls go out automatically — all from Mews data.
One WFW integration handles both human guests and A2A booking platforms. No separate implementation for each caller type.
A2A Dual-Mode — OTA AI vs. Guest Call
A2A dual-mode — automatic
WFW detects OTA AI callers and returns structured JSON. Human guests always get voice. One integration, both modes.
Capabilities
What this integration enables.
Three concrete capabilities unlocked by connecting WFW to Mews.
Live Data
Real-Time Availability and Reservation Creation
WFW queries the Mews Distribution API for live availability by room type, date range, and rate plan. When a guest confirms, WFW creates the reservation via the Mews Operations API — complete with guest profile, preferences, and arrival instructions.
Live Data
A2A Dual-Mode: OTAs Get JSON, Guests Get Voice
When an OTA booking platform's AI calls to check availability or modify a reservation, WFW detects the agent caller and responds with structured JSON — not voice. Human guests get a natural conversation. One integration handles both automatically.
Live Data
Pre-Arrival Personalization Calls
WFW initiates outbound calls to arriving guests 24 hours before check-in. The agent knows the guest's room type, length of stay, and any prior visit history from the Mews guest profile — offering tailored upsells and arrival instructions.
Data Flow
How it works.
From caller type detection to reservation creation — what moves between WFW and Mews.
Caller identified as guest or agent
WFW identifies whether the inbound call is from a human guest or an A2A caller (OTA platform, travel management system). Human guests receive voice; agent callers receive structured JSON via WFW's A2A response protocol.
Availability queried from Mews Distribution API
For reservation requests, WFW queries the Mews Distribution API for live room availability, rate plans, and restrictions. The agent presents accurate options — no inventory lag, no manual rate lookups.
Reservation created in Mews Operations API
When a guest confirms a booking, WFW creates the reservation via the Mews Operations API, attaching the guest profile, room preferences, and any special requests captured during the call.
Pre-arrival outreach triggered from Mews data
WFW reads upcoming arrivals from Mews and triggers pre-arrival calls via POST /v2/calls/initiate. The agent's context includes the guest's room category, prior visits, and any preferences recorded in the Mews profile.
Use Cases
Before and after.
Real hotel guest experience workflows transformed by the Mews + WFW integration.
Before
Guests calling to book hear an IVR that transfers them to a reservation agent — who may or may not be available. Calls after hours go to voicemail and reservations are lost.
After
WFW answers reservation calls 24/7. Agent queries live Mews availability, answers questions about room types and amenities, and creates the booking before the guest hangs up.
Before
Concierge requests routed through front desk, often during peak check-in/check-out periods. Guest experience suffers from wait times and information gaps.
After
WFW handles concierge calls with access to the guest's Mews profile — room number, arrival date, loyalty status. Requests are logged in Mews. Escalations route to staff when needed.
Before
Generic confirmation emails are the only pre-arrival touchpoint. Upsell opportunities for room upgrades, dining, and spa are missed entirely.
After
WFW calls arriving guests with personalized messages based on their Mews booking. Upgrade offers, restaurant reservations, and early check-in options are presented conversationally — conversion tracked in Mews.
Technical Details
Integration specifications.
Dual API connections, A2A detection, and data fields for your tech team.
| Connection method — availability | Mews Distribution API — REST over HTTPS for real-time room inventory and rates |
| Connection method — operations | Mews Operations API — REST over HTTPS for reservations, profiles, and service requests |
| Auth method | Mews access token stored encrypted in WFW vault |
| A2A detection | WFW identifies OTA AI callers by UA and caller patterns — returns structured JSON instead of voice response |
| Data pulled from Mews | Room availability, rate plans, guest profile, reservation history, preferences, loyalty status |
| Data written to Mews | New reservations, reservation modifications, service requests, guest profile updates, concierge notes |
API Endpoints
The WFW endpoints this integration enables.
These /v2/ endpoints become available once Mews is connected. Trigger pre-arrival outreach, pull reservation data extracted from calls, and monitor guest engagement campaign performance.
Full API Reference →Available Endpoints
/v2/calls/initiateTrigger pre-arrival personalization call for an upcoming Mews reservation
/v2/calls/{id}/extractionsRetrieve reservation data, guest preferences, and upsell responses from the call
/v2/agents/{id}Check agent health and Mews API connection status
Setup
Connect Mews in three steps.
Access token entered once. Both APIs configured automatically.
Add Mews access token
Enter your Mews access token in WFW admin under Integrations → Mews. WFW configures connections to both the Distribution and Operations APIs automatically.
Configure A2A response rules
Set which caller patterns WFW treats as A2A (OTA booking platforms, travel agents). These callers receive structured JSON responses instead of voice.
Enable on your agent
Toggle Mews active on your agent. Reservation calls, concierge handling, and pre-arrival outreach go live immediately.
Get Started
Connect Mews to your voice agents.
Voice reservations, A2A availability responses, and pre-arrival personalization — all powered by live Mews data. No middleware required.
Connect MewsQuestions? Talk to our team →