Rentals - Overview & How to Get Started

Getting Started with Rentals

Use this article as your starting point, then follow the linked guides to set up your rentals with confidence.

What are Rentals?

Feature of Rentals

Rentals is built to handle the unique complexities of rental-based scheduling. Here's what Rentals can do:

Setting Up Rentals

If you don't see the Rentals tab in your Calendar settings, enable it by following the instructions in How To Enable/Disable Rentals For Your Locations.

Rental invoices are not automatically sent to the customer whenever a booking is created. We are working on rectifying the information being displayed within the contacts/conversations page that conveys otherwise.

Once Rentals is enabled for your sub-account, continue:

Go to Calendars → Calendar Settings → Rentals.

1. 1Click to add your first rental item or property.
2. 2its,,,, and.
3. 3Use to,,, and.

To get more information on how to create a listing, read our article on Creating and Editing Listings.

Navigate to Rentals → Global Settings to adjust business hours, communication settings, and payment

methods.

For more information on how to customize global settings, read our article on Global Settings in Rentals.

Looking for more information on how to create a booking? Read our article on Creating a Booking in Rentals

How to Provide Feedback

Your feedback is critical to improving Rentals before general release. Here's how to share it:

• Post your feedback/suggestions/ideas on our.
• Schedule a Feedback Call: Book a time that works for you using this.
• Email us directly at: mayank.jain@Adaptive AI.com or swadha.bhoj@Adaptive AI.com

Frequently Asked Questions

Before you begin

“Rentals - Overview & How to Get Started” is part of the Properties → Property Listings area in Adaptive AI. Create and manage property or rental listings. Administrative settings can affect every user and customer-facing process. Make changes deliberately, verify permissions, and preserve a clear record of the previous configuration. The objective is not merely to save a setting; it is to confirm the result works for the staff member or customer who will depend on it.

• Confirm the business, location, user role, and settings area before changing a global option.
• Identify the teams, workflows, pages, channels, reports, or integrations that depend on the setting.
• Capture the current value and prepare a rollback path before changing security, notification, compliance, or account-wide behavior.
• Use a non-admin test user when the change affects permissions, navigation, visibility, or notifications.
• Choose a low-risk test window and notify responsible users when the result could affect active work.

Verify the result

After completing the instructions in this guide, use a controlled test before treating the setup as finished. A saved screen or success message confirms configuration, but only an end-to-end test confirms the business outcome.

1. 1Save the change, reload the settings area, and confirm the stored value is still present.
2. 2Test the result as the user role, device, channel, or customer state the setting is intended to affect.
3. 3Verify related workflows, notifications, integrations, and audit records continue to behave correctly.
4. 4Check that users outside the intended scope did not gain access or lose required functionality.
5. 5Document the final value, owner, reason, and verification result for future troubleshooting.

Troubleshooting checklist

If the result differs from what you expected, preserve the current state and isolate one variable at a time. Start with the checks below before deleting the configuration or rebuilding it from scratch.

• Confirm you edited the correct business and have permission to change the setting.
• Reload the page and test in a private browser window when the saved value and visible behavior do not match.
• Check inherited, user-level, integration-level, or channel-level settings that may override the account-wide value.
• Review audit history and recent administrator changes when behavior shifted without an obvious cause.
• Restore the documented prior value if the change causes broad disruption, then isolate the dependency before trying again.

Best practices

• Grant the least access needed and review administrator, billing, integration, and export permissions regularly.
• Use consistent naming and ownership conventions so settings can be maintained by more than one person.
• Document account-wide changes and avoid combining several unrelated changes into one troubleshooting session.
• Test notification and permission changes with real role boundaries, not only with an administrator account.
• Schedule periodic reviews for compliance, connected apps, inactive users, security controls, and billing configuration.