Connect a Channel and Avoid Double Bookings

A channel connection imports listings, reservations, and related data. Map carefully and verify inventory before relying on it for availability or operational job generation.

What you will accomplish

By the end of this guide, you will be able to complete a channel connection from the correct CleanOver screen, understand the important checks before saving, and verify that the result is visible to the people who use it next.

Before you begin

• Obtain approved credentials for the channel account.
• Decide which internal units correspond to the external listings.
• Sign in to the Admin workspace and confirm you are in the correct business context.
• Use real operational dates and the property’s local timezone when the workflow includes time.

Step 1: Open Channels

Go to Channel Manager > Channels and choose the supported provider. Review any current connection before adding another.

Expected result: You know which account and environment are being connected.

Step 2: Authorize the provider

Complete the provider-specific connection flow with an authorized account. Do not reuse credentials from an unrelated business.

Expected result: The channel reports a connected state.

Step 3: Wait for initial listing import

Allow the first sync to load listings and connection metadata. Investigate authentication errors before mapping.

Expected result: External listings are available in CleanOver.

Step 4: Map each listing

Open Listing Mapping and pair every listing with the exact CleanOver unit. Confirm address, unit number, and provider ID.

Expected result: Each active listing has one intended internal destination.

Step 5: Handle combined inventory carefully

For parent, child, or multi-unit listings, use the approved inventory relationship. A convenient but incorrect one-to-one mapping can create conflicts.

Expected result: Inventory structure matches how the provider sells the property.

Step 6: Verify reservation import

Open Calendar Management and locate known upcoming reservations. Compare confirmation number, dates, and unit with the provider.

Expected result: CleanOver shows the same stay on the correct unit.

Step 7: Check overlap protection

Confirm cancelled or failed records do not block dates and that two active stays cannot occupy the same inventory unintentionally.

Expected result: Availability is protected from double booking.

Step 8: Monitor sync health

Review connection and mapping errors after launch, especially when listings are added or renamed in the provider.

Expected result: The connection remains accurate as inventory changes.

How to confirm the workflow is complete

• Refresh the destination list or calendar and confirm the saved record appears only once.
• Check the unit, date, status, owner or assignee, and any linked record before leaving the page.
• Open the next downstream view mentioned in the guide and confirm it shows the same information.
• Record an internal note when the action corrects historical data or changes another person’s responsibility.

Common issues and what to do

The expected record is missing

Clear old filters, check the date and business context, then search by the most specific identifier available. If the data comes from a connected provider, check connection and mapping status before recreating it manually.

A button is disabled

Look for a required field, incomplete checklist item, missing permission, locked lifecycle status, or unresolved linked task. Complete the highlighted requirement instead of trying to bypass it.

The page shows different information after refresh

Another user or integration may have updated the record. Compare timestamps and the source system, then apply the correction in the system that owns the data.

You are unsure whether to continue

Stop before cancelling, overwriting, revoking, or issuing a financial document. Ask the workflow owner to confirm the intended outcome and add that decision to the internal record.

Best practices

• Use clear names that make sense to a new team member without extra context.
• Prefer the smallest safe scope for bulk actions, filters, permissions, and date ranges.
• Keep guest-facing communication separate from internal diagnostic notes.
• Verify a high-risk change in a second view before considering it finished.
• Update the source configuration when the same correction is needed repeatedly.