Properties, reservations and guest threads
Guesty
Webhooks and scheduled sync keep the stay history current, so a performance question is answered against real bookings rather than a summary.
How Guesty connectsIntegration stack · Guesty + Wheelhouse + Slack
Answer owner questions with Guesty reservations, Wheelhouse performance and a Slack approval
Give an AI operator Guesty reservation context and Wheelhouse recommended prices and KPIs, then keep pricing approvals and owner escalations in Slack.
Reviewed 28 August 2026 · Every system below has its own current Proptonomy integration page
Who this stack is for
Guesty operators that run Wheelhouse for revenue management and spend real time answering owners about occupancy, rate and performance.
The coordination problem
An owner asks why their unit was quiet last month. The stay history is in Guesty, the recommended rate, the occupancy against the neighbourhood and the RevPAR are in Wheelhouse, and the person answering has to open both and assemble the story by hand. It is slow enough that the answer is often a promise to look into it.
The answer
One workflow, with clear system ownership
Proptonomy joins that context without replacing either system. It reads the reservations from Guesty and the recommended prices, pricing settings and KPIs from Wheelhouse, and answers with the actual figures. If the conversation ends in a price decision, that decision is put to the team in Slack before anything is changed.
Recommended prices, pricing settings and KPIs
Wheelhouse
The AI reads the nightly recommendation, the base price and absolute floors, and occupancy against the neighbourhood, ADR and RevPAR. It can apply an explicit, authorised change.
How Wheelhouse connectsTeam questions, exceptions and approvals
Slack
The proposed change goes to the authorised channel with the figures behind it, and a teammate approves or asks a follow-up without leaving Slack.
How Slack connectsExample workflow
From incoming question to confirmed outcome
The stack matters only if the same operational record survives the handoff between tools and people.
- 1
An owner asks how the property is doing
The Guesty listing and its reservations identify the exact unit and period, including the nights that were blocked rather than unsold.
- 2
Wheelhouse supplies the performance
Proptonomy reads occupancy against the neighbourhood, ADR, RevPAR and the recommended prices for the days ahead, so the reply carries figures rather than reassurance.
- 3
Slack holds the decision
If the answer is that the rate should move, the before-and-after values go to the authorised team channel for an explicit instruction.
- 4
The change is applied and reported
An approved base price, absolute minimum or custom rate is written to Wheelhouse and confirmed with what actually changed. Wheelhouse still posts rates to the channel through its own connection.
Boundaries
What each tool continues to own
A trustworthy integration explains the non-goals as clearly as the data flow. These boundaries prevent duplicate records and unexpected writes.
Guesty owns the reservation
The operation does not migrate away from Guesty, and Proptonomy does not edit listings or reservations as part of this workflow.
Wheelhouse owns the rate engine
Proptonomy reads and acts on selected Wheelhouse settings; it does not replace Wheelhouse's forecasting or its rate posting to the channel.
People approve exceptional changes
Reading is safe by default. Changing a base price, an absolute minimum or a custom rate requires an explicit request from an authorised teammate and leaves an audit trail. A read-only Wheelhouse API key removes the possibility entirely.
Rollout
Connect, observe, then enable
The exact credentials differ by system, but the safe operating sequence stays the same.
- 1
Connect the sources
Connect Guesty, Wheelhouse, Slack with the credentials or partner flow described on each integration page.
- 2
Confirm the matches
Check that properties, reservations, partner chats and external records resolve to the same operational entity before any write action is enabled.
- 3
Review observe-mode work
Let the AI read current traffic, draft answers and show proposed actions. Correct property knowledge and routing while nothing is sent automatically.
- 4
Enable one boundary at a time
Turn on the inboxes and actions the team trusts, while sensitive categories and less-tested properties remain behind approval.
FAQ
Guesty + Wheelhouse + Slack FAQ
Direct answers, written to stand on their own in search and AI results.
Does Proptonomy replace Wheelhouse?
No. Wheelhouse remains the revenue management system and continues posting rates to your channel. Proptonomy makes its recommendations and KPIs available inside operational and owner questions, and can apply an authorised change.
Can the AI change prices on its own?
Not in this workflow. It reads and explains pricing and performance data by default. A base price, absolute minimum, absolute minimum stay or custom rate is changed only after an authorised teammate explicitly asks for it.
What if my channel does not support a setting?
Wheelhouse accepts the change and quietly discards what the channel cannot act on, such as minimum stays on some channels. Proptonomy reads the warning it returns and reports that the setting was not applied, rather than confirming a change that never landed.
How is this different from the PriceLabs stack?
The shape is the same and only one of them is usually in play, since Wheelhouse and PriceLabs occupy the same seat. Wheelhouse also exposes portfolio KPIs such as occupancy against the neighbourhood, ADR and RevPAR, which is what makes owner reporting part of this workflow.
Map this stack to your accounts.
We will show what connects, what remains read-only and how the first real workflow runs.
Scale your property management
with AI as a native team member
Sign up in 30 seconds and we will set your team up in the next onboarding batch.
No commitment