Properties, reservations and guest threads
Hostaway
Webhooks and scheduled sync keep the booking context current, and guest replies return to the original Hostaway conversation.
How Hostaway connectsIntegration stack · Hostaway + PriceLabs + Slack
Give an AI operator Hostaway reservation context and PriceLabs recommendations, then keep human pricing approvals and escalations in Slack.
Who this stack is for
The coordination problem
The answer
Proptonomy brings the relevant reservation and pricing context into the same operational conversation. PriceLabs remains the pricing engine, Hostaway remains the PMS, and Slack remains the internal approval channel. Price changes happen only when an authorised teammate explicitly asks for them.
Properties, reservations and guest threads
Webhooks and scheduled sync keep the booking context current, and guest replies return to the original Hostaway conversation.
How Hostaway connectsRecommended prices and listing bounds
The AI can read recommended prices and bounds, explain them to staff or owners, and apply an explicit, authorised change.
How PriceLabs connectsTeam questions, exceptions and approvals
The right channel receives the decision with the relevant figures, and a teammate can approve or ask a follow-up without leaving Slack.
How Slack connectsExample workflow
The stack matters only if the same operational record survives the handoff between tools and people.
An owner or teammate asks why a weekend is empty or what the current rate is. The Hostaway listing and reservation context identify the exact unit and dates.
Proptonomy reads the recommended price and current minimum, maximum or base bounds for that listing instead of inventing an answer.
If a change is proposed, the facts and the exact before-and-after values go to the authorised team channel for an explicit instruction.
An approved PriceLabs change is applied and confirmed with what changed. PriceLabs still pushes rates to Hostaway through its normal connection.
Boundaries
A trustworthy integration explains the non-goals as clearly as the data flow. These boundaries prevent duplicate records and unexpected writes.
The operation does not migrate away from Hostaway, and Proptonomy does not edit listings or reservations as part of this workflow.
Proptonomy reads and acts on selected PriceLabs controls; it does not replace PriceLabs forecasting or its channel-manager sync.
Reading is safe by default. Changing a pricing bound or override requires an explicit request from an authorised teammate and leaves an audit trail.
Rollout
The exact credentials differ by system, but the safe operating sequence stays the same.
Connect Hostaway, PriceLabs, Slack with the credentials or partner flow described on each integration page.
Check that properties, reservations, partner chats and external records resolve to the same operational entity before any write action is enabled.
Let the AI read current traffic, draft answers and show proposed actions. Correct property knowledge and routing while nothing is sent automatically.
Turn on the inboxes and actions the team trusts, while sensitive categories and less-tested properties remain behind approval.
FAQ
Direct answers, written to stand on their own in search and AI results.
No. PriceLabs remains the pricing engine and continues pushing rates to Hostaway. Proptonomy makes its recommendations available inside operational questions and can apply an authorised bound or override.
Not in this workflow. It can read and explain pricing data by default. A base, minimum, maximum or date override is changed only after an authorised teammate explicitly asks for it.
Yes. Guest conversations sync from Hostaway and approved or enabled replies go back to the same thread through Hostaway.
Slack gives the internal team a familiar place for exceptions, pricing approvals and follow-up questions while the reservation and rate evidence stays attached to the decision.
We will show what connects, what remains read-only and how the first real workflow runs.
Sign up in 30 seconds and we will set your team up in the next onboarding batch.