Vendor product documentation checked 27 August 2026. No affiliate links.
Start with the work the software needs to do
Current product pages from Hostaway, Guesty, Hospitable, iGMS, and Turno describe event-based messages, reservation-linked tasks, payment or review workflows, and cleaning scheduling. Those are useful features. The operator still needs a person to interpret unusual guest requests and own the result when a vendor fails.
Start by checking whether the underlying reservation state reaches every booking channel. If a date or status change is missing from one channel, compare channel managers for Airbnb before adding message or task rules. Otherwise, automation may act on stale booking data.
For each task, write down what starts it, what the software may do, and how your team can confirm the result. Automation is incomplete until a person owns its failures. Assigning that role to a short-term-rental virtual assistant requires documented access, approval limits, coverage hours, and escalation conditions. That turns the product claims into something you can test, regardless of how much artificial intelligence (AI) appears in the description.
See the vendors' descriptions of Hostaway automations, Guesty workflows, Hospitable messaging, iGMS automation, and Turno cleaning coordination.
Five products, two different kinds of job
Feature names are the vendors' own. Inclusion can vary by plan.
| Product | Main use | Documented automation | Buying path | What to confirm |
|---|---|---|---|---|
| Hospitable | Property management system with extensive guest messaging | Scheduled and event-based messages, common-question replies, a unified inbox, and cleaning or teammate workflows. Artificial intelligence (AI) and device features vary by plan. | Public plans, a free Essentials tier, and a 14-day trial. | Test whether replies use the right property facts and whether the purchased tier includes the required workflow. |
| Hostaway | Property management system with reservation-based automations | Automated messages, reviews, reservation-linked cleaning and maintenance tasks, and payments. | Sales-led quote; no public dollar price on the pricing page. | Evaluate the automation inside the wider Hostaway contract, permissions model, and channel setup. |
| Guesty | Property management system for guest and operating tasks | Messaging, task creation, turnover workflows, payments, review requests, and pricing tools. Some products are separate add-ons. | Public Lite entry price; Pro and Enterprise are quoted. | Ask which workflow, AI, lock, accounting, and support products are included in the quoted plan. |
| iGMS | Property management system with messaging and task automation | Message templates, calendar sync, review workflows, cleaning schedules, and task management. Flex lists AI-driven replies; higher tiers add further AI and finance features. | Public per-booked-night Flex option and per-property Pro tiers. | Model the bill under your actual booked nights and confirm which AI and owner features require a higher tier. |
| Turno | Cleaning scheduling tool connected to the reservation system | Calendar-linked cleaning schedules, assignments and acceptance, cleaner communication, marketplace search, and automatic payments. | Host and cleaner pricing is published separately by Turno. | Use it to coordinate turnovers. Reservation, inbox, and booking-channel data still live elsewhere. |
Sources: Hospitable guest communication and pricing; Hostaway automation and pricing; Guesty automation and pricing; iGMS automation and pricing; and Turno features and pricing.
Five workflows to specify before you shop
Reservation confirmed
- Automatic action
- Create the guest thread, send the correct confirmation, and start related work from the reservation record.
- Failure signal
- Required guest or property data is missing, or a connected system does not receive the booking.
- Human decision
- Correct the record, choose whether to contact the guest, and reconcile affected systems.
Reservation changed or cancelled
- Automatic action
- Update scheduled messages, access timing, payment rules, and turnover work.
- Failure signal
- An old message, code, charge, or task remains active.
- Human decision
- Reverse the stale action and confirm the replacement state with the guest or vendor.
Check-in approaches
- Automatic action
- Release approved arrival instructions when payment, identity, and readiness conditions are satisfied.
- Failure signal
- The property is not ready, access data is absent, or a condition remains unresolved.
- Human decision
- Delay, provide alternate access, or escalate the readiness problem.
Guest sends a question
- Automatic action
- Route a known question to a template or draft a response from approved property information.
- Failure signal
- The request is ambiguous, safety-sensitive, policy-sensitive, or requires money or vendor action.
- Human decision
- Interpret the request and approve the response, expense, exception, or escalation.
Checkout occurs
- Automatic action
- Open the turnover task and notify the assigned cleaner through the connected workflow.
- Failure signal
- The cleaner declines, misses the acknowledgement, or reports damage or unfinished work.
- Human decision
- Reassign the job, authorize remediation, and decide whether the next arrival is affected.
An alert needs a recovery owner
A dashboard full of alerts does not resolve anything by itself. Each exception needs the reservation, property, failed action, current guest or vendor impact, evidence already checked, allowed response, and next person to contact.
Keep the record beside the workflow it belongs to. That lets you see whether the failure came from bad source data, a disconnected integration, an unavailable vendor, or a decision the automation was never allowed to make.
Example exception
- Event
- Guest changed arrival from Friday to Thursday
- Expected
- Arrival message, access timing, and turnover task update
- Observed
- Reservation changed; Thursday access code is still absent
- Immediate action
- Verify the lock integration and prepare approved backup access
- Owner decision
- Required only if the backup changes security policy or creates an expense
Build from the reservation outward
- Keep booking details in one place. Your PMS or channel manager should hold the reservation dates, status, guest identity, and booking channel.
- Write the conditions. State exactly when a message, task, code, payment action, or review request may fire.
- Make completion visible. The person monitoring the work needs to see delivery, task acceptance, payment, and device status.
- Assign problems. Name who watches for them, the hours they cover, what they may approve, and when they contact the owner.
- Test changes and cancellations. Change and cancel a reservation, then confirm that every related message and task changes or cancels with it.
Test the native PMS workflow first
First test the built-in rules in the platform that already holds the reservation. Add cleaning, pricing, access, or integration software only when the current platform cannot meet a written requirement. Each added tool brings another data connection, login, bill, and place where an update can fail.
Use the product table above to compare buying paths against the written workflow. A full Airbnb management software platform is the starting point when one system needs to hold reservation state and coordinate several workflows. Add a specialist tool only for a requirement that remains unmet after that test.
Give the person monitoring problems authority to act
A list of alerts is not useful if the person watching it can only forward every problem. Define which replies they can send, which refunds or expenses require approval, who can reassign vendors, and which safety issues go straight to the owner. Settle those terms before assigning the monitoring role.
An Airbnb virtual assistant can own that review only after the systems, coverage, access, allowed actions, and escalation conditions are documented. If that is the recurring role you are defining, book a consultation to map it before placement.