> For the complete documentation index, see [llms.txt](https://software-help-docs.gitbook.io/knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://software-help-docs.gitbook.io/knowledge-base/software-guide/calendar/recurring-appointments.md). # Recurring Appointments **Introducing Recurring Appointments.** This article will go over recurring appointments in calendars and how to use them. All calendar types support recurring appointments. The only difference is that if you picked Round-robin, there must be a maximum of 1 user or team member on the calendar. {% embed url="" %} {% embed url="" %} Once you toggle on the Recurring Appointments, we can see the recurring appointments settings and you can select the settings based on your use case. {% embed url="" %} **What is the "If slots are not available" setting?** This basically means that if there is another appointment or event already booked for the intended slot, then the user has the following options: * Continue Booking * That simply means double book the slot * Skip booking Unavailable slot * That simply means book ONLY the ones that are available and ignore the rest * Book Next Available Slot * That simply means to book the reoccurrences irrespective of how far out in the future the calendar needs to scout for the available slots. * Caveat: We check only until the next 3 slots for availability * if unavailable we drop the booking * if available we continue and complete all recurrences **So, now will the already configured triggers fire for Recurring appointments?** No, it won't. We have added some new filters for Appointment Triggers. So all your configured triggers will have added a new filter for your Triggers {% embed url="" %} We added a new Event Type Filter in the appointment trigger, so now you can control the triggers that can fire for the type of your appointments. For all the existing Appointment Status triggers in your sub-account we have added a new Filter by default, and the Filter is Event Type: Normal. **Here are the new Filters and their scope:** **Event Type:** This new filter is added, so that you can fire for the appointments related to the type of the Calendar (Recurring Appointments Calendar or Non-Recurring Appointments Calendar or both) {% embed url="" %} Event: Normal So if we select this filter, then the appointments that are normal(which aren't recurring), and all your existing appointments would be considered normal and if we select this, then it would work the same as how it is working now. Event: Recurring If we select this filter, then the trigger would fire only for the appointments that got booked in Calendars that had recurring appointment settings turned On. Event: Any If we select this filter, then the trigger would fire for any type of appointment. ***Please Note:*** ***We are deprecating the Customer Booked Appointment Trigger, please use the Appointment Status Trigger*** {% embed url="" %} So now, if you select Created By Filter: 1. Customer: It would work the same as the Customer Booked Appointment, so if this filter is added, then appointments that are booked by the customer i.e. if the appointment is booked from the widget, then only this would fire. 2. User: All the appointments that are booked inside our software or any other source other than the appointments that are booked from the widget would fire the appointment. ***Please Note:*** * *User cannot bulk update appointments (cancel or reschedule)* * *Users should be careful when selecting the recurring booking option (book next vs skip booking vs continue booking)* * *If the meeting location is Zoom or google meet, All recurring appointments will have different meeting urls* * *If sync is on - events are synced as individual events with the third-party calendars* * *Recurring appointments can only be booked for standard slots (for custom slots we do not display a recurring booking option)* * *Users will not be able to book recurring appointments from the opportunities page. The recurring calendars will be available in the drop-down to book but only for a single time slot.* --- # 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://software-help-docs.gitbook.io/knowledge-base/software-guide/calendar/recurring-appointments.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.