> For the complete documentation index, see [llms.txt](https://docs.talkfurther.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.talkfurther.com/products/web-data/tour-availability-and-connected-calendars.md). # Tour Availability & Connected Calendars Tours are one of the strongest indicators of move-in intent, but scheduling them can be difficult when availability is unclear, calendars are disconnected, or teams have to manage confirmations manually. Further helps solve that by giving operators a way to control tour scheduling availability and, when enabled, connect sales calendars for a more automated scheduling experience. Further’s Tour Availability and Connected Calendars work together to help communities define when tours can be booked, optionally show real-time availability, and let sales teams confirm or reschedule tours directly from Further notifications. *** #### What it is and what it does Tour Availability lets teams: * Set bookable days and time windows for each community. * Allow or block same-day and next-day bookings. * Control whether scheduling follows fixed availability settings or connected sales calendars. Connected Calendars adds enhanced scheduling functionality by: * Connecting eligible team members’ calendars to Further for tour scheduling. * Supporting Google, Outlook, and Office 365-based calendar connections. * Giving sales teams Confirm and Reschedule options in tour request notifications. * Sending a confirmation notice and calendar appointment to both the prospect and the team member once a tour is confirmed. * Allowing staff to suggest alternate dates when the original requested time does not work. *** #### Key outcomes * More structured and accurate tour scheduling across communities. * Less manual back-and-forth for confirmations and reschedules. * Better alignment between booking flows and team availability when connected calendars are enabled. *** #### What problem it solves Customers often run into a few common problems: * Prospects request times that do not actually work for the sales team. * Teams have to manually confirm or reschedule tours after the initial request. * Scheduling logic is inconsistent across communities or booking experiences. Tour Availability and Connected Calendars help solve those issues by giving operators one place to manage booking rules and, if desired, layer in real calendar-based scheduling and confirmations. *** #### Value propositions * Reduce scheduling friction by making available tour times clearer. * Help sales teams move faster with built-in confirm and reschedule actions. * Support a more reliable prospect experience by tying bookings more closely to actual team availability. *** #### How it fits in the Further ecosystem Tour Availability supports scheduling experiences in Further-powered booking flows, including VSA and Conversational Webforms. Connected Calendars is a related enhancement layer. It can power real-time availability and enable confirmation and rescheduling workflows from tour request notifications. Pre-tour reminders and post-tour follow-up can also be used alongside tour scheduling, but they are separate messaging workflows rather than the core Tour Availability feature itself. *** #### How do you set it up **1. Prerequisites** * A Further community with tour scheduling in use. * Corporate access to manage Tour Availability and Connected Calendars. * Member-level users entered in Further if you want to connect individual calendars. **2. Enable or access it** To manage Tour Availability: * Go to `Settings → Tour Scheduling → Tour Availability`. To manage Connected Calendars: * Go to `Settings → Tour Availability → Connected Calendars`. **3. Required setup steps** * Set the days, hours, and same-day or next-day booking rules for each community. * If using real-time calendar availability, turn on connected calendars and select the users whose calendars should sync. * Send the authentication prompt so each selected user can connect their calendar. * Save and publish changes so the updated availability is reflected in the active flow. **4. How to test it’s working** * Submit a test tour request through an active Further booking flow. * Confirm the requested slot follows the configured availability rules. * If connected calendars are enabled, confirm the sales user receives Confirm and Reschedule actions in the notification. * Confirm that a successful confirmation sends the prospect a notice and creates a calendar appointment for both parties. *** #### Integrations and configuration overview **Required** * Tour scheduling configured in a Further booking flow. * Community-level Tour Availability settings. **Optional** * Connected Calendars for real-time availability and confirmation workflows. * Pre-tour reminders and post-tour follow-up campaigns layered on separately. **Key configuration options** * Bookable days and time ranges. * Same-day and next-day booking rules. * Whether availability is driven by fixed settings or connected calendars. * Which users’ calendars are eligible to sync. *** #### FAQs * **Do prospects only see valid times?** * Yes, if availability is configured correctly. That may come from fixed Tour Availability settings or, if enabled, from connected sales calendars for real-time availability. * **Do we need calendar integration to accept tour requests?** * No. Communities can still use Tour Availability settings without connecting calendars. Connected Calendars is required only for real-time availability and enhanced confirmation or rescheduling workflows. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.talkfurther.com/products/web-data/tour-availability-and-connected-calendars.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.