Property Requests

The Property Requests section is where the Operations team manages and processes new landlords’ property connection requests. It centralizes all information for each request: property details, selected tier, requested services, and chosen channels. Operations users review requests, create or connect listings on OTAs, and track request status from here.

Where it lives in the dashboard

• List view: Property Requests (shows all properties with one or more connection requests).

• Details view: Property Request Details (drill-down for a single property with tabs for overview, details, images, amenities, location, pricing, rooms, and channels).

• Direct link: https://admin.hububb.com/dashboard/property-requests

Before connecting a property to any channel, make sure the following are completed:

• An account has been created on the OTA using the property details.

• The listing has been published on the OTA.

• The listing is currently active on the OTA.

• You are logged in to the OTA with the same account used to create the listing.

⚠️ The connection process will fail if the listing is not active on the OTA prior to starting the connection.

1

Open Property Requests

• The list shows properties that have at least one connection request and have completed onboarding.

• Search by property name, landlord name, street, or connection channel.

• Filter by request status (Pending, In Progress, Completed, Rejected) or channel (Airbnb, Booking.com).

• Sort by request date, property name, landlord name, or status urgency.

2

Review grouped requests per property

• Each property row shows title, landlord name, address, and management tier.

• Under each property, each request (e.g., “Airbnb”, “Booking.com”) appears with status and request date.

3

Open property details

• Top panel: property title, nickname, and quick actions:

  • Send Message to landlord (creates a support thread).

  • Edit Property (navigates to property edit page).

• Visible info: management tier, included services, extra subscriptions, and any related purchases.

4

Process connection requests from the Connection Requests section

• Airbnb connection:

  • Click “Connect to Airbnb”. The modal shows requirements: the listing must already exist and be active on Airbnb.

  • Choose whether the connection is visible to the landlord in their dashboard or kept private.

  • Proceed to open the Airbnb connection flow in a new tab.

  • The system polls the connection status and updates the property when done.

• Booking.com connection:

  • Click “Connect to Booking.com”.

  • If the property is not prepared for Booking.com (no Channex link), you’ll be prompted to connect to Airbnb first (Booking.com relies on Channex).

  • Follow the Booking.com connection flow: [[Booking.com Connection Flow]]

5

Manage connected channels and URLs

• Once a connection is Completed, view or add the public OTA URL (e.g., Airbnb listing URL) and store it against the channel.

• View channel status (e.g., Active/Inactive) in the Channels tab.

6

Optional actions

• Send a message to the landlord for clarifications (creates a support thread and routes Ops to it).

• Disconnect Airbnb if needed (e.g., misconfiguration). Disconnecting resets property status to active and removes the channel link.

Airbnb Connection as a Prerequisite for Other Channels

• Connecting to Airbnb is mandatory before establishing connections to other OTAs (e.g., Booking.com) because Airbnb is used to create the property structure in Channex.

• If a landlord requested only Booking.com (and not Airbnb), Operations must:

  • Create an Airbnb account on behalf of the landlord.

  • Create and publish the listing on Airbnb.

  • Initiate the Airbnb connection within Hububb. In the Connect to Airbnb modal, select “Hidden from landlord”, proceed, then unlist the property on Airbnb to prevent bookings. After that, connect Booking.com.

• If the landlord requested both Airbnb and Booking.com, Operations must:

  • First connect Airbnb using “Visible to landlord”.

  • After a successful Airbnb connection, connect Booking.com. This sequence ensures Channex is properly bootstrapped and prevents connection errors with other OTAs.

System flow (behind the scenes)

• Data retrieval:

  • List view: retrieves all properties via the properties API and filters to only those with connectionRequests.

  • Details view: retrieves a single property by ID with all related data: connection requests, property channels, images, amenities, address, pricing, subscriptions, and purchases.

• Airbnb connection:

  • App requests a short-lived connection link from the integrations API using landlord user ID, property ID, and chosen visibility flag.

  • A new browser tab navigates to Airbnb’s flow.

  • The app polls connection status using a temporary connection ID. Statuses: connected, pending, or failed.

  • On success, the property is refreshed and the request status becomes Completed; a success toast is shown.

• Booking.com connection:

  • If the property already has an active Airbnb/Channex connection, the Booking.com connect flow opens.

  • Otherwise, Ops are instructed to connect Airbnb first to bootstrap Channex.

• Storing OTA URLs:

  • For Completed requests, Ops can view or save the OTA URL. The URL is stored on the property channel record.

• Messaging:

  • Sending a message from the details page creates a support thread with source “operator” associated to the landlord; Ops are redirected to that thread.

• Disconnecting Airbnb:

  • The integrations API is called to disconnect; property details are marked Active and data is refreshed.

Statuses and what they mean

Request statuses

• PENDING: Request has been made by the landlord; Ops have not completed the connection yet.

• IN_PROGRESS: Ops are actively working on it (internally used; displayed as info).

• COMPLETED: The OTA connection has been successfully established.

• REJECTED: The connection failed in a final way (e.g., invalid listing).

Channel statuses (for already connected channels)

• Active: Live and bookable.

• Inactive/Cancelled: Disconnected or not visible to travelers.

• Pending: Connection in progress or awaiting confirmation.

What Ops can do in the details tabs

• Overview: property summary, hero image, description, quick stats, top amenities, pricing highlights, location preview.

• Details: metadata like bedrooms, bathrooms, type, listing type, times, and timestamps.

• Images: gallery; highlighted if photography service was purchased.

• Amenities: rich amenity list with icons.

• Location: full address details and map (if coordinates available).

• Pricing: base price or smart pricing ranges, weekend price, fees, guest pricing, weekly/monthly factors.

• Rooms: rooms and occupancy breakdown (when available).

• Channels: connected channels and their current status; summary of pending requests.

Important rules and edge cases

• Only properties where landlords have fully completed onboarding appear in Property Requests. If onboarding isn’t finished, the property will not show up and no connection can be initiated.

• Booking.com connections require prior Airbnb setup. If a property only has a Booking.com request but no Airbnb connection, Operations must connect Airbnb first. If the landlord does not want Airbnb bookings, the Airbnb listing can be unlisted immediately after the connection.

• When connecting to Airbnb, the listing must already exist and be active. The modal dialog will remind Operations to verify this before proceeding.

• Because the Airbnb flow opens a new browser tab, popup blockers can disrupt the process. If a popup is blocked, an error toast will appear — allow popups and retry.

• The system uses status polling after starting the Airbnb connection to check success, pending, or failure. Once status changes, the property view refreshes automatically and Operations receive a notification.

• When adding OTA URLs, the channel must already be connected. If disconnected, reconnect before saving OTA URLs.

• Disconnecting a channel removes the connection but keeps the property active within Hububb so it can be reconnected later without data loss.

What success looks like (Ops)

• Property appears in the list with a PENDING or IN_PROGRESS request.

• Ops completes the Airbnb flow; the request turns COMPLETED, the channel shows Active, and the OTA URL can be saved.

• If Booking.com was requested, Ops can proceed once Airbnb is in place; statuses transition similarly.

• Landlord communication can be initiated from the details view; a support thread is created and tracked.