How to route enquiries across multiple properties
A practical map for separating guests from owners, identifying the property and handing context to the responsible person.
In this guide · 5 sections
A message such as “can I arrive later?” seems simple. In a multi-property operation, the answer depends on the property, booking, approved instructions and person on duty. Automating the first reply without resolving those dependencies can simply move the confusion elsewhere.
Use this map to identify the property, gather context and hand the enquiry to the right person.
Separate two journeys at the start
A guest needs help with a stay. An owner may want a company to manage a property. These are different processes: one needs operational context; the other needs a commercial assessment, geographic coverage and a conversation about the service.
Provide two clear options and an alternative for people who are unsure. Do not ask an owner for a booking reference or treat a guest enquiry as a property acquisition opportunity.
Map the context handover
Use one row per step. Begin with one enquiry type and a representative property.
| Step | Minimum information | Who confirms | Condition for moving forward |
|---|---|---|---|
| Entry | Guest, owner or another subject | Customer service | Journey identified |
| Property | Property and appropriate reference | Operations team | Unambiguous property |
| Need | Question, relevant date and language | Customer service | Understandable enquiry |
| Decision | Approved instruction or exception | Person responsible at the property | Authorised answer |
| Completion | Next action and responsible person | Operations team | Customer informed and follow-up assigned |
Collect only what is needed. A booking reference may help locate the booking; identity documents or payment data should not be requested for convenience in this workflow.
Define exceptions before automation
Late arrivals, maintenance problems and refund requests may have different owners and urgency. Define service hours, out-of-hours handover and the existing approved channel for urgent situations. An automatic acknowledgement is not a resolution.
When the property is unclear or information is outdated, ask for clarification or hand over to a person. Do not invent instructions or substitute information from another property.
Choose the appropriate intervention
WhatsApp Agent can collect context through configured instructions and support human handover in the inbox. The team checks the booking and instructions in its existing system. The product does not include a universal PMS connection, automatic booking or synchronised calendar.
If the operation needs a property-aware portal or PMS connection, Studio first identifies the supplier, available API, permissions, data owner and maintenance costs. An integration enters the proposal only after this assessment.
Test the workflow and record a baseline
Rehearse with fictional data: a known property, an unknown property, another language, an out-of-hours enquiry and human handover. Record what the team needs to consult in each case.
In an authorised pilot, compare equivalent periods and disclose the sample size. Useful observations include unassigned enquiries, time to first human reply and enquiries reopened because context was missing.
Start with the multi-property workflow and illustrative demonstration. For an initial assessment, describe the workflow to Makers. Makers leads this conversation and confirms scope before proposing a product or project.
