AI turnover inspection for Hosthub

Overview

Hosthub keeps a precise record of the booking and a written one of the property. Rentals, channels, calendars and rates are synchronised to the minute, and when something needs a human, a booking Action is flagged at one of three levels with a note explaining why, which then lands in a Daily Actions Report every morning. The note is a sentence a person typed. Nothing in Hosthub looks at the rental. RapidEye reads your rentals and their booking dates from Hosthub, together with the photos your team takes at the turnover, and returns a finding per issue: what is damaged, what was not cleaned, what is missing, with the photo of that spot before the stay next to the one after it.

How it works with Hosthub

Hosthub already knows the two things a finding has to be tied to: which rental, and which stay. RapidEye takes those and adds the third thing, what the place actually looked like.

• The rental. Hosthub's rental record is the anchor. Findings arrive named by rental, so a manager running forty of them reads a list of properties rather than a folder of loose photos, and a rental that keeps producing findings is visible as a pattern instead of a memory.
• The booking dates. Check-out sets the moment a turnover exists and check-in sets the deadline it has to beat. RapidEye reads the photos from that window against the last known state of the same spot, which is what makes a scratch attributable to one stay rather than to whoever was blamed for it.
• Preparation Time. Hosthub can block the night before and after every reservation to keep back-to-backs off the calendar. A rental with no preparation time set is a rental where a turnover has no slack in it, and those are the ones most worth reading first.
• What comes back as an Action. A finding is not an Action. It is the evidence you would want before deciding whether to raise one, and at which of Hosthub's three levels. You raise it in Hosthub, with the note in your own words, and it flows into your morning report exactly as it does today.
• Owners and their rentals. Hosthub scopes people to rentals, and so does a finding. An owner conversation about a damaged sofa is easier when the evidence is one rental, one stay, one photo, rather than a thread.

Every finding says which rental, which room, where in the room, what kind of problem it is, how bad it is, and shows the before and after photo. Findings arrive in the RapidEye dashboard, and in Slack or an inbox when your team prefers to be nudged there. Hosthub stays the system of record: RapidEye creates nothing, clears nothing and blocks nothing. And if your turnovers produce something other than still photos, video walkthroughs, 3D scans or an inspection format your team built, that is a setup conversation rather than a limit. Tell us the shape and we read it.

How to connect Hosthub to RapidEye

1. Create the team member. In Hosthub, go to Team Management, then Team members, and create a new member with the name Rapid Eye and the email support@rapideyeinspections.com. Team Management sits in the left sidebar under the Admin area and is visible only to Admins. Hosthub sends a verification email to that address.
2. Give it the Ground Crew role. Open the member's Manage page from Setup, then Team, then the three dots next to the name. Select the role first and save. Ground Crew is Hosthub's documented basic role for on-the-ground staff: view only on rentals and booking details, no access to guest details, price details, access codes, the Inbox, rate management or expenses.
3. Assign the rentals. On the same Manage page, scroll to Assigned rentals at the bottom, add the rentals you want turnovers checked on with the green button, and save with the blue button at the top right. Hosthub only applies the assignment once the invitation has been accepted, so a member showing zero rentals is usually one that has not accepted yet. We accept and email you when your first findings are ready.

What Hosthub records about a turnover

Checked against Hosthub's help centre, September 2026.

Two parts of Hosthub decide what an operator can know about a turnover after it happened: the Action flagged on the booking, and the role the person doing the work was given. Both are documented carefully, and together they explain why a turnover leaves a written trail rather than a visual one.

Booking Actions

According to Hosthub's help centre documentation (hosthub.com), booking Actions exist to flag reservations that need human intervention, for offline tasks, maintenance issues and administrative follow-ups that need to stay tied to a specific booking. They are set from the Booking Details drawer or the Inbox header, they are available on every plan to any user with the Actions and Notes permission, and they come in three levels.

Setting one immediately prompts for a note, which Hosthub makes required on purpose so anyone receiving the alert knows why the flag was raised. Everyone with access to that rental is notified, the flag then shows as a coloured marker on the dashboard card, over the channel icon in the bookings index, as a dot on the booking bar in the multi-calendar and in the header of the booking and the Inbox. Every morning at 6:00 AM local time a Daily Actions Report consolidates every booking still carrying an Action Required or Urgent flag. Actions have to be cleared by hand with All done, which is also what takes the booking out of tomorrow's report.

It is a good system, and the thing to notice is what it is made of: a level, a note, and a person who decided to raise it. Hosthub documents no photograph anywhere in that flow. A turnover where nobody typed anything produces no record at all, which is exactly the turnover an operator wants to know about.

Who can see what: the Ground Crew role

Hosthub documents a set of basic roles that exist in every account, and one of them is built for the person cleaning the property. It is worth reading closely before you invite a cleaner, because the shape of it is unusually well judged.

Read across the Ground Crew column and the design is clear: a cleaner can see where to go and when, can write on the booking, and can see nothing about the guest or the money. That is the right amount of access for the job, and it is the same amount RapidEye asks for. Hosthub also documents two further roles, Property Owner with reporting only and Read Only, plus custom roles for Pro accounts, and notes that team members exist as records even before they verify their email, though rental assignments only take effect once the invitation is accepted.

Does Hosthub have cleaning tasks with photos?

Not as a native object. Hosthub's help centre has a category called Cleaning and Task Management, and the article inside it explains how to connect Turno: create a Turno account, sync it with Hosthub, and both systems share rentals and bookings so tasks, automations and workflows can be built on current information. Hosthub's write-up of Turno lists its quality assurance tools, checklists, photo sharing and problem reporting, along with auto-scheduling and its cleaner marketplace. Hosthub also has no native mobile app at all; it documents a mobile web app at its app domain and says most of its users work from it, which is the same place a cleaner would open a capture link.

Hosthub integration FAQ