Scope first
List the exact fields, actions and escalation rules needed for the first use case.
Hotel systems
Start with the PMS that holds the guest truth.
Each integration is scoped against the system version, permissions and workflows required by the property. These pages describe possible deployment patterns, not a claim of marketplace certification.
PMS · Hotel operations
Mews
Connect conversational workflows to the reservation and guest context available in a Mews environment.
- Availability and rate lookup scope
- Reservation actions to validate
- Structured conversation outcomes
PMS · Enterprise hospitality
Opera Cloud
Define a controlled voice layer around the Opera workflows used by a property or hotel group.
- Cloud and deployment context review
- Approved read and write actions
- Human fallback and audit trail
PMS · Independent hotels
Cloudbeds
Scope guest and reservation workflows around the Cloudbeds configuration used by the hotel.
- Property and reservation context
- Booking workflow validation
- Pilot before production routing
Beyond the PMS
One guest journey touches more than one system.
Yourcall can be scoped around the tools already present in the operation. Availability depends on the customer's environment and access.
AmadeusSalesforceHubSpotZendeskFreshdeskTwilioZenchefSevenRoomsOpen APIWebhooks
Integration principles
Useful integrations are narrow, testable and observable.
Read access supplies only the context required for the call. Write actions use the permissions approved for the workflow and count as complete only after the destination confirms success; timeouts, errors and unavailable inventory follow the tested fallback path.
Least access
Request only the permissions required by the agreed workflow and environment.
Test safely
Validate happy paths, exceptions and duplicate-action protection before live traffic.
Keep a record
Return the intent, action, outcome and escalation context to the operational team.
What we confirm before an integration pilot
No two hotel environments are identical. The discovery step turns a broad logo on a diagram into a precise, testable scope.
System context
Product, version, deployment model, account structure and existing middleware.
Allowed actions
What the agent may read, create, update, cancel, transfer or only recommend.
Failure handling
Timeouts, unavailable inventory, authentication failure, human escalation and retry rules.