01 / THE QUICK VIEW
Everyday automation.
A connected workspace for guest messages, channel calendars and daily operations. A useful starting point when repetitive hosting tasks consume your week.
The editorial take
Put Hospitable on your shortlist if its workflow matches your biggest operational need. Use a trial or a focused demo to verify that fit with your own properties, channels and team.
- Start your evaluation with
- Guest communication and automation
- Pricing approach
- Published plans; feature limits apply
- Direct booking setup
- Available on eligible plans
- Our assessment
- Provider documentation; no claimed hands-on test
02 / THE EVERYDAY WORK
Look beyond the feature list.
Guest communication
Can the system send the right arrival instructions for each property and channel? Ask to see exception handling, not just a successful scheduled message.
Calendar and channel management
Connect a test listing where possible. Verify changes to availability, restrictions and rates, then ask what happens when a connection is interrupted.
Direct bookings
Confirm the eligible subscription, booking service fees, payment processing and the protections available in your country.
03 / STRENGTHS & CHECKS
The useful details, upfront.
Reasons to explore
- Guest communication, calendars and task coordination in one workspace.
- Automations can reduce repetitive work around arrivals and departures.
- Direct booking tools are available on eligible plans.
Before you commit
- Check which AI and automation features are included in your chosen plan.
- Account for Direct booking fees as well as the software subscription.
- Test the connections for your own channels, smart devices and accounting tools.
PLAN YOUR SETUP
Which Hospitable plan fits the job?
Start with the smallest plan that covers your required workflow. A free account can help you explore the product, but it is not a substitute for checking the paid functions your operation depends on.
| Plan | Published distinction | Decision to make |
|---|---|---|
| Essentials | Free subscription; limited AI and optional paid features. | Identify which integrations and automations your setup needs. |
| Host | One active property included; maximum two. | Consider the next property before building your process around this tier. |
| Professional | $59/month includes two active properties; then $15 per additional active property. | Direct booking and smart-device needs make this a relevant starting point. |
| Mogul | Owner statements and owner portals. | Get a written quote: public pricing and help documentation disagree on additional-property pricing. |
These are documented boundaries, not performance scores. Read the feature matrix and billing documentation together. A feature marked “coming soon” should not determine a purchase that depends on it today.
Subscription cost as your portfolio grows
MESSAGING, WITH BOUNDARIES
Build message rules around exceptions.
A useful automation has a trigger, accurate property information and a clear owner when something goes wrong. Start with arrival instructions and recurring questions. Keep access changes, complaints and unusual requests in a workflow where a person can intervene.
Scheduled messages
Record the send time and what should happen if reservation dates change.
AI replies
Separate a suggested answer from an answer sent automatically. Review the property information behind it.
Human handover
Decide who sees an unresolved question and how a colleague knows it has been handled.
Hospitable documents AI Auto Replies and their controls. That confirms availability, not accuracy for your property. Use your own recurring questions, record the output and correct the underlying information before broadening automation.
An automatic message is useful when the information is right and the exception has somewhere to go.
BUDGET THE WHOLE WORKFLOW
Separate subscription, bookings and devices.
Write three lines in your budget: software subscription, charges linked to direct reservations, and other necessary services. Keep processing separate so it is not missed or counted twice. For a seasonal operation, compare a quiet month with your busiest month.
The paid base subscription continues while the subscription is active even if properties are inactive. Pricing-only usage has separate billing rules, so no arrivals does not necessarily mean every charge disappears. Confirm how your planned settings will be billed.
Our Direct fee breakdown explains Basic and Premium; the cost worksheet accepts a confirmed quote and your booking assumptions. It does not forecast additional revenue.
| Test | Record |
|---|---|
| Changed arrival | Next scheduled message, its content and revised send time. |
| Device connection | Exact model, connection requirements and additional charges. |
| Direct reservation | Guest total, provider fee, processing and the payment record. |
| Owner workflow | Property access and whether the statement belongs to your plan. |
The product is less compelling if your shortlisted plan cannot handle an essential job, or if the remaining work is split across too many subscriptions. For more involved team and reporting requirements, use the Hostaway reporting checks as another evaluation path.
YOUR FIRST AUTOMATION AUDIT
Give every property a reliable information sheet.
Before evaluating Hospitable’s replies, collect the facts a guest actually asks for. Include the correct entrance, parking restrictions, arrival window, Wi-Fi instructions, heating controls and emergency contact. Keep the details property-specific: two apartments in the same building may use different entrances or have different parking arrangements. A beautifully written answer for the wrong apartment is still an operational failure.
Choose a person to approve changes. When a door code, parking rule or appliance changes, update the information used by the workflow and inspect the next relevant message. Avoid leaving conflicting instructions in an old template and a newer property note. During the demonstration, ask where each answer comes from and which source takes precedence.
Try an ambiguous question
“Can we arrive early?” requires more than a check-in time. The answer may depend on a departing guest, cleaning progress and your policy. Your desired result could be a request for human approval rather than an immediate yes. Write that expected result before testing the reply.
A small, repeatable message test
Collect representative questions
Use anonymized examples from your own inbox. Include an ordinary question, a question with missing information and a request outside your house rules. Remove guest names and private details from any shared evaluation document.
Define a satisfactory response
Record the required fact, any information the reply must not disclose and when a person should take over. A friendly tone is useful, but accuracy and the correct next action determine whether the reply is usable.
Review the complete conversation
Inspect earlier messages as well as the latest answer. A second instruction can contradict an agreement already made by a co-host. Ask how your team can review or stop the next automated response.
These are proposed evaluation checks, not measured Hospitable results. Start with a limited set of predictable questions. Expand only after the output and handover match your requirements.
A MANAGEABLE DAILY ROUTINE
Use the inbox to surface decisions.

For a small coastal rental, routine messages might concern parking, balcony access or the walk to the beach. Exceptions are different: a guest cannot enter, a cleaner reports damage, or an arrival changes at short notice. Decide which person covers urgent issues and how they acknowledge responsibility. An unread count alone cannot tell you whether a request is being handled.
Use a short opening check: inspect today’s arrivals, unresolved conversations and changes since the previous shift. At handover, record the remaining action rather than merely forwarding a thread. “Confirm whether the cleaner can finish before 2 pm” gives the next person a clear job; “see guest message” does not.
Check whether automation is helping
Keep a baseline from your current process, then compare similar operating periods. Track conversations requiring a manual correction, missed handovers and time spent maintaining templates. Avoid counting every automatically sent message as time saved: some messages would never have required a separate manual reply.
If your test repeatedly needs information that is not available to the workflow, keep that case with a person or simplify the rule. Review the message controls above before broadening coverage. When the problem is mostly website presentation or checkout rather than communication, investigate the Lodgify guest-journey checks as a separate shortlist direction.
Before committing, retain a list of essential scenarios that passed, scenarios that require a workaround and unresolved questions. That record makes the decision explainable to a co-host and gives you a practical starting point for the first month.
04 / YOUR NEXT STEP
Bring a real workflow to the demo.
Use one representative property
Choose a listing with your typical fees, channels, arrival process and turnover requirements. A simpler sample can hide the work you actually need to automate.
Follow a reservation end to end
Check confirmation messages, payments, date changes, cleaning tasks and checkout. Include one cancellation and one message that needs a human response.
Get the full cost in writing
Ask for the subscription, booking and payment charges, onboarding, optional integrations and renewal conditions for your portfolio.
Plan the switch carefully
Keep a record of future bookings. Agree on channel connection order and verify calendars and payments before retiring the old workflow.
05 / FOLLOW THE EVIDENCE
Official sources.
This overview summarizes publicly documented capabilities. It does not claim a hands-on test or guaranteed results. Plan availability and local payment support should be confirmed directly.
